> 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/router/buy-router-balance.md).

# Buy Router balance

Router is coming soon; USDC balance purchases will cover model usage after the daily staking allowance is used.

{% hint style="info" %}
vAPI Router is coming soon. This page describes how it works at launch.
{% endhint %}

This page is for people and agents who need more Router usage after the daily staking limit is used.

Buy Router balance in fixed USDC tiers from the console, CLI, HTTP API, or local MCP server.

## Tiers and payment

The available tiers are:

* $1
* $5
* $20
* $50

You pay in USDC over x402 on Base. Arc is available when it is configured. The purchased balance never expires.

The HTTP API exposes one top-up route for each tier:

```http
POST /api/router/top-up/{1|5|20|50}
```

Authenticate the request with one of the accepted credentials: an owner session, an API key, or an agent bearer with `router.use`. Resolve that credential before the payment challenge. An unauthenticated request returns `401 owner_required` and does not include an x402 challenge. The selected route buys the matching tier with exact USDC after the owner is resolved. See the [HTTP API reference](https://docs.vapinetwork.ai/reference/http-api/api-overview) for the public API conventions.

## How Router spends it

CLI chat, local MCP chat, and SDK `client.router.chat()` try Compute first, then a stored balance key after Compute is exhausted. Each Router key spends one source selected at creation: Compute or balance. Other OpenAI-compatible clients spend the source attached to the supplied key and must switch keys themselves. Your Router usage shows the purchased amount, spent amount, and remaining amount.

See [Usage and limits](/router/usage-and-limits.md) for the daily Compute window and [Use Router from your agents](/router/use-router-from-your-agents.md) for linked agent budgets.

## Buy from the console

Open `/router` and find the Router balance section. Select a tier and complete the USDC payment.

## Buy from the CLI

Buy a tier:

```bash
vapi router buy <1|5|20|50>
```

The command accepts `--account <name>` and `--json`.

After a chat request exhausts Compute, the client checks the balance threshold and can buy the selected tier. Set automatic refill:

```bash
vapi router buy --auto <tier> --below <usd>
```

Clear automatic refill:

```bash
vapi router buy --auto off
```

The automatic refill command accepts `--account <name>`. Client spend caps apply to every purchase, including automatic refill.

## Buy from local MCP

The `router.buy` tool accepts `usd` of `1`, `5`, `20`, or `50` and returns a receipt summary and the new Router balance. It does not return a Router key.

## Next

* [How Router works](/router/how-router-works.md)
* [Usage and limits](/router/usage-and-limits.md)
* [HTTP API overview](https://docs.vapinetwork.ai/reference/http-api/api-overview)

Checked on 2026-10-02.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vapinetwork.ai/router/buy-router-balance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.