vaaya / about

The payment system for AI agents

Vaaya is one MCP server that gives agents metered, pay-per-call access to the providers they need — without handing the agent a pile of vendor accounts, API keys, or subscriptions.

What Vaaya does

An agent describes an outcome. Vaaya routes it to a suitable provider, validates the request, shows the price ceiling, executes the call, and returns the result. Search, data, LLMs, media, scraping, compute, and storage all sit behind the same connection.

Calls are metered individually and failed calls are not billed. See the public capability catalog, pricing, and documentation.

Who builds it

Vaaya is built and maintained by Vaaya Inc. The MCP connector and integration work are visible through the vaaya-ai GitHub organization, where developers can inspect releases, open issues, and follow the project.

Our goal is simple: make a new capability available to an agent without making every user become an API integrator and billing administrator.

How the security model works

The agent gets narrow, metered access to a capability. It does not receive the upstream provider credential.

Credentials stay server-side. Provider keys and accounts are held by Vaaya and injected only when a validated call is dispatched.
Authorization is revocable. MCP clients connect over OAuth 2.1; grants and tokens can be revoked without rotating every upstream key.
Spend is bounded and visible. Every paid call carries a maximum cost, is recorded in the ledger, and is charged only after a successful result.
Payment rails are abstracted. Vaaya can settle through x402, MPP, or a conventional provider account while the user sees one balance and audit trail.
Direct x402 is optional. Agents holding USDC can call supported endpoints without a Vaaya account; the payment challenge and settlement happen over HTTP.

Questions, security reports, or partnerships

Email hello@vaaya.ai, or open an issue in the public MCP repository. Legal and privacy contacts are listed in our Privacy Policy and Terms.