AgentSmyth · OAuth Scopes
AgentSmyth OAuth Scopes
OAuth 2.0
probed
AgentSmyth 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 ServicesCapital MarketsArtificial IntelligenceAI AgentsTradingInvestment ResearchMarket IntelligenceMCPAgent-NativeFintech
Scopes: 0
Flows:
Method: probed
Scopes (0)
AgentSmyth 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.
Read from the provider's live OIDC discovery document, not from an OpenAPI - no OpenAPI is published. These are the only scopes the authorization server advertises. They are the standard OIDC identity set; no resource- or product-specific scopes (no read/write, no per-agent scopes) are published, so an agent cannot request least-privilege access to a named capability. If finer-grained scopes exist they are not in the public metadata.
Read from the provider's live OIDC discovery document, not from an OpenAPI - no OpenAPI is published. These are the only scopes the authorization server advertises. They are the standard OIDC identity set; no resource- or product-specific scopes (no read/write, no per-agent scopes) are published, so an agent cannot request least-privilege access to a named capability. If finer-grained scopes exist they are not in the public metadata.
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.