Episode Six · OAuth Scopes

Episode Six OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://docs.episodesix.com/mcp/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.

CompanyPaymentsCard IssuingIssuer ProcessingLedgerBankingFinancial-ServicesEmbedded FinanceFintechVirtual AccountsVirtual CardsCreditPrepaidMulti-Currency

Scopes: 1 Flows: authorizationCode, clientCredentials Method: probed

OAuth endpoints

Authorization URL
https://docs.episodesix.com/mcp/oauth/authorize

Token URL
https://docs.episodesix.com/mcp/oauth/token

Flows
authorizationCodeclientCredentials

Scopes (1)

Scope	Description	Flows
mcp:search	Search the Episode Six TRITIUM developer documentation through the MCP server. This is the single scope advertised in scopes_supported; it bounds the MCP surface to documentation retrieval and grants no access to the payments platform.	authorizationCode, clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-12'
method: probed
source: https://docs.episodesix.com/.well-known/oauth-authorization-server
docs: null
docs_note: >-
  No public scopes or permissions reference exists. The only scope Episode Six publishes
  anywhere on a public surface is the one advertised in its MCP OAuth authorization-server
  metadata. The TRITIUM platform API scope model, if it has one, is behind the docs gate.
schemes:
- name: MCPOAuth2
  source: well-known/episode-six-oauth-authorization-server.json
  issuer: https://docs.episodesix.com/mcp/oauth
  applies_to: https://docs.episodesix.com/mcp
  flows:
  - flow: authorizationCode
    authorizationUrl: https://docs.episodesix.com/mcp/oauth/authorize
    tokenUrl: https://docs.episodesix.com/mcp/oauth/token
  - flow: clientCredentials
    tokenUrl: https://docs.episodesix.com/mcp/oauth/token
scopes:
- scope: mcp:search
  description: >-
    Search the Episode Six TRITIUM developer documentation through the MCP server. This is
    the single scope advertised in scopes_supported; it bounds the MCP surface to
    documentation retrieval and grants no access to the payments platform.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - well-known/episode-six-oauth-authorization-server.json
scope_count: 1
x-evidence:
  fetched: '2026-08-12'
  url: https://docs.episodesix.com/.well-known/oauth-authorization-server
  http_status: 200

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/episode-six-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.