Chamade · Authentication Profile

Chamade Io Authentication

Authentication

Authentication methods for Chamade

Chamade declares 2 security scheme(s) across its OpenAPI definitions.

Voice gatewayChat gatewayAI AgentsSIPSpeech API

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

Bearer token http-bearer

MCP OAuth 2.1 oauth2

· flows:

Source

Authentication Profile

generated: '2026-11-03'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://chamade.io/llms-setup.txt
sources:
- https://chamade.io/llms-setup.txt
- https://chamade.io/docs/quickstart
- https://chamade.io/docs/mcp
- https://chamade.io/docs/voice-providers
description: Authentication methods for Chamade
schemes:
- type: http-bearer
  name: Bearer token
  evidence: 'Auth is either a standard Authorization: Bearer chmd_* header (same API key as the REST API, best for config-file clients) or the
    MCP OAuth 2.1 flow with Dynamic Client Registration (used by claude.ai Custom Connectors — paste the URL, sign in, done).'
  location: header
  header: Authorization
  how_to_obtain: Mint an agent key on the dashboard (starts with chmd_) and place it after "Bearer " in the Authorization header.
- type: oauth2
  name: MCP OAuth 2.1
  evidence: Chamade runs an OAuth 2.1 authorization server (Dynamic Client Registration + PKCE) so the client registers itself on the fly, the
    user approves once in a consent screen at chamade.io/mcp-auth/consent, and an opaque access token is issued.
  location: header
  header: Authorization
  flows:
  - authorizationCode
  authorize_url: https://mcp.chamade.io/mcp-auth/consent
  how_to_obtain: Client initiates OAuth 2.1 flow with Dynamic Client Registration; user consents at the consent screen and receives an access
    token.
docs: https://chamade.io/llms-setup.txt

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/chamade-io-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.