vAPI Network

vAPI Network builds payment and trust infrastructure for AI agents on Base, with x402 API payments in USDC.

One wallet, every x402 API. vapi-network is its open-source, non-custodial TypeScript client for discovering and paying x402 services from a terminal, an MCP client, or your own code. Your key is generated on your machine, encrypted under your passphrase, and never leaves it. vAPI applies spend policy before signing, sends the payment straight to the service, and writes a local receipt. Every payment identifies this client as vapi through x402 builder-code; when an API advertises payment-identifier, the generated id is kept on that receipt.

Call is launching. Router, Stake and Agents are coming soon. Tasks is in preview. See vapinetwork.ai and the documentation.

vAPI Network is not related to Vapi.ai, the voice AI company.

npm i -g vapi-network

No install? Prefix any command with npx vapi-network, for example npx vapi-network init. (npx vapi cannot work: the bare vapi name on npm belongs to an unrelated package.)

npm i -g vapi-network
vapi setup [--no-cloud-backup]   # creates or restores the vault, derives main, links it to your owner wallet; safe to rerun
vapi fund                        # opens the hosted funding page for your address
vapi search "weather"            # every catalogue, merged, with provenance
vapi pay <listing-ref> --max 0.02
vapi receipts                    # one line per paid call: quote, settlement, latency

Back up the recovery phrase only in a terminal; vAPI cannot recover it. Turn on encrypted cloud backup with vapi backup --cloud; only the owner can approve a restore.

Wallets and custody are in docs/wallets.md, and account transfers are in docs/sending.md. Configuration, funding, networks and bug reports are in docs/configuration.md.

The MCP server registers docs.search, docs.read, vapi.status, vapi.accounts, vapi.siblings, accounts.add, accounts.caps, accounts.send, auth.link, auth.status, router.models, router.usage, router.chat, router.buy, call.search, call.inspect, call.pay, call.read, swarm.setup, swarm.add, swarm.leave, swarm.fund, swarm.rebalance, swarm.status, swarm.dissolve, wallet.address, wallet.balance, wallet.accounts, wallet.list, wallet.use, wallet.fund, receipts.list, receipts.stats, support.report, swarm.run, swarm.allocate, swarm.delegate, swarm.runs; inputs and results are in docs/mcp.md.

Swarms keep a treasury and capped member accounts on this machine. Setup is safe to rerun; the owner approves account links and funds the treasury. A deposit arriving at the treasury after dissolve stays on the treasury account, which is kept on this device.

• swarm.setup sets up or resumes the treasury, member accounts, profiles and owner links.
• swarm.add adds or resumes one member.
• swarm.leave sweeps one member to the treasury and removes it from the swarm.
• swarm.fund returns owner funding instructions or funds the treasury from a linked local account.
• swarm.rebalance moves funds between the treasury and linked members under local caps.
• swarm.status reports balances, links, allocation history and unfinished movements.
• swarm.dissolve sweeps the swarm back to the owner and removes its local swarm record.
• swarm.run runs the lead, which may delegate one level deep using treasury-funded budgets bounded by a per-run draw (default $2.00), or runs every member independently on its own capital.
• swarm.run accepts detach: true to start in the background, and swarm.runs lists a swarm's runs with status.
• swarm.allocate and swarm.delegate are agent-only operations and are refused outside a swarm run; their optional requestId input makes retries idempotent.

MCP always declines approval prompts during swarm runs.

CLI commands:

• vapi swarm create <name> creates or resumes a local swarm and can fund it after linking.
• vapi swarm add <name> <role> adds or resumes one member.
• vapi swarm remove <name> <member> sweeps one member to the treasury and removes it.
• vapi swarm fund <name> <usd> prints owner funding instructions or funds from a local account.
• vapi swarm rebalance <name> moves capital toward the swarm's configured targets.
• vapi swarm status <name> reports balances, links, allocation history and unfinished movements.
• vapi swarm dissolve <name> sweeps the swarm to the owner and removes its swarm record.
• vapi swarm run <name> "<task>" runs the lead or every eligible member with per-run budget and treasury-draw limits.
• vapi swarm run <name> "<task>" --detach [--runtime local] starts the run in the background.
• vapi swarm runs <name> lists background runs and their status.
• vapi swarm stop <name> [<runId>|--all] [--confirm-worker-stopped] stops one or all running local processes for the swarm. The confirmation flag clears one stale start only after you verify its worker is gone.
• vapi agent run <name> "<task>" --detach starts one agent run in the background.

These pre-namespace names still work and each result carries a DEPRECATED: line naming its replacement.

Every command accepts --json, which writes one JSON value, success or error, to stdout. Exit codes are 0 for success, 1 for an operational failure, and 2 for invalid usage or an announced preview-only command.

Every wallet command takes --account <name>, falls back to VAPI_WALLET, then the default from vapi accounts use; --wallet <name> keeps working for one release.

Every npm tarball is bundled and has zero runtime dependencies. The scoped packages are useful for embedding; most users should start with vapi-network.

A pnpm workspace for Node.js 22 and pnpm 10. The gate, in order:

pnpm install
pnpm format:check
pnpm lint
pnpm typecheck
pnpm test
pnpm build
pnpm pack:check

All five packages share one version and are released together. npm reads a package manifest before lifecycle hooks run, so the release is made from the generated publish/ directories, never from the workspace package roots.

pnpm install --frozen-lockfile
pnpm pack:check
npm login
pnpm --dir packages/core publish:npm
pnpm --dir packages/sources publish:npm
pnpm --dir packages/mcp publish:npm
pnpm --dir packages/cli publish:npm
pnpm --dir packages/vapi-network publish:npm

publish:npm publishes a package's staged ./publish directory to the latest npm tag; publish:npm:next publishes the same tarball to next. The manual release workflow verifies artifacts and prints these commands; it never receives npm credentials and never publishes.

See AGENTS.md for layout and invariants, CONTRIBUTING.md for the workflow, CHANGELOG.md for what shipped in each release, and SECURITY.md for private vulnerability reports.

Apache-2.0. See LICENSE.