Deliverd · Authentication Profile

Deliverd Dev Authentication

Authentication

Deliverd secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyAI AgentsHuman-in-the-LoopApprovalsMCPAgent GovernanceComplianceWorkflows

Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http

scheme: bearer

Source

Authentication Profile

generated: '2026-11-05'
method: searched
source: https://deliverd.dev/docs/developers/authentication
summary:
  types:
  - http
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: 'API key (dlv_…) created in Settings → API tokens, or an OAuth access token (dlvo_…). Every route
    below can answer `401 auth_error` — the credential was not accepted — or `403 insufficient_scope`, which is
    a different thing: the credential is fine and was not issued with the scope this route needs. Reissue it with
    that scope rather than replacing it with another of the same ones. Older clients may '
  sources:
  - openapi/deliverd-dev-openapi.yml
docs: https://deliverd.dev/docs/developers/authentication
tokens:
- kind: API key
  prefix: dlv_
  obtained: Created in the app (Settings → API tokens, or an agent page under Agents → Agents), or by deliverd login.
    Shown once.
  acts_as: The person who created it, or an agent identity.
- kind: OAuth access token
  prefix: dlvo_
  obtained: By an MCP client or connector, after you approve it in a browser.
  acts_as: The person who approved it.
oauth:
  used_by: MCP server (https://deliverd.dev/api/mcp); tokens also work on the REST API
  spec: MCP authorisation specification — discovery, dynamic client registration and PKCE
  membership_checked: on every request
env:
  DELIVERD_API_KEY: SDK key
  DELIVERD_BASE_URL: SDK address
  DELIVERD_URL / DELIVERD_TOKEN: CLI address and token
  DELIVERD_MODE: development = imaginary approver, no key, no network
scopes_ref: scopes/deliverd-dev-scopes.yml

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/deliverd-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.

GitHub Google LinkedIn

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