Samu · OAuth Scopes

Samu OAuth Scopes

OAuth 2.0 probed

Samu publishes 1 OAuth 2.0 scope via the authorizationCode and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Samu API on a user’s behalf.

Tokens are issued from https://api.samu.ai/oauth/token.

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.

CompanyArtificial IntelligenceSalesSales IntelligenceConversation IntelligenceCRMCall RecordingAnalyticsLatin AmericaTranscriptionWhatsAppMCPagent-native

Scopes: 1 Flows: authorizationCode, refreshToken Method: probed

OAuth endpoints

Authorization URL
https://api.samu.ai/oauth/authorize

Token URL
https://api.samu.ai/oauth/token

Flows
authorizationCoderefreshToken

Scopes (1)

Scope	Description	Flows
mcp:read	The only scope advertised in scopes_supported. Read access for MCP clients to the Samu MCP server. Samu publishes no per-scope description; this is the scope string verbatim from the authorization-server metadata.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://api.samu.ai/.well-known/oauth-authorization-server
note: >-
  Samu's OpenAPI declares only an apiKey scheme and has no oauth2 flows, so
  derive-oauth-scopes.py found nothing. The OAuth surface is real but lives
  entirely in the MCP authorization server metadata on api.samu.ai, which is
  served anonymously and is captured verbatim in well-known/. Samu publishes no
  human-readable scope reference page.
schemes:
- name: MCP OAuth 2.1
  source: well-known/samu-oauth-authorization-server.json
  issuer: https://api.samu.ai
  protected_resource: https://api.samu.ai/mcp
  dynamic_client_registration: https://api.samu.ai/oauth/register
  code_challenge_methods: [S256]
  token_endpoint_auth_methods: [none]
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.samu.ai/oauth/authorize
    tokenUrl: https://api.samu.ai/oauth/token
    revocationUrl: https://api.samu.ai/oauth/revoke
  - flow: refreshToken
    tokenUrl: https://api.samu.ai/oauth/token
scopes:
- scope: mcp:read
  description: >-
    The only scope advertised in scopes_supported. Read access for MCP clients to
    the Samu MCP server. Samu publishes no per-scope description; this is the
    scope string verbatim from the authorization-server metadata.
  flows: [authorizationCode]
  sources: [well-known/samu-oauth-authorization-server.json]
x-evidence:
  fetched: '2026-08-13'
  url: https://api.samu.ai/.well-known/oauth-authorization-server
  http_status: 200
  content_type: application/json

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