Dexi Net Authentication

generated: '2026-11-05'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.dexi.net/authentication.md
sources:
- https://docs.dexi.net/authentication.md
- https://docs.dexi.net/mcp/oauth.md
- https://docs.dexi.net/quickstart.md
- https://docs.dexi.net/mcp/getting-started.md
description: 'Dexi provides two authentication methods: OAuth 2.1 for MCP connections and personal API tokens used as Bearer tokens.'
schemes:
- type: oauth2
  name: MCP OAuth
  evidence: MCP clients never handle long-lived secrets. When a client first connects to `https://mcp.dexi.net/mcp`, it registers itself, opens
    your browser to a Dexi consent page, and receives short-lived tokens after you approve — the standard OAuth 2.1 flow, handled automatically
    by the client.
  flows:
  - authorization_code
  authorize_url: https://mcp.dexi.net/authorize
  scopes:
  - notes:read
  - notes:write
  - openid
  - email
  - profile
  how_to_obtain: Dynamic client registration via `POST /register` then run the browser‑based consent flow to receive an authorization code and
    exchange it for access (`dxm_…`) and refresh (`dxr_…`) tokens.
- type: http-bearer
  name: Personal API token
  evidence: 'A token authenticates **exactly one endpoint**: [`POST /api/v1/bookmarks/save`](https://docs.dexi.net/api/save-bookmark).'
  header: Authorization
  how_to_obtain: Create a token in Settings → API tokens; the token is a 44‑character string starting with `dxi_` shown once at creation.
docs: https://docs.dexi.net/authentication.md