Samaya AI · OAuth Scopes

Samaya AI OAuth Scopes

OAuth 2.0 probed

Samaya AI 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.

Artificial IntelligenceFinancial-ServicesInvestment ResearchAI AgentsMCPagent-nativeCapital MarketsEnterprise SearchRetrievalGraphQL
Scopes: 0 Flows: Method: probed

Scopes (0)

Samaya AI 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.

Samaya's MCP authorization server publishes RFC 9728 protected-resource metadata with an EMPTY scopes_supported array, and the RFC 8414 authorization-server document declares no scopes_supported key at all. This is a measured absence, not an unchecked field: the server runs OAuth 2.1 with dynamic client registration and PKCE S256 but exposes no granular permission vocabulary, so an agent connecting to it cannot request or be granted least privilege at the protocol level. The published REST OpenAPI declares no oauth2 securityScheme (it uses a WorkOS bearer token), so it contributes no scopes either.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-26'
method: probed
source: https://mcp.samaya.ai/.well-known/oauth-protected-resource/mcp
scope_count: 0
scopes: []
note: >-
  Samaya's MCP authorization server publishes RFC 9728 protected-resource metadata with an EMPTY
  scopes_supported array, and the RFC 8414 authorization-server document declares no scopes_supported
  key at all. This is a measured absence, not an unchecked field: the server runs OAuth 2.1 with
  dynamic client registration and PKCE S256 but exposes no granular permission vocabulary, so an
  agent connecting to it cannot request or be granted least privilege at the protocol level. The
  published REST OpenAPI declares no oauth2 securityScheme (it uses a WorkOS bearer token), so it
  contributes no scopes either.
authorization_server:
  issuer: https://mcp.samaya.ai/
  authorization_endpoint: https://mcp.samaya.ai/authorize
  token_endpoint: https://mcp.samaya.ai/token
  registration_endpoint: https://mcp.samaya.ai/register
  revocation_endpoint: https://mcp.samaya.ai/revoke
  code_challenge_methods_supported:
  - S256
docs: null
evidence:
- url: https://mcp.samaya.ai/.well-known/oauth-protected-resource/mcp
  status: 200
  scopes_supported: []
- url: https://mcp.samaya.ai/.well-known/oauth-authorization-server
  status: 200
  scopes_supported: absent

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/samaya-ai-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 email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.