APIs.io · OAuth Scopes

APIs.io OAuth Scopes

OAuth 2.0 derived

APIs.io publishes 3 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the APIs.io API on a user’s behalf.

Tokens are issued from https://apis.io/api/v1/auth/token.

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 AggregationAPI DirectoryAPI DiscoveryAPI IndexingAPI RatingAPI SearchAPIs.jsonSearch EnginesAPI CatalogAgent DiscoveryMCPAgent SkillsOpenAPIAPI GovernanceA2A

Scopes: 3 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://apis.io/api/v1/auth/authorize

Token URL
https://apis.io/api/v1/auth/token

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
apis:pro	The tier-gated resources -- ratings, insights, demand depth, the Saved Workspace.	authorizationCode
apis:read	Read the catalog. Granted to every caller.	authorizationCode
offline_access	Issue a refresh token. Authorization-server scope only; no resource asks for it.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-11'
method: derived
source: openapi/apis-io-v1-openapi.yml
schemes:
- name: OAuth2
  source: openapi/apis-io-v1-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://apis.io/api/v1/auth/authorize
    tokenUrl: https://apis.io/api/v1/auth/token
  description: The machine path to the same tiers, and the better of the two options for an
    agent. APIs.io runs its own OAuth 2.1 authorization server -- RFC 8414 metadata at /.well-known/oauth-authorization-server,
    a JWKS at /.well-known/jwks.json, PKCE (S256 only), RFC 7591 dynamic client registration,
    and RFC 8707 resource indicators -- so a client can earn access through a protocol handshake
    instead of a human pasting a key. An access token resolves to the same tier and the same
    per-user quota as that user's API key. Declared here as of 2026-08-30; the server has been
    live since before that, and an agent reading this contract to decide how to authenticate
    could not previously discover it.
scopes:
- scope: apis:pro
  description: The tier-gated resources -- ratings, insights, demand depth, the Saved Workspace.
  flows:
  - authorizationCode
  sources:
  - openapi/apis-io-v1-openapi.yml
- scope: apis:read
  description: Read the catalog. Granted to every caller.
  flows:
  - authorizationCode
  sources:
  - openapi/apis-io-v1-openapi.yml
- scope: offline_access
  description: Issue a refresh token. Authorization-server scope only; no resource asks for
    it.
  flows:
  - authorizationCode
  sources:
  - openapi/apis-io-v1-openapi.yml

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/apis-io-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.