Verified
API key
The one credential every call to CPI carries.
The one credential every call to CPI carries. There is no separate client id, no OAuth handshake,
one key, sent as api_key on a plain REST call or as an Authorization: Bearer header over
MCP.
A key is minted with one of three scopes, Account, App (pinned to one project), or
Full Stack VPS (auto-issued on provisioning), and picks full access (everything the
account can do, except any method carrying private: true) or custom access (an explicit
allowlist you build in the key form). Creating a key requires identity verification first.
See Authentication for the full flow.