Let your customers’ agents pay for metered services.
If your product runs agents for customers, those agents need search, data, models, and compute from outside providers. Vaaya gives each one a credit account with a policy, so you do not have to hold vendor balances on your customers’ behalf.
The agent’s job
Your product’s agent does work for a customer. It researches, enriches records, generates media, or runs code. Each step may call a paid provider.
The friction today
To serve those calls, you open an account with every provider, fund it, hold the keys, and re-bill customers from your own ledger. Each new provider adds another balance to watch and another key to guard.
With Vaaya
Each agent gets a key with a policy. It calls providers through Vaaya, which pays the provider and records the transaction under that key. You see what each agent drew, and the account settles from your card weekly.
An example
A sales assistant product enriches 400 contacts for a customer. The agent calls a contact data provider through Vaaya at a few cents per contact, inside a $50 monthly limit on its key. The product shows the customer the cost per contact straight from the transaction record.
Integration
Use the HTTP API with one key per customer agent, or MCP if your agent runs in an MCP host. Tag each call with an agent name to keep records separate.
Risk
Restrict keys to the categories your product uses. Set a monthly limit per key. A key that misbehaves can be revoked without touching the others.
Give your product’s agents an account.
Create an account, then create one key per agent from the API.