Evermuse · Authentication Profile

Evermuse Authentication

Authentication

Evermuse secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyProduct ManagementCustomer FeedbackVoice of CustomerArtificial IntelligenceData IngestionProduct AnalyticsMCPDeveloper Tools

Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in: header

Security Schemes

IngestApiKey apiKey

· in: header (x-api-key)

EvermuseOAuth oauth2

scheme: authorization_code · flows: authorizationCode

Source

Authentication Profile

generated: '2026-07-19'
method: searched
source: openapi/evermuse-ingest-v1-openapi-original.yml
docs: https://docs.evermuse.com/authentication
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
schemes:
- name: IngestApiKey
  type: apiKey
  in: header
  parameter: x-api-key
  description: |-
    Workspace-scoped API key, sent as the `x-api-key` header. Keys are prefixed
    `em_sk_` and created in Settings > API Keys. Each workspace can hold up to 10 keys.
    The Ingestion API requires the `api:write` permission (`api:read` keys get 403).
  sources:
  - openapi/evermuse-ingest-v1-openapi-original.yml
  - https://docs.evermuse.com/authentication
- name: EvermuseOAuth
  type: oauth2
  scheme: authorization_code
  description: |-
    OAuth 2.1 protects the hosted Evermuse MCP server (https://api.evermuse.com/api/mcp).
    Authorization Server metadata is published at
    /.well-known/oauth-authorization-server (RFC 8414) and the protected resource at
    /.well-known/oauth-protected-resource (RFC 9728). PKCE (S256) is required and
    Dynamic Client Registration is supported (RFC 7591) at /oauth/register.
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.evermuse.com/oauth/authorize
    tokenUrl: https://api.evermuse.com/oauth/token
    registrationUrl: https://api.evermuse.com/oauth/register
    pkce: S256
    scopes:
    - mcp:read
    - mcp:write
    - mcp:thirdparty
  sources:
  - well-known/evermuse-oauth-authorization-server.json
  - well-known/evermuse-oauth-protected-resource.json
permissions:
- key: api:read
  description: Read access to API endpoints (e.g. checking batch status).
- key: api:write
  description: Write access to API endpoints. Required for the Ingestion API.
- key: mcp:read
  description: Read access via MCP. Requires a default product.
- key: mcp:write
  description: Write access via MCP. Requires a default product.

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/evermuse-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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