Aeternity · OAuth Scopes

Aeternity OAuth Scopes

OAuth 2.0 probed

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

BlockchainLayer 1Smart ContractsCryptocurrencyWeb3Distributed LedgerOpen SourceGraphQLState ChannelsOracleNaming SystemDeveloper ToolsReal-Time
Scopes: 0 Flows: Method: probed

Scopes (0)

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

Neither OpenAPI declares an oauth2 securityScheme, so nothing was derivable from the specs (derive-oauth-scopes.py found 0 oauth2 schemes). The only OAuth surface æternity publishes is the MCP endpoint on aeternity.com, and its authorization-server metadata declares exactly one scope. No scope reference page exists in the documentation; these values are read verbatim from the served discovery documents, not inferred.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-12'
method: probed
source: https://aeternity.com/.well-known/oauth-authorization-server
note: >-
  Neither OpenAPI declares an oauth2 securityScheme, so nothing was derivable from the specs
  (derive-oauth-scopes.py found 0 oauth2 schemes). The only OAuth surface æternity publishes is the MCP
  endpoint on aeternity.com, and its authorization-server metadata declares exactly one scope. No scope
  reference page exists in the documentation; these values are read verbatim from the served discovery
  documents, not inferred.
authorization_server: https://aeternity.com
protected_resource: https://aeternity.com/wp-json/mcp/mcp-oauth-server
flows:
  authorization_code:
    authorization_endpoint: https://aeternity.com/oauth/authorize
    token_endpoint: https://aeternity.com/oauth/token
    revocation_endpoint: https://aeternity.com/oauth/revoke
    pkce: S256
    grant_types:
    - authorization_code
    - refresh_token
scopes:
- name: mcp
  description: >-
    The single scope advertised in scopes_supported by both the authorization-server metadata and the
    protected-resource metadata. The documents publish no description of what it grants, and the tool set it
    gates could not be enumerated anonymously.
  source: https://aeternity.com/.well-known/oauth-authorization-server
scope_count: 1

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