> 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/agents/control/owner-and-agents.md).

# Owner and agents

Agents is coming soon; owners will link, limit, pause, or revoke agents without giving them control of the owner wallet.

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

This page is for owners who want to link, limit, pause, or revoke local agents without giving them control of the owner's wallet.

The owner controls the vAPI account, while each agent uses a separate local wallet. This keeps account permissions and wallet control separate.

## Link an agent

As the owner, you sign in to the console with your wallet. You can use any wallet you control, and the client creates separate agent wallets on your machine.

Start a link for the selected agent wallet:

```bash
vapi login --account <name>
```

The terminal shows a code and a URL. Open `https://api.vapinetwork.ai/link?code=...`, approve with your wallet, and set the agent's daily Router allowance in USD. The code lasts 20 minutes.

On a device the owner trusts, later links can complete without the browser step, and the terminal prints `Linked on this trusted device`. The client must request trusted-device linking with a bearer token from an account already linked on that device. Requested permissions must fit that token's scopes. The requested Router allowance must fit the trusted allowance.

The default link gives the agent `mcp:call` and `router.use` rights on your account. Add publishing rights when you start the link:

```bash
vapi login --account <name> --publish
```

This adds the optional `call.publish` scope. These scopes grant rights on your account, never on your wallet.

Agents run on your own machines with their own wallets. They can use vAPI on your account within the limits you set. They can never move money from your wallet.

## Fund and sweep

Funding is push-only. You send USDC to the agent's address. The funding command prints the funding page:

```bash
vapi fund --account <name>
```

To send the agent wallet's USDC back to the linked owner, omit the destination address:

```bash
vapi sweep --account <name>
```

## Check or revoke a link

Check the owner link and its permissions:

```bash
vapi whoami --account <name>
```

The result includes the link and either `Status: active` or `Status: revoked`.

In the console, open **My agents** at `/agents`. You can use **Change allowance** or **Revoke** in one click. You can also revoke or remove a local link from the CLI:

```bash
vapi agent revoke <name>
vapi logout --account <name>
```

Relinking an agent wallet revokes its previous link. One owner can have at most 20 linked agents.

The agent's tokens and Router key live in the OS secret store under the wallet name, never in a file.

## Next

* [How wallets work](/agents/wallets/how-wallets-work.md)
* [Limits and ceilings](/agents/wallets/limits-and-ceilings.md)
* [Agents and Router HTTP API](https://docs.vapinetwork.ai/reference/http-api/agents-and-router)

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/agents/control/owner-and-agents.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.