APILayer · OAuth Scopes

APILayer OAuth Scopes

OAuth 2.0 probed

APILayer 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.

API MarketplaceAPI CatalogAPI DiscoveryDeveloper ToolsSaaS APIsGeolocationCurrencyData API
Scopes: 0 Flows: Method: probed

Scopes (0)

APILayer 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.

APILayer publishes no scopes reference page. This list is read verbatim from the OAuth authorization server metadata and the MCP protected-resource descriptor, which are the only places APILayer states its scopes. Scopes apply ONLY to the hosted MCP server; the REST product APIs use an unscoped account-wide access_key.

Source

OAuth Scopes

Raw ↑
generated: '2026-09-12'
method: probed
source: https://auth.apilayer.com/.well-known/openid-configuration and
  https://mcp.apilayer.com/.well-known/oauth-protected-resource
provider: APILayer
providerId: apilayer
note: >-
  APILayer publishes no scopes reference page. This list is read verbatim from the OAuth
  authorization server metadata and the MCP protected-resource descriptor, which are the only
  places APILayer states its scopes. Scopes apply ONLY to the hosted MCP server; the REST
  product APIs use an unscoped account-wide access_key.
authorization_server: https://auth.apilayer.com
protected_resource: https://mcp.apilayer.com/mcp
scopes:
  - name: openid
    description: Standard OpenID Connect scope; requests an ID token.
    source: authorization server metadata
  - name: offline_access
    description: Standard OAuth scope; requests a refresh token.
    source: authorization server metadata
  - name: offline
    description: Legacy alias for offline_access advertised alongside it.
    source: authorization server metadata
  - name: mcp:read
    description: Read access to the APILayer hosted MCP server.
    source: authorization server metadata and MCP protected-resource metadata
  - name: api:ipstack
    description: Access to the IPstack product through the MCP server.
    source: authorization server metadata and MCP protected-resource metadata
finding: >-
  The scope list is the strongest available evidence of how much of the marketplace the MCP
  server actually fronts. Exactly ONE product scope exists - api:ipstack - against a catalog of
  22 published OpenAPI documents. The MCP surface is an IPstack pilot, not a marketplace-wide
  agent door.
docs: null
checked: '2026-09-12'

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

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