Wire it into your stack

An integration you cannot inspect is one you cannot trust. Every surface here is documented, versioned and testable from inside the app with your own credentials.

Reference pages you can actually use

Each surface ships an OpenAPI schema and a live reference page. Authorise with a real key, expand an endpoint, send the request, read the response — the same request your code will make, against your own data, before you commit to anything. There is a ReDoc rendering alongside it for reading rather than poking.

One key, one job

Keys are minted per surface. A key issued for personas is refused by any other endpoint even when the person holding it is entitled to both, so revoking one has a blast radius you can predict rather than discover.

Name them for what they are — the client, the script, the machine — and the list tells you when each was last used. Switch one off while you investigate something and switch it back on; the token survives. Delete it and it does not.

Rate limits that protect you from your own automation

Every plan carries per-minute ceilings on requests and tokens, plus a limit on how fast any single conversation may turn. That last one is the useful one: an agent that loops is the ordinary way a month's budget disappears in an afternoon, and it is caught in seconds rather than at the invoice.

Two surfaces, and the reason there are two

The personas API is chat against the colleagues you built. The teams API runs a whole multi-agent crew as one call, for work that needs several roles in conversation rather than one voice answering.

There is deliberately no third. Raw model-configuration access stays internal to the platform — it would give you nothing the personas surface does not, on the same models, minus the voice and memory that make an endpoint worth naming.