NEWTON’SFunded before execution
A workload has a visible balance before it starts. Authorization does not quietly turn an automation into membership overage.
AGENTS / AUTOMATION
Give automation
its own lane.
Agents is Newton’s metered workload layer for unattended execution. Keep human-driven interactive work included with membership; fund, scope, and inspect the jobs that run without you.
DESIGNED FOR UNATTENDED WORK
Different job.
Different control.
Interactive subscriptions optimize for a person in the loop. Agents optimizes for repeatability, clear authorization, and a small blast radius when a process behaves unexpectedly.
Scoped to the job
Use a separate workload key for background loops, CI, parallel tasks, or production automation so human and machine traffic stay legible.
Bounded by policy
RPM, concurrency, model availability, and fair-use controls apply. A runaway loop should stop at a known boundary.
COMMON WORKLOADS
Put the right work
behind the key.
Use an Agents workload when the request should continue while the developer is away from the keyboard.
Review every change
Run bounded code review, test explanation, release-note, or migration jobs from a dedicated automation key.
Keep the queue moving
Process jobs, summarize incoming work, or enrich records without consuming a human plan’s interaction lane.
Scale a known loop
Split a repeatable task across controlled concurrency, then use receipts to understand route, usage, and cost.
OPERATING CONTRACT
Start bounded.
Expand with evidence.
Agents is intentionally explicit. The system should tell you when funding, policy, capacity, or a route prevents a request from continuing.
| Before execution | During execution | After execution |
|---|---|---|
| Fund the balance and create a workload key. | Honor rate, concurrency, model, and retry boundaries. | Store the request ID and settled receipt, not the secret. |
| Choose only an exact published model ID. | Stop on policy, identity, or authorization errors. | Reconcile accepted cost and remaining balance. |
Keep people and processes clear.
Use membership for the developer at the keyboard. Use Agents when the job needs to run on its own.