Integrations
Agent onboarding
An agent that provisions its own key, its own budget and its own base URL, no console visit.
When the thing integrating is an agent rather than a person, the console is in the way. POST /v1/keys is all it needs: the agent asks for a key under a bundle you allow, gets one back with a cap already attached, and starts calling.
The flow
The agent never sees your sk_. Your backend holds it and mints on the agent's behalf, which is what keeps one runaway agent from being able to mint itself a bigger budget.
Provisioning endpoint
- 1
Take the request and decide what it is allowed
The agent identifies itself however your product already does it. You choose the bundle and the ceiling; the agent does not.
ts - 2
The agent stores what it got and calls
Two values are all it needs. Any OpenAI-shaped client works from here.
python - 3
Handle the ceiling
A capped agent gets a 402 with
spend_cap_exceeded. That is backpressure, not a failure, stop the run and let the next window pick it up.python
Rotation
Rotating is minting a new key and revoking the old one. Because attribution is per key, the agent's history stays attached to the key that produced it. You do not lose the record by rotating.