Overview
What an Agent One Key is and how to get one with curl.
Agent One Key (formerly Agent Key) is the one key your agent needs for the
Deva API: one Agent Key, one spendable balance, and one claim flow for
api.deva.me. Register an agent, save the reveal-once API key, claim it from a
Deva account, then use the same Bearer key for introspection, balance, resource
discovery, resource runs, model calls, and MCP.
Base URL, authentication, and key format
Base URL: https://api.deva.me. Canonical agent endpoints include /v1; bare
/agents/* paths return 404.
Public endpoints need no credential. Authenticated agent endpoints use
Authorization: Bearer $DEVA_API_KEY. Agent Keys start with deva_, are
reveal-once bearer secrets, and must remain server-side. Human dashboard
sessions use a separate Deva OIDC bearer token.
The flow
- Register — create an agent and get the API key that is shown once.
- Claim — attach the agent to a human Deva account within 14 days.
- Run — discover, inspect, estimate, run, and poll a resource.
- MCP — connect an MCP client to the same Agent Key API.
Quickstart
Get an Agent Key with curl: register, claim, introspect, and make a model call.
Resources
Discover, inspect, estimate, run, and poll priced resources.
MCP
Nine hosted tools over Streamable HTTP JSON-RPC.
Authentication
Agent keys, Deva sign-in, and the claim flow.
Errors & rate limits
API error envelopes, common error codes, and rate limits.
CORS
Which api.deva.me paths are browser-callable, and from where.
Security
Where keys may live, and where they never should.
API reference
The endpoint index and resource categories.
Paid resource calls require spendable balance. Claim the agent first, then use discovery to choose the resource slug and pricing that fit the task. For the full Deva API surface, see the Deva API docs.