Aiera · OAuth Scopes
Aiera OAuth Scopes
OAuth 2.0
probed
Aiera 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.
Financial ResearchEarnings CallsTranscriptsSEC FilingsMarket DataFinancial DataBroker ResearchExpert NetworksSpeech-to-TextFinancial-ServicesMCPagent-native
Scopes: 0
Flows:
Method: probed
Scopes (0)
Aiera 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.
The only OAuth surface Aiera publishes is the hosted MCP server at mcp-pub.aiera.com, and the only scopes it advertises are the three OIDC identity scopes. There is no resource-level or permission-level scope vocabulary: authorization to Aiera data is carried by the account's entitlements, not by OAuth scope. The REST API at premium.aiera.com is API-key authenticated and has no scope surface at all.
The only OAuth surface Aiera publishes is the hosted MCP server at mcp-pub.aiera.com, and the only scopes it advertises are the three OIDC identity scopes. There is no resource-level or permission-level scope vocabulary: authorization to Aiera data is carried by the account's entitlements, not by OAuth scope. The REST API at premium.aiera.com is API-key authenticated and has no scope surface at all.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.