Interactive work
Every verified route is included for one human-driven user, with 60 RPM and 2 concurrent requests.
Fair use & limits
Unlimited for real work.
Explicit about abuse.
Heavy legitimate interactive development continues. Credential sharing, resale, scraping, attacks, compromised keys, and disguised unattended automation do not. Operational limits remain visible.
newtons / signalPOLICY / 06POLICY / 06Make the boundary legible.
POLICY BOUNDARYreason + next step!FROMsubscription rail
→TOfair use / explicit
Six distinct boundaries
A limit should tell you what happened.
Newton’s separates commercial inclusion, operational capacity, and abuse protection instead of hiding all three behind one generic error.
| Boundary | What it means | What happens next |
|---|---|---|
| Agents funded balance | The prepaid Agents wallet cannot cover the next authorization. | The workload request stops before creating spend beyond the available balance. |
| Rate limit | Too many requests entered the current time window. | Newton’s returns 429 with retry guidance. |
| Concurrency | Too many requests are active at once for the access class. | Reduce parallelism and retry after the active work completes. |
| Route availability | The requested published route is not currently verifiable or available. | Refresh the catalog; Newton’s does not silently substitute another model. |
| Protection state | Confirmed abuse, automation on an interactive key, or a compromised credential requires intervention. | You see the reason, duration, affected keys, and support route. Cost alone cannot restrict legitimate interactive use. |
| Interactive-use policy | Solo and Team have no daily or monthly token cutoff for legitimate human-driven interactive use. | Human work continues. Unattended and automated workloads move to prepaid Agents. |
Human vs automated
Separate lanes protect both.
Continuous agents can create a radically different cost and capacity profile from an individual developer. Newton’s does not hide that difference.
Shared work
Five seats share every verified route, governance, 120 RPM, and 4 concurrent requests.
Automated work
Loops and background execution use scoped keys, 60 RPM, 4 concurrent requests, and a prepaid balance ceiling.
Limits should preserve trust.
If a request is blocked, the reason should help you decide what to do next.