Vaaya Review (2026): Pricing, Features & Honest Verdict

Vaaya is pay-per-call payment infrastructure for AI agents that turns your GitHub history into a spending limit. We found the pricing unusually transparent and the credit line unusually vague. Best for: developers shipping agents that need to buy tools. Price: From $0 ($2 free credit, no card). Rating: 7.5/10.

What is Vaaya?

Vaaya sits between your AI agent and the services it wants to buy. Instead of signing up for Exa, Firecrawl, Fal, Apollo.io, Browserbase and Modal separately, putting a card on each and handing your agent six API keys, you connect Vaaya once and your agent gets metered, priced, pay-per-call access to more than 1,400 tools through a single connection. The agent never receives a provider credential. It asks Vaaya, Vaaya pays the provider, and one line lands in your ledger with the price and the result.

The novel part, and the reason it took a top slot on Product Hunt on 16 August 2026, is how you get spending power. Connect your GitHub account and Vaaya reads your public history: how long you have been contributing, what you have shipped and how consistently. That produces a score, and the score unlocks a credit line your agents can draw against before you have paid anything. The company is Vaaya Inc, the connector ships as the npm package @vaaya/mcp, currently at version 0.6.4 and first published in June 2026, and the integration work is public through the vaaya-ai GitHub organisation.

What are Vaaya’s key features?

A credit line derived from your GitHub profile

Scores run from 300 to 850. Below 500 the starting limit is $0 and you earn upward from there. Around 600 it starts near $20, around 700 near $75, and a top record starts in the hundreds. Settled usage grows the limit toward a ceiling that scales with the same score, capped at $5,000. The score refreshes at most once a day, and immediately when the scoring model changes, while the limit itself moves per settlement event rather than on a schedule. It is a credit bureau for developers, built on the only public financial-shaped record most developers have.

A catalog where the price is quoted before the call runs

Every paid call carries a maximum cost and is priced before it executes, so the agent sees the number and a spend cap in advance. Failed calls cost $0. The published sample rates give a good sense of the shape: LLM answers from under 0.1 cents across 300-plus models behind one OpenAI-compatible endpoint, web search and web scraping at about 1 cent, deep research at 10 to 30 cents, lead enrichment from 5 cents a contact, company signals at 25 cents, image and media generation from 33 cents, email at 1 cent, browser sessions at 0.2 cents a minute, property data at 20 cents, and compute and GPU billed by the second from T4 up to H100.

One install and three ways in

Setup is npx @vaaya/mcp install for anyone comfortable in a terminal. If you are not, there is a click-through setup for Claude, ChatGPT and other MCP clients, and a browser chat that skips setup entirely while drawing on the same services and the same balance. Meeting non-terminal users where they are is a deliberate choice for a product whose buyers are mostly developers, and it widens the audience past the CLI crowd.

Four payment rails, hidden behind one balance

Underneath, Vaaya settles four different ways and shows you one number. Some calls go out as an x402 payment per request in USDC on Base. Some use MPP, a token per purchase. Some run against a conventional provider account Vaaya holds and meters on your behalf. And for services with no per-call product at all, Vaaya subscribes with its own card and exposes the service per call anyway, so you are not buying a seat to make one request. That last case is the most useful of the four and the hardest to replicate yourself.

Spend controls that are named rather than described

The security page lists controls by name instead of adjectives. Provider keys are held server-side and injected only when a validated call is dispatched. MCP clients connect over OAuth 2.1 with PKCE, and API callers use a bearer key you can name and revoke, with revocation never requiring an upstream key rotation. Outbound work such as email drafts waits for your approval before it goes anywhere. Vaaya also states that your data is never used to train public or shared foundation models, never sold and never licensed.

How much does Vaaya cost?

Vaaya has no subscription, no seats and no monthly minimum. Every account starts with $2 of free credit at signup with no card required, and everything else is added on top of that rather than replacing it. From there you have two routes. Connect GitHub and your score unlocks a card-backed line, roughly $20 at a mid record, around $75 at a strong one and into the hundreds at the top. Or buy prepaid packs at $10, $30 or $100 that never expire.

The $10 pack is the useful reference point, and Vaaya prices it in work rather than tokens: roughly 1,000 web searches, 200 contact lookups, or 30 generated images at catalog prices. That works out to about a cent a search, 5 cents a lookup and 33 cents an image, which reconciles with the published sample rates. Settlement on the card-backed line happens at the end of each week, or immediately once the amount passes $50, so the line is real credit rather than a prepaid wall.

Against the field this is remarkably legible. We checked the obvious comparisons and none of them publish a price: Skyfire sells agent identity and payment credentials with no pricing page, Payman does agentic banking with no published figures, and Nekuda’s WebMCP product does not publish rates either. In a category where every competitor says “contact us”, Vaaya publishes a twelve-row rate card and a $2 free balance you can spend without a card. That alone earns it a look.

How honest is Vaaya’s no-markup claim?

Vaaya says there is no platform fee, no per-seat charge and no monthly minimum, and that the catalog price is the final price. All three are true as stated. But the page also says something more interesting a few lines down, and it deserves reading carefully.

For most of the catalog, Vaaya pays the provider on its own account and “the listed price covers that cost plus Vaaya’s margin”. So there is no fee added on top of the quote, and there is margin inside the quote. Those are different claims and the site does not blur them. For the x402 and MPP rails, which settle per request against the merchant directly, Vaaya says you pay exactly what the merchant asks with “no Vaaya markup on top today”. That word today is doing real work, and it is to the company’s credit that they left it in rather than writing a promise they might have to break.

What you cannot do is check the margin. Without each provider’s list price for each call, “cost plus margin” is unfalsifiable. The commitment Vaaya does make is procedural rather than numerical: if it ever changes how it takes margin, the change appears in the catalog price quoted before a call, which is the only number that reaches your ledger. That is a reasonable bargain for a gateway, and the honest framing is that you are buying convenience and consolidated billing, not a guarantee of the cheapest possible rate. If a single provider dominates your spend, price it directly before routing it through here.

What does Vaaya’s security page actually promise?

We read it end to end because a product that holds provider credentials and charges a card weekly is asking for more trust than a typical developer tool. The page is better than most, and its limits are worth stating plainly.

The strong part is that every claim names a mechanism. Not “enterprise-grade security” but OAuth 2.1 with PKCE, server-side credential injection per validated call, revocable named bearer keys at a specific endpoint, per-call maximum cost priced before execution and charged only on success, human approval gates on outbound work, and encryption in transit and at rest. It also describes, per data type, what Vaaya stores and what it forwards, on the reasoning that a call cannot run without sending its parameters to the provider that serves it. That is a real limitation stated rather than hidden.

The gap is certification. There is no SOC 2, no ISO 27001 and no third-party audit claimed anywhere on the page. Incidents go to a general hello@ address read by “the people who operate the system”, which is candid and also tells you the size of the team. For a solo developer or a small startup that is fine. For anyone whose procurement asks for an audit report before a vendor touches a card, Vaaya is not through the gate yet, and no amount of well-written control documentation substitutes for the certificate.

Who is Vaaya best for?

Use Vaaya if you are building agents that need to buy things: research agents that search and scrape, sales agents that enrich leads, media agents that generate images, or anything that needs a sandbox or a GPU for a few seconds. The value is highest when your agent touches many providers occasionally rather than one provider constantly, because that is exactly the case where signing up, holding keys and reconciling six invoices costs more than the margin you are paying. The $2 free balance means you can prove the shape of it before deciding.

Skip Vaaya if your agent hammers a single provider, since you will get a better rate and better support going direct. Skip it if your GitHub history is thin or your career has been in private repositories, because the credit line is derived from public contributions and a sparse public profile means a $0 limit above the free $2, which turns the headline feature into a prepaid card. And skip it for now if you need a SOC 2 report to onboard a vendor.

What are the best Vaaya alternatives?

Skyfire is the closest competitor in ambition, giving agents verified identity and payment credentials that work across the open internet rather than inside a curated catalog. It is the broader bet: Vaaya sells you a marketplace, Skyfire sells you the trust layer to transact anywhere. It publishes no pricing at all, so you cannot compare cost without a conversation.

Payman approaches the same problem from banking rather than API access, deploying agents that execute real transfers and payments on your existing rails with configurable controls and audit trails. If your agent needs to move money rather than buy tools, that is the shape you want. It also publishes no pricing.

Holding your own provider keys is the honest baseline, and for a small number of providers it wins. You pay list price with no margin, you keep the direct support relationship, and you control your own rate limits. What you give up is the thing Vaaya sells: one balance, one ledger, one credential to revoke, per-call metering on services that only sell subscriptions, and no reconciliation at month end.

Final verdict: is Vaaya worth it?

Vaaya is the most legible product we have seen in agentic payments, which is a low bar the category keeps failing to clear. It publishes a twelve-row rate card when its competitors publish nothing, it gives you $2 to spend without a card, it charges nothing for failed calls, and it discloses where its margin sits instead of hiding behind a no-platform-fee headline. The GitHub credit score is a clever answer to a real problem, which is that a new agent developer has no way to establish spending trust with anyone.

The reservations are about what you cannot verify. The margin inside the catalog price is unfalsifiable without provider list prices. The credit line is described in ranges and adverbs, with the actual figure visible only once you are inside, so you cannot know before signing up whether your history buys you $0 or $300. And there is no third-party security certification behind a product that holds credentials and charges your card weekly. None of that is disqualifying at this size, and all of it is fixable. Start with the free $2 and a $10 pack, keep your heaviest single provider direct, and let the ledger tell you whether the convenience is worth the margin. For most developers shipping agents in 2026, we think it will be.