cubic · Authentication Profile

cubic Authentication

Authentication

cubic secures its APIs with http across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyArtificial IntelligenceCode ReviewDeveloper ToolsGitHubPull RequestsMCPAnalytics
Methods: http Schemes: 2 OAuth flows: API key in:

Security Schemes

apiKey http
scheme: bearer
mcp-oauth oauth2

Source

Authentication Profile

Raw ↑
generated: '2026-11-04'
method: searched
source: https://docs.cubic.dev/account/members-api
docs: https://docs.cubic.dev/account/members-api
summary:
  types:
  - http
schemes:
- name: apiKey
  type: http
  scheme: bearer
  header: Authorization
  format: 'Authorization: Bearer cbk_your_api_key'
  description: One key works for both the Members and Analytics APIs. Personal keys start with cbk_ and
    use the key owner's organization access; organization keys start with cok_, are created by an organization
    admin with Read or Admin access, and reach only their own organization. A Read organization key gets
    403 admin_required on PATCH. Analytics keys starting with cak_ keep working with the Analytics API
    but are no longer created. cubic shows the full key value only once.
  key_prefixes:
  - prefix: cbk_
    kind: personal
  - prefix: cok_
    kind: organization (read or admin)
  - prefix: cak_
    kind: legacy analytics key (Analytics API only, no longer issued)
  issued_at: https://www.cubic.dev/settings?tab=api-cli
  sources:
  - openapi/cubic-dev-openapi.yml
  - openapi/cubic-dev-analytics-openapi.yml
  - https://docs.cubic.dev/api-reference/overview.md
- name: mcp-oauth
  type: oauth2
  applies_to: MCP server https://www.cubic.dev/api/mcp
  description: The MCP server is connected by signing in with a cubic account from the MCP client; the
    docs warn that some clients compare the protected resource URL exactly, so use https://www.cubic.dev/api/mcp
    rather than https://cubic.dev/api/mcp. Not a REST API scheme.
  sources:
  - https://docs.cubic.dev/ide/mcp-server.md
key_types:
- name: Personal key
  prefix: cbk_
  issued_to: Any cubic user
  acts_as: You, with your own cubic access.
- name: Organization key
  prefix: cok_
  issued_to: An organization admin
  acts_as: One organization, with read or admin access to its members.
  access_levels:
  - Read
  - Admin
header: 'Authorization: Bearer cbk_your_api_key'
notes:
- Keys are shown in full only once; the same personal key is used by the CLI (CUBIC_API_KEY), MCP server,
  Members API and Analytics API.
- A Read organization key gets 403 admin_required on PATCH. No key can change billing.
- Legacy cak_ Analytics API keys keep working but are no longer issued.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/cubic-dev-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.