IPstack · OAuth Scopes

IPstack OAuth Scopes

OAuth 2.0 probed

IPstack publishes 5 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the IPstack API on a user’s behalf.

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.

GeocodingIP GeolocationLocationThreat IntelligenceNetworkingMCPPublic APIs

Scopes: 5 Flows: Method: probed

Scopes (5)

Scope	Description	Flows
openid	Standard OpenID Connect scope; requests an ID token.
offline	Requests a refresh token (Ory/Hydra-style alias of offline_access).
offline_access	Standard OIDC scope requesting a refresh token for long-lived agent sessions.
mcp:read	Read access through the APILayer MCP server. Advertised by the protected-resource document at mcp.apilayer.com as one of the two scopes that endpoint accepts.
api:ipstack	Access to the IPstack product surface through an APILayer token. The only product-named scope in the discovery document.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-04'
method: probed
source: >-
  https://auth.apilayer.com/.well-known/oauth-authorization-server (HTTP 200) and
  https://mcp.apilayer.com/.well-known/oauth-protected-resource (HTTP 200). Both fetched
  anonymously on 2026-09-04 and saved verbatim under well-known/. derive-oauth-scopes.py
  produced nothing because no OpenAPI with oauth2 securitySchemes is published.
name: IPstack / APILayer OAuth scopes
description: >-
  The APILayer authorization server publishes its scope list in discovery. Two of the five
  scopes are product scopes and one of them names IPstack explicitly — api:ipstack — which
  is also the ownership proof that mcp.apilayer.com is IPstack's own agent surface and not
  a sibling product's.
issuer: https://auth.apilayer.com
resource: https://mcp.apilayer.com/mcp
scopes:
  - name: openid
    description: Standard OpenID Connect scope; requests an ID token.
    source: authorization-server metadata scopes_supported
  - name: offline
    description: Requests a refresh token (Ory/Hydra-style alias of offline_access).
    source: authorization-server metadata scopes_supported
  - name: offline_access
    description: Standard OIDC scope requesting a refresh token for long-lived agent sessions.
    source: authorization-server metadata scopes_supported
  - name: mcp:read
    description: >-
      Read access through the APILayer MCP server. Advertised by the protected-resource
      document at mcp.apilayer.com as one of the two scopes that endpoint accepts.
    source: both authorization-server and protected-resource metadata
  - name: api:ipstack
    description: >-
      Access to the IPstack product surface through an APILayer token. The only
      product-named scope in the discovery document.
    source: both authorization-server and protected-resource metadata
docs: null
note: >-
  APILayer publishes no human-readable scopes/permissions reference page; the scope list
  exists only in the machine-readable discovery documents. That is recorded as an honest
  gap rather than filled in.

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