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.

1 public source
#SourceRolePublic status
1freestyle.shsourceprimary receiptsource_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.

Discovery graph / next reads

Continue through New Runtime

Open the graph
  1. 01related materialAnswer -> generated interfaceShift connected to this capability delta.
  2. 02related materialAgent APIs Need Fewer Magic Tricks and More FactsField Note connected to this capability delta.
  3. 03topicAgents - New RuntimeExplore the agents topic hub.
  4. 04topicAPI Design - New RuntimeExplore the api design topic hub.
  5. 05related materialAttacker-first agents turn vuln triage into repair candidatesShares agents.

These links are also published in this page’s JSON twin and as typed edges in DiscoveryGraph v1.

Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate…

Open the JSON contract