A controlled account for internal agents.
Coding agents and internal assistants need paid services during their work. Vaaya gives the team one account, one key per agent, and a record of what each agent spent.
The agent’s job
A coding agent searches documentation, scrapes a page, runs code in a sandbox, or calls a model that is not on the team’s plan.
The friction today
Each developer signs up for providers, pastes keys into agent configs, and expenses the bills. Keys end up in repositories, and nobody knows what an agent spent until the invoice arrives.
With Vaaya
The team opens one account. Each developer’s agent connects over MCP and gets its own key and policy. Calls are priced before they run, charged on success, and listed by agent.
An example
An engineer connects Claude Code with one command. The agent runs a deep research call and then a sandbox for half a minute. Both calls appear under the engineer’s key with the price paid, and the account settles once a week.
Integration
Run "npx @vaaya/mcp install" on each machine, or point the agent at the remote server at vaaya.ai/mcp. No provider keys are stored on developer machines.
Risk
Give each key the categories it needs and a monthly limit. Revoke a key when someone leaves the team.
Connect the team’s agents.
One command per machine. Every call lands under the key that made it.