> 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/access-and-keys.md).

# Access and keys

Router is coming soon; wallet-bound keys and linked agent credentials will authorize model requests at launch.

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

Router keys authorize requests to vAPI Router. Use the console for owner keys, or link a local agent wallet and use the agent commands.

## Create and revoke an owner key

Sign in to the vAPI console with your wallet, then open `/router`. The Router page lets you create and revoke Router keys.

A Router key is a bearer token bound to one wallet. A wallet can hold 10 active owner Router keys across both sources. Each secret appears once at creation, so copy it then. When you create an owner key, choose whether its source is `compute` or `balance`:

* A Compute key uses the wallet's daily Compute limit.
* A balance key uses the wallet's purchased Router balance.

Send a Router key only to the Router base URL. Never send it to the console API. Revoking a key in the Router page stops that key.

For the daily allowance that comes from staking, see [Compute from staking](https://docs.vapinetwork.ai/stake/compute-entitlement).

## Linked agent keys

An agent receives scoped rights on your vAPI account, not on your wallet. Agent keys can only make model calls. The agent's Compute key uses both its daily allowance and the owner's daily Compute limit. Its balance key spends the owner's shared purchased Router balance, outside those daily limits. See [Use Router from your agents](/router/use-router-from-your-agents.md).

To inspect the link from the CLI:

```bash
vapi whoami
```

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

To rotate a linked agent's Router key:

```bash
vapi router key --rotate
```

The command accepts `--account <name>`. The agent API rotates the key under a per-agent lock, preserves the allowance, and removes older non-top-up stake keys after minting the replacement.

The linked-agent rotation endpoint is:

```http
POST /api/agents/self/router-key
```

Linked agents can mint or rotate a balance key with the `router.use` scope through:

```http
POST /api/agents/self/router-balance-key
```

See [Usage and limits](/router/usage-and-limits.md) for the daily window and usage view.

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/access-and-keys.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.