vAPI gives agents one USDC wallet for every x402 API call

An agent that reaches a paywalled API today has three bad choices. Hard-code a key owned by a human. Skip the request. Build a brittle signup flow of its own. A new open-source project called vAPI Network adds a fourth. One wallet, one spend policy, one receipt log for every x402 API the agent calls. Trendshift ranked it 7th on its daily list on 6 November 2026.

vAPI is on GitHub as vAPI-Network/vapi-network under the Apache-2.0 licence. It has 2,210 stars. It was created on 2 October 2026. The client is a non-custodial TypeScript CLI and MCP server. Keys stay on the agent's machine. Payment is in USDC on the Base network.

What the client does on each call

An x402 service answers an unauthenticated request with HTTP 402 Payment Required and a price. The agent runs vapi pay <listing-ref> --max 0.02. The vault reads a spend policy before signing. It sends the payment straight to the service. It writes a local receipt. vAPI Call takes no fee, so the provider gets the whole payment. The receipt shows the quote, the settlement, and the latency.

The client comes with an MCP server. It registers tools for discovery, payment, routing, and account management. An agent in Claude Code or Codex can call call.search, call.inspect and call.pay. Those tools find an API, check the price, and pay the call. A tool called router.chat sits over many models with one balance. A separate installer sets up Claude Code with vapi code install.

Spend caps, agent accounts, and swarms

The README describes three ways a team caps spend. An agent gets its own local wallet with a dollar cap. Multiple agents can share a treasury and policy as a swarm. A member can leave and the treasury sweeps the funds back. The owner signs off on every account link and every top-up to the treasury. The CLI refuses an approval prompt during an unattended swarm run, so the agent cannot talk itself past the cap.

Receipt logs live on the machine as JSON. A team reading them can tell how much each call cost, what it returned, and how long it took. That is the number a buyer could not get before when the alternative was a monthly SaaS bill.

What is still unverified

Three honest limits. First, the token totals in the receipts are vAPI's own. No third party has audited them. Second, x402 adoption is small. Cloudflare's Monetization Gateway charges agents on the seller side. It opened in closed beta on 30 September 2026 with four customers. A buyer-side client only pays off when enough sellers price per request. Third, USDC on Base means the funds move on-chain. A team sending a $0.002 call pays a Base network fee on top. That fee has been stable but is not zero.

Given those, the signal is real. A team building agents that call paid tools can now test one wallet across many services. Buy $5 of USDC. Tell an agent to search and call. Read the receipts after a day. If the model's spend lines up with what the receipts show, the loop is closed. That is a different test than guessing API costs from a SaaS dashboard.

Source

• vAPI-Network/vapi-network, GitHub