Buildonto Dev Authentication

generated: '2026-11-03'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.buildonto.dev/api/auth.md
sources:
- https://docs.buildonto.dev/api/auth.md
- https://docs.buildonto.dev/mcp/remote.md
- https://docs.buildonto.dev/quickstart.md
- https://docs.buildonto.dev/mcp/setup.md
description: Onto uses Bearer tokens for its Read API and an OAuth2 authorization code flow (PKCE) for the Remote connector.
schemes:
- type: http-bearer
  name: Read API key
  evidence: Every Read API request needs a Bearer token in the Authorization header.
  location: header
  header: Authorization
  how_to_obtain: Sign in at https://app.buildonto.dev, go to /read/keys and copy the displayed key (onto_sk_live_...).
- type: oauth2
  name: Remote connector (OAuth)
  evidence: One URL — https://api.buildonto.dev/mcp — and a sign‑in with your Onto account. No key to paste, nothing to install.
  flows:
  - authorization_code
  authorize_url: https://api.buildonto.dev/authorize
  scopes:
  - onto:read
  how_to_obtain: Run the client’s add command (e.g., $ claude mcp add --scope user --transport http onto https://api.buildonto.dev/mcp); the client
    will be redirected to Onto’s sign‑in page, approve the request, and receive an access token via the PKCE authorization‑code flow.
docs: https://docs.buildonto.dev/api/auth.md