EP02: Router & Staking.
Agents need intelligence to get work done. Network participants need a way to put their stake to use.
Router brings access to AI models. Staking connects $vAPI participation to compute credits, putting that intelligence within reach.
Two more pieces fall into place: https://t.co/SDzSQvhTIv
Your $vAPI stake can power your AI.
Earn compute credits every day by staking $vAPI, then put them to work across 150+ AI models through vAPI Router. One stake. Daily credits. Your choice of models.
Start staking, connect via SDK, CLI or MCP, and use those credits to power your applications and agents.
Explore the docs to learn more: https://t.co/bFYWvQNizG
o1 Exchange is now part of our Verified Provider selection!
Access launchpad data, swap quotes and token launch preparation from @o1_exchange for your agent, paid per call through vAPI Call.
Integrate our MCP to try o1 today: https://t.co/MengtlwliP
EP02: Router & Staking.
Agents need intelligence to get work done. Network participants need a way to put their stake to use.
Router brings access to AI models. Staking connects $vAPI participation to compute credits, putting that intelligence within reach.
Two more pieces fall into place: https://t.co/SDzSQvhTIv
Our Verified Provider selection now includes @birdeye_data!
Access 20 Birdeye Data endpoints covering token prices, security, holders, trades and more through vAPI Call.
$0.003 per call, paid in USDC on @Solana via x402.
Integrate our MCP to try Birdeye today: https://t.co/CNutqJi2G3
vAPI security update
Following this week’s PHP and Node.js security advisories and our infrastructure provider’s security incident:
• PHP: vAPI is not affected by this week’s critical PHP remote code execution vulnerabilities. PHP isn’t part of our stack.
• Node.js: patched to the latest security release and rolling out across all services.
• Credentials: rotating all keys and secrets as a precaution.
vAPI is up and running normally. Some planned updates may land a little later while our provider’s build pipeline recovers.
Next up: vAPI Router and Staking launch soon. Stay tuned. 👀
EP02: Router & Staking needs one more day.
Deployment issues with our infrastructure provider have delayed today’s release.
Until then, a little of what’s coming.
We now support @arc and @solana across our MCP, SDK and CLI.
Agents and developers can access paid APIs on these networks through vAPI Call, with USDC payments powered by x402.
Connect through MCP, integrate vAPI into your application with the SDK, or make requests directly from the command line.
More networks, and more capabilities within reach. One connected infrastructure for agentic commerce.
From setup to your first paid API call. See vAPI Call in action.
Our protocol lead @MarkTbuilds walks through installation and demonstrates Call using @graphprotocol as a showcase provider, with USDC payments on @base powered by x402.
The first piece is live. The next two arrive together.
Another step toward one trusted network where agents and humans do business.
EP02: Router & Staking - October 21.
Good question, two cases:
Wrong payTo: the buyer signs for one exact amount and recipient. Our client pins each listing to its registered payout address, so if the 402 asks for a different one, it aborts before signing. Self-listed APIs that don’t pay their own payout address can’t be listed.
Low balance: the facilitator rejects the authorization before settlement. No USDC moves and the API doesn’t serve the response.
Under the hood of vAPI Call: how an API request becomes a paid transaction.
The API returns its payment requirements. The buyer authorizes a specific USDC amount for a specific recipient. Payment settles on @base through x402, and the API returns its response.
Discovery gets an agent to the right capability. Call gives it a way to pay for and use it within the same workflow.
For providers, that turns an API endpoint into something an agent can purchase when the job demands it.