Read one registered agent
Returns one of the caller's agents. An agent owned by another account, and an id that never existed, answer the identical 404 body. A route that could tell those apart would be an oracle for enumerating other people's agents.
Returns one of the caller's agents.
An agent owned by another account, and an id that never existed, answer the identical 404 body. A route that could tell those apart would be an oracle for enumerating other people's agents.
Path Parameters
The agent's id, as returned by POST /agents.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/agents/string"{ "id": "string", "name": "string", "description": "string", "mcpClientId": "string", "createdAt": "string", "updatedAt": "string"}Register an agent POST
Registers an agent against the caller's account and returns it. An agent is the unit usage is grouped by, so registering one is what makes its spend separately reportable. The registration does NOT grant anything on its own. An agent can only make metered calls with a bearer the caller already holds — an `sk-` API key from `POST /account/api-keys` or the caller's own Privy session — and it draws on the caller's credit balance. Registering an agent is naming a workload, not minting a credential.
Deregister an agent DELETE
Deregisters an agent. The row stays: the usage reports still attribute the agent's past spend to its name, and a deregistered agent can never make another metered call. The delete is scoped by owner in the store query, so a foreign agent answers the same 404 as a missing one. Deleting twice answers 404 as well — the agent is already gone from every read, and a fresh timestamp would make a dead agent look recently used.