Skip to main content
An agent reaches your CanvasView organization in one of two ways. Both are managed on the API keys page.
  • Connected agents sign in through your browser. Claude Code and Codex connect this way. See Connect your agent.
  • Manual API keys are for scripts, headless agents and MCP clients that cannot sign in through a browser.
Everything an agent does is billed to the organization’s credits.

Who manages what

Every key and connected agent belongs to the person who created it.
  • Members see, create, revoke and reconnect their own keys and connected agents.
  • Admins see and manage everyone’s. Each key someone else created shows that person’s email.
An agent acts for the person who created its key or connected it, with that person’s role:
  • The canvases it creates are owned by that person.
  • A Member’s agent sees the canvases that Member can see: their own, and those shared with the organization. An Admin’s agent sees every canvas in the organization.
  • Events follow the same rule. A Member’s agent gets events only for canvases that Member can see.
See Sharing and access and Organizations and members.

Connected agents

A connected agent appears under Connected agents after you approve it in your browser. Claude Code and Codex are shown by name. Each person who connects an agent gets their own connection. A connected agent works in your default organization: the first organization you used CanvasView in. If you leave that organization, it moves to another one you belong to. To work in a different organization from a script or agent, create a manual API key while that organization is the one shown in the account menu. To disconnect an agent:
  1. Select Disconnect next to it.
  2. Select Disconnect now to confirm.
The agent loses access at once. Signing in again from the agent does not restore it. To let it back in, select Reconnect.

Manual API keys

A manual key belongs to the organization you are working in when you create it. To create a key:
  1. Under Manual API keys, enter a Key name that says where you will use it.
  2. Select Create key.
  3. Copy the key. It starts with cvk_ and is shown only once.
Send the key as a bearer token:
The list shows each key’s name, a short prefix to recognise it by, and whether it is Active or Revoked. An organization can have up to 50 active manual keys. To revoke a key, select Revoke, then Revoke now. Anything using the key stops working at once. A revoked key cannot be restored. Create a new key instead.
Treat a key like a password. Keep it out of source control and chat. If a key leaks, revoke it and create a new one.
When someone leaves the organization or is removed, the keys and connected agents they created there are revoked. See Organizations and members.

Cap a key’s spending

Admins see a Daily cap (USD) field on each active key and connected agent. Enter an amount and select Save key cap to limit what that key or agent spends each day. Leave the field empty for no key cap. The organization’s daily cap applies as well. See Credits and billing.

Troubleshooting