> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/products/roadmap-status.md). # Roadmap and status Current product status and recently shipped work. This page is for readers checking the status of each vAPI product and what is being built next. | Area | Status | Where | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | vAPI Call | Live: pay x402 APIs from the console, the CLI, MCP or the SDK | [Call](https://docs.vapinetwork.ai/call/) | | vAPI Router | Live: OpenAI-compatible Venice models; daily Compute from staking or prepaid Router balance | [Router](https://docs.vapinetwork.ai/router/) | | Stake | Live: stake vAPI on Base for a daily Router Compute limit; 24-hour withdrawal cooldown | [Stake](https://docs.vapinetwork.ai/stake/) | | Agents | Coming soon: local wallets and owner-controlled account links | [Agents](https://docs.vapinetwork.ai/agents/) | | Reference | Reference for Call: client 0.9.5, public HTTP API, x402 on vAPI, contracts. Router and Stake routes live; Agents setup is documented separately | [Reference](https://docs.vapinetwork.ai/reference/) | | Tasks | In preview | [Tasks](https://docs.vapinetwork.ai/tasks/) | | vAPI token | Live on Base | [The vAPI token](/token-and-foundation/vapi-token.md) | ## Live in Call * Directory with card and table views, plus **My APIs** at `/call/my-apis`. * Permissionless listing with verification as a tier. * The Graph as the first Verified Provider. * MPP listings shown as **Not payable here**. * ERC-8004 identity shown on listings. * **Routed through vAPI** stats for USDC settled through vAPI clients. ## Live in Router and Stake * Router API keys, model catalog, usage, and USDC balance top-ups. * Active-stake snapshots at 00:00 UTC, with the Compute job at 00:10 UTC. * Withdrawal requests, 24-hour cooldown, cancellation, and withdrawal. * Staking contracts redeployed on 2026-10-20 with the 24-hour cooldown. The current addresses are on [Staking contracts](https://docs.vapinetwork.ai/stake/contracts). * Owner-approved allowances that cap each linked agent's Compute and balance keys separately. ## Coming soon * Agents. Tasks is in preview for longer work with escrow between clients and workers. The preview accepts no payments or work. ## Being built Each item below has a published design and plan. None of them is live yet, and none has a date. | Item | What it does | Product | | ---------------------- | ---------------------------------------------------------------------------------------------- | ------------ | | Owner rules for agents | Allowed providers, verified listings only, owner approval above an amount, more than one owner | Agents | | Provider trust score | One score per listing from live checks, uptime, latency, verification and payment outcomes | Call | | Pay per usage | The agent signs a maximum and pays what the request used | Call, Router | | A2A agent card | A standard card so agents on other platforms can find APIs through Call search | Call | | Paid MCP tools | Tools on the hosted MCP server that any x402-paying MCP client can buy | Agents | ## Later * Batched tiny payments, so sub-cent prices do not each need their own settlement. * The trust score published to ERC-8004 reputation onchain. ## Next * [How vAPI works](/how-vapi-works.md) * [Products overview](/products/overview.md) * [Tasks](https://docs.vapinetwork.ai/tasks/) Checked on 2026-10-15. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.vapinetwork.ai/products/roadmap-status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.