Creating a key
Click to open Create API Key, give it a name — “e.g. Oviond, Production” — choose its Access, and create it. The confirmation reads “API key created”.
Give a reporting tool such as Oviond a Read Only key. If it ever leaks, nothing can be changed or spent with it.
Name keys after where they’re used. When you later need to revoke one, the name is all you have to work out what will break.
Using the key
Send it in theX-API-Key header against the REST API:
The MCP snippets on this screen don’t work
The creation screen shows three copy-able snippets: aclaude mcp add command, an mcpServers JSON block, and a curl example. Only the curl one is correct.
The correct MCP configuration is just the URL:
What a key can do
A key authenticates as the organization, not as the person who created it. It reaches every project in the organization, and it isn’t limited by the creating member’s role.- A Read Only key reads. Anything else — a write, or a call that spends — answers
403with “This API key is read-only.” - A Full Access key acts as an owner: it can do anything an owner can, including deleting projects.
One key per use
Create a separate key for each consumer — your CI pipeline, a scheduled job, a production integration. It costs nothing and means you can revoke one without taking down everything else. AI clients don’t need a key at all; they authenticate through OAuth.Related
- Manage API keys — review keys and their last-used dates
- Revoke or delete an API key — stop a key immediately
- API authentication — using the key against the REST API
- Connect the MCP server — which needs no key