Agent-first API makes retries deterministic
Explicit fields, precise errors, request metadata, and raw facts turn an agent retry from guessing into near-deterministic repair.
Capability delta
Before: Agent calls a human-friendly SDK and receives an opaque failure. Enabling change: API returns command, exit code, stderr, allowed values, request id, timeout, and raw metadata. After: Agent can correct the next tool call from explicit machine-readable facts. Human consequence: The human spends less time reading logs for the agent and explaining what exactly broke.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | freestyle.shsource | primary receipt | source_urls |
| 2 | x.comsource | supporting receipt | source_urls |
| 3 | aws.amazon.comsource | supporting receipt | source_urls |
This is the first homepage delta for New Runtime. It shows that post-app software starts not with beautiful generated UI, but with the right contract between the model, tools, and the state of the world.
Why now
As tool use grows, the API becomes the environment where the agent thinks and repairs itself. An opaque error breaks the loop; an explicit error gives the next step.
September 2026 update
Why now
Scoped-key and multi-account gateway designs make an agent’s next action both more machine-readable and more constrained. Governed connectors add a platform example.
The contract should include allowed values, error class, request ID, timeout, idempotency, scope, expiry, and audit record. Keep a human approval gate for material writes.