Concepts
Seven ideas the whole API is built out of — tenancy, projects, sandboxes, agents, budgets, memory and workflows.
After these seven pages the rest of the API explains itself.
The cloud has many capabilities. It does not have many ideas — it has seven, composed. Read these once and a capability you have never opened will make sense from its name and its address.
The org is the one boundary. How a request becomes a tenant, and why nothing behind the edge re-decides it.
Two different things are called a project. Which one you have decides which API you want.
The one compute primitive: a lease on a pod that runs somebody else's code.
Define an agent, open a session, steer it, keep the run. One flow is one tree.
What an agent may spend. Quoted before the call, refused in band, in integer micro-USD.
What an agent remembers, where it is stored, and who else can read it.
Work that runs itself — on a schedule, on a webhook, or on a canvas.
The one sentence
A request carries a credential. The edge turns that credential into an org — the tenancy boundary every store is isolated on. Inside an org you create projects, which scope work. Code runs in a sandbox, which is a lease. An agent is a definition plus a session that can be steered and replayed. What it may spend is its budget, checked before every call. What it knows comes from memory. What runs without you asking is a workflow.
Everything else in the API is one of those seven with a specific job.