Bring your own agent.
Point OpenClaw, Hermes, or your own runtime at one Deva endpoint.
Introducing the Deva Agent API
Give your agent one Deva key for frontier models, web search, images, voice, browser tools, and usage metering across providers.
Agent teams do not need another API directory. They need one runtime surface for model calls, tools, metering, and spend control.
Agent resources, one subscription
Point OpenClaw, Hermes, or your own runtime at one Deva endpoint.
Models, tools, credits, and limits sit behind the same credential.
Use Deva credits across providers instead of managing separate vendor spend.
Use Deva as the default path, then bring provider keys when you need them.
01
Create a Deva account and use the same credential for model calls, tools, and metering.
02
Use Deva from OpenClaw, Hermes, or your own runtime without juggling provider-specific API keys.
03
Run the agent yourself, or let hosted Genie provision the server and connect channels for you.
Use one API path for channels like Slack, Telegram, and WhatsApp when your agent needs to respond.

Call Claude, OpenAI, Kimi, and more through one Deva credential instead of provider-specific wiring.
Hey, I need help scheduling a team meeting that works well for everyone. Any suggestions for finding an optimal time slot?

Track credits across model calls and tools so agent spend is visible from the first request.
Pick a plan for your key. It works with any agent you run.
Plus
Monthly credits for every model and tool
Super
Larger credit pool for daily drivers
Ultra
Highest credit pool for heavy agents
Do not want to self-host? Genie runs the agent for you.
Your Deva key pre-wired on a hosted server, live in under a minute.
Genie Go
2GB / 2vCPU / 60GB
$20/mo
Genie Plus
4GB / 2vCPU / 80GB
$40/mo
Genie Pro
8GB / 2vCPU / 160GB
$65/mo

1 API
Give your agent one Deva key. We route model calls, agent tools, credits, and hosted Genie when you want the server too.
API catalogs
Directories like getanyapi.com or monid.ai help discovery, but your agent still needs glue across providers.
Deva Agent API
One API for agents: models, tools, credits, and a hosted path when you want Deva to run it.
API catalogs
Directories like getanyapi.com or monid.ai help discovery, but your agent still needs glue across providers.
Deva Agent API
One API for agents: models, tools, credits, and a hosted path when you want Deva to run it.
Single agent API surface
Frontier models plus agent tools
One account for metering and top-ups
Works with self-hosted agents
Hosted Genie on-ramp
Bring your own provider keys
Built for production agent spend
Privacy & data
How Deva approaches credentials, routing, and control so you can ship agent API traffic with confidence.
01
Use a dedicated Deva credential for agent workloads and rotate access when your policy requires it.
02
Traffic is protected in transit with modern TLS. Stored data uses platform-standard encryption at rest.
03
Your agent request content is not used to train public foundation models. It stays in your environment.
04
Enable only the model and tool surfaces you need. Revoke or rotate access anytime from your account.
05
When you use your own API keys, they are stored and applied securely without exposing them in the client.
06
Track credits and top-ups from one Deva account instead of reconciling separate provider bills.
07
Operational access to infrastructure follows strict controls and is limited to what is required to run the service.
08
We document what runs where, what leaves your instance, and how subprocessors are used so you can review risk.
FAQ
Connect your runtime to Deva for models, tools, credits, and usage metering. Add hosted Genie only when you want us to run it.