A
licenseNot graded
qualityC
maintenanceEnables MCP-compatible agents to discover and call x402 paid services from a directory of over 2,000 APIs.
Apache 2.0
@vapi-network/mcp
Officialby vAPI-Network
Integrates with Coinbase Bazaar as a discovery source, allowing the client to read and merge public x402 v2 service listings from Coinbase's facilitator catalog.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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. The device vault encrypts your keys on this machine,
using an OS-stored device key with optional password protection. vAPI applies spend policy before
signing, sends the payment straight to the service, and writes a local receipt.
Local runs keep keys on this machine; experimental Railway runs require explicit member-key export.
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.
vAPI Call takes no fee. Providers are paid directly.
Call, Router, Stake and Agents are live on production. Tasks is coming soon. See vapinetwork.ai and the documentation.
vAPI Network is not related to Vapi.ai, the voice AI company.
Install
This README describes client 0.13.0. npm view vapi-network version shows the latest published release.
npm i -g vapi-networkNo 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.)
An agent can set itself up from the agent skill. Tell it: "Read https://vapinetwork.ai/SKILL.md and follow it to set up vAPI." The same file ships in this package as SKILL.md, with the CLI version it describes in its frontmatter.
Interactive CLI runs check for a newer release at most once a day and cache the result in
~/.vapi/update-check.json. JSON, MCP server, CI and non-TTY runs skip the check. Set
VAPI_NO_UPDATE_CHECK=1 to disable it.
Related MCP server: x402-mcp
Quickstart
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, latencyBack 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.
Headless Linux
On Linux without a working keyring (servers, containers, GitHub Codespaces), set
VAPI_VAULT_PASSWORD before vapi setup; the device key and agent link are then
kept in ~/.vapi/secrets.json, encrypted with that password. The choice is made once
per vault.
read -rs -p 'Vault password (at least 12 characters): ' VAPI_VAULT_PASSWORD
export VAPI_VAULT_PASSWORD
vapi setupIn GitHub Codespaces, add VAPI_VAULT_PASSWORD as a Codespaces secret with at least
12 characters before running setup.
What you can do
Surface | What it does | Guide |
Call | Discover, check, publish and pay for x402 APIs. | |
Router | Use vAPI Router for model access and balance. | |
Tasks | Preview task posting, USDC escrow and delivery; coming soon on production. | |
Agents | Run capped local agents with dedicated wallets and profiles. | |
Swarms | Group capped local agents around a treasury and capital policy. | |
MCP | Use namespaced payment tools from an MCP client. | |
SDK | Use Call, vAPI Router and local agents behind one wallet-bound API. | |
Vault | Manage the owner wallet, device vault, accounts and spend caps. | |
Backup | Store encrypted vault copies and restore with owner approval. |
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, tasks.search, tasks.show, tasks.post, tasks.propose, tasks.submit, tasks.award, tasks.sign, tasks.fund, tasks.deliver, tasks.release, tasks.refund, tasks.dispute, tasks.counter-evidence, tasks.resolve-unmatched, tasks.message, tasks.thread, tasks.watch, tasks.status, 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. The tasks.* tools target the Tasks preview, which is coming soon on production. Inputs and results are in docs/mcp.md.
Swarms
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.setupsets up or resumes the treasury, member accounts, profiles and owner links.swarm.addadds or resumes one member.swarm.leavesweeps one member to the treasury and removes it from the swarm.swarm.fundreturns owner funding instructions or funds the treasury from a linked local account.swarm.rebalancemoves funds between the treasury and linked members under local caps.swarm.statusreports balances, links, allocation history and unfinished movements.swarm.dissolvesweeps the swarm back to the owner and removes its local swarm record.swarm.runruns 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.runacceptsdetach: trueto start in the background, andswarm.runslists a swarm's runs with status.swarm.allocateandswarm.delegateare agent-only operations and are refused outside a swarm run; their optionalrequestIdinput 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 local or Railway runs for the swarm. The confirmation flag clears one stale start only after you verify its worker is gone.vapi agent run <name> "<task>" --detachstarts one agent run in the background.
Deprecated tool aliases
These pre-namespace names still work and each result carries a DEPRECATED: line naming its replacement.
Alias | Use instead |
|
|
|
|
|
|
|
|
Use your Compute in Claude Code and Codex
These commands are available since 0.12.0.
Set up a vAPI account with the quickstart above. Install Claude Code or Codex and make its executable available on PATH. Configure vAPI for the tools it finds:
vapi code installThe installer reuses your account link and Router key, or starts login and creates
a key when needed. The key stays in the existing OS secret store. Codex gets a
vapi model provider and profile in ~/.codex/config.toml, or
$CODEX_HOME/config.toml when CODEX_HOME is set. Claude Code needs no config file
change. Missing tools are reported and skipped; if neither exists, nothing is
written.
Interactive terminals ask once before adding shell aliases. To accept without a prompt:
vapi code install --yesAliases cover only tools found on PATH. The installer replaces its marked block
in ~/.zshrc or ~/.bashrc; Windows skips aliases. Open a new terminal after
adding them. To keep your shell configuration as it is:
vapi code install --no-aliasStart either tool in your project directory:
vapi claude
vapi codexAt launch, vAPI chooses the Router when at least $0.50 of today's Compute remains. Otherwise, or when the Router cannot be reached, it starts your own Claude subscription or Codex/ChatGPT login. You must already be signed in to that tool. The choice happens at launch. There is no local proxy or automatic mid-session switch.
Claude Code defaults to venice/claude-sonnet-5-5. The installer sets Codex's
profile model to venice/openai-gpt-61-sol. At launch, Codex uses that profile's
configured model unless --model overrides it. Without the profile, the launcher
supplies equivalent options for the child process and writes no config file.
Flag | Behavior |
| Uses the tool's own login with your existing environment, without checking the Router. |
| Forces the Router route, even below $0.50. Missing credentials fail the launch; unavailable usage omits the amount. |
| Counts purchased Router balance for launch selection; uses it for the session when Compute is below $0.50. |
| Selects a model. Claude accepts |
| Selects the vAPI account whose Router credentials and allowance to use. |
vapi claude --own
vapi codex --vapi
vapi claude --use-balance --model opus
vapi codex --model venice/openai-gpt-61-sol --account mainOther arguments keep their order. A literal -- ends launcher option parsing and
passes everything after it to the tool. The interactive launchers reject
--json; install and uninstall support it. If you supply Claude Code's
--settings, vAPI passes yours through and warns that its model settings were
not added.
When Compute runs out mid-session, the Router returns HTTP 429 with
budget_exceeded. Exit Claude Code:
/exitThen resume the conversation through the launch check:
vapi claude --continueFor Codex, quit the session:
/quitThen resume its last conversation:
vapi codex resume --lastThe launchers change model endpoint and selection. Project files, CLAUDE.md,
skills and MCP servers stay as configured. Claude requests on vAPI Compute go
through Venice. Claude rows on Venice are anonymized, not private.
Remove the installed provider, profile and marked alias blocks:
vapi code uninstallUninstall preserves other config content, including MCP entries. It retains your account link and Router key.
CLI reference
The code installer and Claude Code/Codex launchers below are available since 0.12.0. Task commands require a preview server; Tasks is coming soon on production.
Most commands accept --json and write one success or error value to stdout.
The Claude Code and Codex launchers are interactive and reject that flag.
Task watch and a partially completed scope-signing flow can emit newline-delimited
JSON; delivery emits one result after chain success. See Task commands. Exit codes are
0 for success, 1 for an operational failure, and 2 for invalid usage or
an announced preview-only command.
Solana listings remain searchable. Inspecting or paying one returns
unsupported_network (CLI exit 1); vault payments on Solana arrive in a later release.
Inspect shows the registry’s last observed quote; pay fetches a fresh quote before signing.
Hosted search hides listings in outage unless --include-outage is set.
API hits can include health and cheaper or healthier alternatives; inspect can
include response schemas and an example request. Search, inspect and pay JSON
results include zero to four next-action hints.
Protected-vault access and legacy secret-store commands are documented in the wallet guide.
Every wallet command takes --account <name>, falls back to VAPI_WALLET, then the default from vapi accounts use; --wallet <name> is deprecated and still accepted.
Task exit codes are 0 ok, 1 error or invalid usage, 2 policy refusal, and 3 approval needed in non-interactive mode. Scope signing requires --yes or interactive approval; without either it exits 3. A policy refusal at exit 2 has JSON ok:false with reason: "policy.perTask" or reason: "policy.perDay". Invalid usage exits 1 with {ok:false,error:{code:"usage_error",message}}. Run vapi task --help for details. Chain operations require a locally trusted escrow factory. Base Sepolia pins 0x6Ba83621eb386B3E093032096251cA504F6ee033; VAPI_TASKS_ESCROW_FACTORY_<chainId> can configure another chain or override that pin. Base Sepolia uses BASE_SEPOLIA_RPC_URL, or https://sepolia.base.org when the variable is unset. The client verifies factory and clone state through the trusted RPC before signing, waits for successful transaction receipts and server confirmation envelopes, and records pending operations under VAPI_HOME for recovery. Dispute and counter-evidence approve the verified contract fee before submitting evidence. Local per-task, daily and approval policies apply to that fee. Fund, deliver, release, refund, dispute, counter-evidence, resolve-unmatched and watch auto-release require a scope signed on this machine. --counterparty only confirms the existing local binding. See task security and recovery.
Posting a task moves no money. The create-order contract stores its market amount, deadline, intake and award limit. A webhook is configured on the new order through its dedicated endpoint. OAuth task reads require tasks:read; writes require tasks:write, which also grants reads. See Task commands.
Command | Options | What it does |
|
| Creates |
|
| Creates or restores the vault, links the first account, and can offer cloud backup. Safe to rerun. |
|
| Lists local accounts and can add the owner's accounts on other devices as read-only rows |
|
| Derives and links a new account |
|
| Imports an account from a private-key prompt or local keystore |
|
| Renames an account and its local records |
|
| Sets the default account |
|
| Moves an account to |
|
| Restores an account from |
|
| Sets the account's spend caps and automatic Base USDC ceiling |
|
| Splits USDC across linked local accounts and records resumable legs |
|
| Continues an unfinished distribution; unsafe restored or legacy address replacement requires its terminal-only review flag |
|
| Cancels eligible legs without signing; restored legs require terminal-only review and signed legs require proven expiry |
|
| Creates or resumes a treasury, member accounts, profiles and owner links |
|
| Adds or resumes one member |
|
| Sweeps a member to the treasury and removes it from the swarm |
|
| Prints owner funding instructions or funds the treasury from a local account |
|
| Moves funds between the treasury and linked members under local caps |
|
| Reports balances, links, allocation history and unfinished movements |
|
| Sweeps the swarm back to the owner and removes its local swarm record |
|
| Runs the lead or each member under run budgets |
|
| Runs dedicated members in experimental Railway sandboxes; see the swarm guide |
|
| Lists stored runs and their runtime status |
|
| Stops local or Railway runs; confirmation clears a verified stale start |
|
| Sends USDC to the owner or another active account; vAPI pays gas |
| - | Name, address, default marker, caps in USD, unlocked, label |
|
| Deprecated alias for |
| - | Makes it the default for every later command |
| - | Deprecated alias for |
|
| Deprecated alias for |
| - | Deprecated alias for |
|
| Sets that wallet's spend caps, in US dollars |
|
| Prints and opens the hosted funding page. Makes no network call. |
|
| Asks the public vAPI documentation assistant and prints its answer and sources; no wallet or payment |
|
| Searches the vAPI documentation and prints matching excerpts; no wallet or payment |
|
| Reads one vAPI documentation page as Markdown; no wallet or payment |
|
| Legacy form: one deposit account per configured network, with balances and guidance |
|
| Registry discovery with group, tier, health and alternatives |
|
| Health, verification, request and response contracts, example request and the registry's last observed quote |
|
| Pays locally, includes hints in JSON, and names the limit blocking a payment |
| - | Checks settlement, shows its payment id, and never pays |
|
| Grades its 402, extensions and same-origin discovery. Never pays |
|
| The wallet's address and USDC balances |
|
| The local append-only call ledger, newest last |
|
| Raw receipts for a spreadsheet or dashboard |
|
| Spend, outcomes, latency percentiles and top services |
|
| Moves USDC to an address, or to the linked owner when omitted; open movement legs block it |
|
| Creates a capped local agent wallet, profile and owner link; |
|
| Runs the named agent with an optional hard budget across Call and Router top-ups; can detach locally |
|
| Runs from an exported member bundle in the experimental remote runtime; see the swarm guide |
| None | Lists profiles, links and today's Call and Router budgets |
| None | Prints the agent's spend policy, caps and tools |
| None | Stops future runs until the agent is resumed |
| None | Allows a paused agent to run again |
| None | Revokes the link and removes the profile, but keeps its wallet |
|
| Opens My agents on your vAPI dashboard and offers to link an unlinked wallet. |
|
| Links the local agent wallet to your vAPI account |
|
| Removes the selected wallet's agent link and stored credentials |
|
| Shows the chosen wallet's owner link and permissions, whether the link is live, and its ERC-8004 agent identity. |
|
| Unreleased (next version). Configures detected coding tools for vAPI Compute and optional shell aliases |
|
| Unreleased (next version). Removes the vAPI provider, profile and marked shell aliases |
|
| Unreleased (next version). Starts Claude Code on Compute or the tool's own login; interactive, no JSON |
|
| Unreleased (next version). Starts Codex on Compute or the tool's own login; interactive, no JSON |
|
| Lists the vAPI Router model ids |
|
| Shows the agent's Compute allowance and Router balance |
|
| Sends one chat request through vAPI Router |
|
| Prints a gated Router key or rotates it without printing it |
|
| Buys vAPI Router balance with USDC from your wallet |
|
| Sets or clears automatic vAPI Router balance refill |
|
| Shows the linked owner's stake and Compute today |
|
| Prints and optionally opens the staking page |
|
| Finds public tasks and filters the returned page. |
|
| Shows the acting party's task or a public card and prints settled escrow receipts |
|
| Stores the task and market settings, configures an optional webhook, and moves no money |
|
| Signs proposal terms locally and offers to take a task |
|
| Uploads files and signs bounty proof. Needs server support for public terms, submissions and bearer tokens on upload routes. |
|
| Awards a proposal or submission. Moves no money. Needs server support for bearer tokens on participant routes. |
|
| Signs the agreed scope locally. A worker creates the unfunded escrow with the local vault wallet. |
|
| Applies local spend policy and funds escrow with the local vault wallet. |
|
| Prepares a delivery manifest from 1 to 20 files and records delivery onchain. |
|
| Releases escrow to the worker with the local vault wallet. |
|
| Returns escrow to the poster with the local vault wallet. |
|
| Applies spend policy, approves the verified fee and raises a dispute. |
|
| Pays the verified fee and submits counter-evidence before the deadline. |
|
| Resolves an unanswered dispute after the onchain deadline. |
|
| Sends a task message. Needs server support for bearer tokens on participant routes. |
|
| Reads task messages. The cursor is nextBeforeSeq for an older page. Needs server support for bearer tokens on participant routes. |
|
| Watches task events. Auto-release signs with the selected local vault wallet. |
|
| Shows chain state and participant events when signed in, or the public task card. |
|
| Prints the private key. Terminal only, never for an agent. |
|
| Prints the 12 words, or turns encrypted cloud backup on or off. |
|
| Rebuilds the vault from a recovery phrase typed at the prompt or piped on stdin, or restores an owner-approved cloud backup. |
|
| Restores a wallet from a prompt, never from argv |
|
| Changes a legacy keystore passphrase; vault accounts use |
|
| Adds a password to the device vault |
|
| Removes the password from the device vault |
|
| Closes the protected vault on this device |
|
| Opens a protected vault session for eight hours |
|
| Deprecated alias for |
|
| Shows whether the device vault is protected and open |
|
| Deprecated alias for |
|
| Writes a privacy-preserving local bug report |
| - | Types the registry API key on a prompt into the OS secret store |
| - | Whether this machine has a key and where it comes from, masked |
| - | Takes the stored key back out |
|
| Probes your API, lists the endpoints you pick, signs the payout wallet |
| - | Takes a listing live once every endpoint pays the signed payout wallet |
| - | Asks vAPI to review the listing |
| - | Every listing this API key owns |
|
| Takes over the listings vAPI indexed from your API, signed by their payee |
|
| Serves the MCP tools over stdio |
|
| Registers vAPI through Claude Code's CLI or writes the client's MCP config |
| - | Preview only; exits |
| - | The client version, also as |
| - | Lists commands and flags, also as |
Phrase recovery checks Base USDC balances until five consecutive addresses are empty and reports the number scanned. vapi restore --accounts <n> (or vapi setup --accounts <n> when restoring) derives a fixed count without balance queries.
Packages
Package | Purpose |
| zero-dependency distribution with the |
| x402 protocol, wallet store, spend policy, discovery merge and receipts |
| vAPI Registry, Coinbase Bazaar, local-file and x402scan source adapters |
| stdio MCP server with namespaced payment tools |
| command parsing and the command implementations behind |
Every npm tarball is bundled and has zero runtime dependencies. The scoped
packages are useful for embedding; most users should start with vapi-network.
vAPI Desktop
vAPI Desktop is the macOS app for managing agent wallets and connecting local MCP clients.
The signer process keeps keys on your computer.
Version 0.1.0 is not released yet; signing and notarization are pending. The source is in apps/desktop.
See the desktop release guide for building and signing the app.
Development
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:checkAll 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:npmpublish: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.
License
Apache-2.0. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessLimited data
Related MCP Connectors
Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.
Metered MCP tools: free discovery over MCP; per-call execution settled in USDC via x402 v2.
Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.223 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes MCP tools that let an agent search a catalog, inspect a paid service's pricing, fetch it with payment handled automatically, and check its remaining budget and active spending limits. Payments are authorized against a signed mandate from the owner, so agents can buy API access over HTTP 402 without ever holding the owner's private key.599 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP hosts to invoke pay-per-call wallet, risk, web, repo, and x402 catalog utilities while automatically handling 402 challenges, EIP-3009 USDC payments on Base, and spend guards with a local agent wallet.MIT