Aidentified · OAuth Scopes

Aidentified OAuth Scopes

OAuth 2.0 probed

Aidentified uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyData EnrichmentWealth ManagementFinancial-ServicesRelationship IntelligenceSales IntelligenceProspectingContact DataIdentity ResolutionMCP

Scopes: 0 Flows: Method: probed

Scopes (0)

Aidentified implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-14'
method: probed
source: >-
  https://login.aidentified.com/.well-known/oauth-authorization-server (HTTP 200) and
  https://login.aidentified.com/.well-known/openid-configuration (HTTP 200), both fetched
  2026-09-14 and saved verbatim under well-known/.
docs: null
docs_note: >-
  Aidentified publishes NO scopes or permissions reference page. These scopes were read from the
  provider's own live OAuth discovery documents, which is the authoritative machine-readable
  source, but a human integrator has nothing to read.
applies_to:
  resource: https://mcp.aidentified.com/mcp
  authorization_server: https://login.aidentified.com
  flows:
    - authorization_code
  pkce: S256

scopes:
  - name: openid
    description: Request an OpenID Connect ID token carrying the subject identifier.
    source: both
  - name: profile
    description: Basic profile claims for the authenticated Aidentified user.
    source: both
  - name: email
    description: Email address claim for the authenticated Aidentified user.
    source: both
  - name: phone
    description: Phone number claim for the authenticated Aidentified user.
    source: both
  - name: offline_access
    description: Issue a refresh token so an agent can act without re-prompting the user.
    source: both
  - name: full_access
    description: >-
      Full access. Advertised by the OpenID Connect discovery document only; absent from the RFC 8414
      authorization-server metadata. No published document defines what it grants.
    source: openid-configuration

scope_count: 6

findings:
  - >-
    The RFC 9728 protected-resource document for the MCP server declares scopes_supported as an EMPTY
    array, while the authorization server advertises six. An agent reading the resource metadata — the
    document the 401 challenge points it at — learns nothing about what to request.
  - >-
    Every scope except full_access is a standard OIDC identity scope. There is no API-capability scope
    (no read/write, no per-resource scope), so the token model is all-or-nothing with respect to
    Aidentified data.
  - >-
    full_access appears in only one of the two discovery documents and is undefined in prose anywhere.

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set 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 scope set

curl "https://apis.io/api/v1/scopes/aidentified-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.