> 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/usage-and-limits.md).

# Usage and limits

Router is coming soon; usage accounting will track the daily staking allowance, agent limits, and purchased USDC balance.

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

Router reports daily Compute usage and purchased Router balance for the wallet or linked agent using it. Use the usage view to see which budget is available before you send more requests.

## Compute

Each owner has a daily Compute limit from staking. The limit follows a 24-hour epoch aligned to 00:00 UTC. It does not roll over.

The daily limit depends on the wallet's share of eligible stake, the daily pool, the per-wallet cap, and the allocation floor. See [Compute from staking](https://docs.vapinetwork.ai/stake/compute-entitlement).

Each linked agent has a separate daily Compute allowance set by the owner. An agent's Compute request uses both its allowance and the owner's daily Compute limit. The usable Compute amount is the smaller remaining amount.

## Router balance

CLI chat, local MCP chat, and SDK `client.router.chat()` try Compute first, then a stored balance key after Compute is exhausted. Direct OpenAI-compatible clients spend the source attached to the supplied key and must switch keys themselves. A balance key spends the owner's shared purchased Router balance, outside the daily Compute limits. Purchased balance does not expire. See [Buy Router balance](/router/buy-router-balance.md).

## View usage

The console shows Router usage and the available balance on `/router`. For an owner session, the session-authenticated API exposes the caller-specific data at:

```http
GET /api/router/usage
```

For a linked agent, do not use the owner-only usage route above. Use its agent bearer with the `router.use` scope at:

```http
GET /api/agents/self/router
```

This response reports the agent allowance, the owner's Compute limit, the remaining Compute amount, and the Router balance when one exists.

## Per-key limits

App-issued Router keys have these per-key limits:

| Limit               | Maximum |
| ------------------- | ------: |
| Requests per minute |      60 |
| Tokens per minute   | 100,000 |
| Concurrent requests |      10 |

These limits are separate from the wallet's daily Compute limit and a linked agent's allowance.

For key creation and rotation, see [Access and keys](/router/access-and-keys.md).

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/usage-and-limits.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.