Authentication and permissions
Give each client the access it needs and keep account management separate from tool execution.
View as MarkdownCreate a scoped API key
Sign in to the website and create a key in API keys. Query permission allows search and retrieval tools; Generate allows generation and transformation tools. Query calls may still cost money.
Read access to the catalog, balance and existing results does not by itself grant every execution capability. When creating a key with the API, omit toolIds to allow all tools within its scopes, or send an empty array to allow zero tools. The API saves repeated tool IDs once, in first-seen order. An unknown ID rejects the whole request.
Authorization: Bearer <your API key>Use the right credential
Signing into the website does not automatically connect a separate agent. Configure the agent's own API key or OAuth connection. Your account credentials do not grant access to arbitrary wallet-funded Runs.
| Credential | Use |
|---|---|
| Website session | Manage your account, keys, spending settings and top-ups in the console. |
| API key | Call the API or a compatible MCP client with the key's tool permissions. |
| MCP OAuth token | Access the MCP server with the granted scopes and supported client configuration. |
Protect and recover access
- Keep keys in a secret store or private local configuration. Never place them in URLs, chat messages or public client code.
- Revoke an exposed key in the console and configure a replacement.
- After restoring authorized access, retrieve the existing Run ID. Do not create a new paid request just because the previous credential expired.