Reflexivity · OAuth Scopes
Reflexivity OAuth Scopes
OAuth 2.0
probed
Reflexivity 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.
CompanyFinancial-ServicesInvestment AnalysisMarket DataArtificial IntelligenceMachine-LearningFintechResearchKnowledge GraphAgents
Scopes: 0
Flows:
Method: probed
Scopes (0)
Reflexivity 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 verbatim from Reflexivity's own RFC 8414 Authorization Server Metadata document, which is served anonymously and enumerates scopes_supported. This is NOT derived from an OpenAPI spec — Reflexivity publishes no public OpenAPI, and the Theneo-hosted API reference is password-protected. Every scope below is the exact string the authorization server advertises. Descriptions are left empty rather than invented: the AS metadata carries no scope descriptions and the scope reference page is behind the documentation password. The naming is the finding — all 23 published scopes are namespaced `mcp:`, meaning Reflexivity's authorization surface is organised around Model Context Protocol services rather than around REST resources.
Read verbatim from Reflexivity's own RFC 8414 Authorization Server Metadata document, which is served anonymously and enumerates scopes_supported. This is NOT derived from an OpenAPI spec — Reflexivity publishes no public OpenAPI, and the Theneo-hosted API reference is password-protected. Every scope below is the exact string the authorization server advertises. Descriptions are left empty rather than invented: the AS metadata carries no scope descriptions and the scope reference page is behind the documentation password. The naming is the finding — all 23 published scopes are namespaced `mcp:`, meaning Reflexivity's authorization surface is organised around Model Context Protocol services rather than around REST resources.
📄 Provider scope reference: https://api-docs.tgl.ai/
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.