Minds · Authentication Profile

Getminds Authentication

Authentication

Minds secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions.

Synthetic ResearchMarket ResearchSurveysUser ResearchMarketing Analyticsai-personasMCPAgent-NativeGDPR
Methods: http, oauth2 Schemes: 2 OAuth flows: API key in:

Security Schemes

ApiKeyAuth http
scheme: bearer
MCP OAuth2 oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-09-20'
method: searched
source: https://getminds.ai/docs/api/authentication
summary:
  types:
  - http
  - oauth2
  note: >-
    REST v1 API uses a personal API key sent as a bearer token. The MCP server
    (https://getminds.ai/mcp) is a separate protected resource that uses OAuth 2.0
    (or the same API key). The OpenAPI document itself is intentionally public.
schemes:
- name: ApiKeyAuth
  surface: rest
  type: http
  scheme: bearer
  bearerFormat: API Key
  key_prefix: minds_
  header: Authorization
  description: >-
    Personal API key sent as `Authorization: Bearer minds_…`. Keys are prefixed
    `minds_`, created at https://getminds.ai/settings/api-keys, shown once at
    creation, and never returned again. `GET /api/v1/auth/me` verifies a key.
    A missing/invalid/revoked key returns a generic 401 (the API deliberately
    does not distinguish among them).
  docs: https://getminds.ai/docs/api/authentication
  sources:
  - openapi/getminds-openapi.json
  - https://getminds.ai/docs/api/authentication
- name: MCP OAuth2
  surface: mcp
  type: oauth2
  flow: authorization_code
  pkce: S256
  dynamic_client_registration: true
  token_endpoint_auth_methods:
  - none
  authorization_endpoint: https://getminds.ai/oauth/authorize
  token_endpoint: https://getminds.ai/oauth/token
  registration_endpoint: https://getminds.ai/oauth/register
  revocation_endpoint: https://getminds.ai/oauth/revoke
  protected_resource: https://getminds.ai/mcp
  scopes:
  - sparks:read
  - sparks:write
  - sparks:chat
  - flows:read
  - flows:write
  description: >-
    RFC 9728 protected-resource metadata is served at
    /.well-known/oauth-protected-resource; the authorization server metadata
    (RFC 8414) and OpenID configuration are served on the same host. Public
    client (token_endpoint_auth_method none) with PKCE and dynamic client
    registration. The MCP server also accepts a Minds API key in place of OAuth.
  docs: https://getminds.ai/mcp/setup
  sources:
  - well-known/getminds-oauth-authorization-server.json
  - well-known/getminds-oauth-protected-resource.json
  - well-known/getminds-openid-configuration.json

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