vAPI Network skill
vAPI Network is an x402 USDC payment client that pays an agent's API calls from a wallet with a local spend limit.
- 4,306 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The client signs real USDC payments from the user's device; a leaked device vault or a wrong spend limit causes direct financial loss.
- Experimental Railway runs require exporting the member key off the local device.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/vapi-networkDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The client signs real USDC payments from the user's device; a leaked device vault or a wrong spend limit causes direct financial loss.
- Experimental Railway runs require exporting the member key off the local device.
This is third-party code. Review the repository files before installing.
What it does
vAPI Network is a non-custodial TypeScript client for discovering and paying x402 services from a terminal, an MCP client, or your own code. The x402 protocol turns an API's `402 Payment Required` response into a payment transaction ready to sign in USDC on Base; the client keeps keys in an encrypted local device vault under a device key with optional password protection, applies a spend limit before signing, and sends the payment straight to the service with no intermediary. Every payment carries the `vapi` identifier in its `builder-code`, and a local receipt is saved to disk.
Who it is for. Agent developers who need to pay for x402 services from one wallet directly from a terminal or MCP client.
Good fit when
- An agent needs to pay a `402 Payment Required` response from a specific API in USDC on Base itself.
- Payments need a spend limit applied before the client signs the transaction.
- A local receipt for every payment is needed, rather than trusting an external billing service.
- Several x402 services need paying from one non-custodial wallet.
Not a fit when
- A server deploy without manually exporting a device key is wanted: that step is currently required separately for Railway.
- Payments need a network other than Base: the client is built specifically for x402 on Base.
- The similarly named voice company Vapi.ai is the intended service: it is an unrelated project.
Example request
Set up vAPI, set a 5 USDC daily spend limit and pay this x402 service's request from your own wallet.Limitations
The client handles real USDC payments on Base: a misconfigured spend limit or a leaked device key causes real financial loss. Runs outside the local device (experimental Railway deployments) need an explicit, separate member-key export, widening the risk surface compared to local storage. The Tasks feature is stated as "coming soon" in the README as of publication, not yet available. The project is unrelated to the voice platform Vapi.ai despite the similar name.
How to disable. Remove the installed `vapi-network` package and wipe the local device key vault; for Railway deployments, revoke the exported member key separately.
FAQ
How does an agent install vAPI itself?
Tell the agent to read `https://vapinetwork.ai/SKILL.md` and follow it; the same file ships in the package as `packages/vapi-network/SKILL.md`.
Where are keys stored?
In an encrypted local device vault under a device key with optional password protection; local runs never leave the machine.
What happens when the spend limit is exceeded?
The client applies the spend policy before signing a transaction, so a payment over the limit is neither signed nor sent.
Does vAPI take a fee on a call?
No, vAPI Call takes no fee; providers are paid directly.
Can it run without installing?
Yes, commands can run through `npx vapi-network`, for example `npx vapi-network init`; the short name `vapi` on npm belongs to an unrelated package.
Discussion
No questions or reviews yet.
Related
SkillsA CLI with an MCP server and a skill: the agent calls paid APIs while the user approves each HTTP 402 stablecoin payment with Touch ID
A Python CLI and SDK for agent payments in USDC: transfers from Circle wallets and paid API calls over the x402 protocol
Coinbase's official skill: sign-in, balance, transfers and token swaps through the awal CLI on Base, Polygon and Solana.
Circle's official plugin: 19 skills on USDC, wallets, bridges and agent payments, plus a remote MCP server with the docs
Skill that finds paid APIs in the TadaPay directory by protocol and network and returns the endpoint and request format. Your client pays.
A skill that connects an agent to EasyPay: Stripe products and invoices, SBP and T-Bank payout links, crypto and Mercury in natural language
README in short
The author describes the product as payment and trust infrastructure for AI agents on Base, with one wallet for every x402 service.