Episode Six website screenshot

Episode Six

Episode Six is a global payment technology company founded in 2015 by John Mitchell, Chermaine Hu and Futeh Kao that supplies banks, fintechs and brands with a cloud-native card issuing and ledger management platform marketed as TRITIUM. The platform is described by the company as an API-first open architecture delivering real-time RESTful API processing for credit, debit, prepaid, commercial, installment and virtual card programs alongside a parallel ledger supporting virtual accounts, revolving credit, installments, loans, interest-bearing and term deposits, multi-currency and negative balance accounts. Episode Six operates in 45+ countries with staff in 20 countries, and states it is a PCI DSS Level 1 Service Provider that is SOC 2 Type II audited and uses GDPR as its global data baseline. Its API documentation is published at docs.episodesix.com behind an access-code gate, so no public OpenAPI is available.

Episode Six publishes 2 APIs on the APIs.io network. Tagged areas include Company, Payments, Card Issuing, Issuer Processing, and Ledger.

Episode Six’s developer surface includes documentation, signup flow, support, engineering blog, authentication, and 19 more developer resources.

24.5/100 emerging ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessApproval
2 APIs 1 MCP Servers
CompanyPaymentsCard IssuingIssuer ProcessingLedgerBankingFinancial-ServicesEmbedded FinanceFintechVirtual AccountsVirtual CardsCreditPrepaidMulti-Currency

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/episode-six: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Episode Six TRITIUM Platform API

The TRITIUM platform API is Episode Six's real-time RESTful interface for card issuing, issuer processing and ledger management — card program setup, account and ledger operatio...

Episode Six Documentation MCP Server

A Model Context Protocol server published by Episode Six on its own documentation host at https://docs.episodesix.com/mcp, exposing the TRITIUM developer documentation to agents...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Episode Six MCP Server

A Model Context Protocol server Episode Six serves from its own documentation host. It exposes the TRITIUM developer documentation to agents. It is not a TRITIUM platform (card ...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Episode Six Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Episode Six Authentication

oauth2 · 1 scheme

SECURITY

Episode Six Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Episode Six Scopes

1 scope · authorizationCode/clientCredentials

1 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: episode-six
name: Episode Six
description: Episode Six is a global payment technology company founded in 2015 by John Mitchell, Chermaine Hu and Futeh Kao
  that supplies banks, fintechs and brands with a cloud-native card issuing and ledger management platform marketed as TRITIUM.
  The platform is described by the company as an API-first open architecture delivering real-time RESTful API processing for
  credit, debit, prepaid, commercial, installment and virtual card programs alongside a parallel ledger supporting virtual
  accounts, revolving credit, installments, loans, interest-bearing and term deposits, multi-currency and negative balance
  accounts. Episode Six operates in 45+ countries with staff in 20 countries, and states it is a PCI DSS Level 1 Service Provider
  that is SOC 2 Type II audited and uses GDPR as its global data baseline. Its API documentation is published at docs.episodesix.com
  behind an access-code gate, so no public OpenAPI is available.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Requires approval
  confidence: medium
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
image: https://episodesix.com/hubfs/Home%20Page%20Featured%20Image%20Oct2025.png
url: https://raw.githubusercontent.com/api-evangelist/episode-six/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment
specificationVersion: '0.23'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Payments
- Card Issuing
- Issuer Processing
- Ledger
- Banking
- Financial-Services
- Embedded Finance
- Fintech
- Virtual Accounts
- Virtual Cards
- Credit
- Prepaid
- Multi-Currency
tags_raw:
- Company
- Payments
- Card Issuing
- Issuer Processing
- Ledger
- Banking
- Financial Services
- Embedded Finance
- FinTech
- Virtual Accounts
- Virtual Cards
- Credit
- Prepaid
- Multi-Currency
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: episode-six-tritium-platform-api
  name: Episode Six TRITIUM Platform API
  description: The TRITIUM platform API is Episode Six's real-time RESTful interface for card issuing, issuer processing and
    ledger management — card program setup, account and ledger operations, transaction processing and product configuration.
    Episode Six markets it as an "API-first open platform architecture" with a "vast, intuitive payments API library." The
    reference is served from docs.episodesix.com, which is gated behind an access code obtained through the company's access-request
    form, so no OpenAPI, base URL or authentication reference is publicly observable.
  humanURL: https://docs.episodesix.com/
  x-base-url-status: not-published
  x-base-url-note: Episode Six does not publish an API base URL on any public page. The documentation host docs.episodesix.com
    307-redirects every path to /login, so the real host is not observable without an access code. Recorded as missing rather
    than guessed.
  tags:
  - Payments
  - Card Issuing
  - Issuer Processing
  - Ledger
  properties:
  - type: Documentation
    url: https://docs.episodesix.com/
  - type: DeveloperPortal
    url: https://episodesix.com/platform/developers
  - type: SignUp
    url: https://episodesix.com/access-request
- aid: episode-six-docs-mcp
  name: Episode Six Documentation MCP Server
  description: A Model Context Protocol server published by Episode Six on its own documentation host at https://docs.episodesix.com/mcp,
    exposing the TRITIUM developer documentation to agents. The endpoint answers a JSON-RPC tools/list with HTTP 401 invalid_token,
    and advertises OAuth 2.0 authorization-server metadata (RFC 8414) at /.well-known/oauth-authorization-server plus protected-resource
    metadata (RFC 9728), with a single scope of mcp:search, PKCE S256, and dynamic client registration.
  humanURL: https://docs.episodesix.com/
  baseURL: https://docs.episodesix.com/mcp
  tags:
  - MCP
  - Documentation
  - Agents
  properties:
  - type: MCPServer
    url: mcp/episode-six-mcp.yml
  - type: OAuthScopes
    url: scopes/episode-six-scopes.yml
  - type: Authentication
    url: authentication/episode-six-authentication.yml
common:
- type: DomainSecurity
  url: security/episode-six-domain-security.yml
- type: Website
  url: https://episodesix.com/
- type: DeveloperPortal
  url: https://episodesix.com/platform/developers
- type: Documentation
  url: https://docs.episodesix.com/
- type: SignUp
  url: https://episodesix.com/access-request
- type: Support
  url: https://episodesix.com/contact-us
- type: Blog
  url: https://buzz.episodesix.com/
- type: BlogRSS
  url: https://buzz.episodesix.com/rss.xml
- type: PrivacyPolicy
  url: https://episodesix.com/privacy-policy
- type: CookiePolicy
  url: https://episodesix.com/cookie-policy
- type: Careers
  url: https://episodesix.com/company/careers
- type: Newsroom
  url: https://episodesix.com/newsroom
- type: Compliance
  url: https://episodesix.com/platform/paymentsecurity
- type: Conformance
  url: conformance/episode-six-conformance.yml
- type: MCPServer
  url: mcp/episode-six-mcp.yml
- type: OAuthScopes
  url: scopes/episode-six-scopes.yml
- type: Authentication
  url: authentication/episode-six-authentication.yml
- type: WellKnown
  url: well-known/episode-six-well-known.yml
- type: LLMsTxt
  url: llms/episode-six-llms.txt
- type: Packages
  url: packages/episode-six-packages.yml
- type: Plans
  url: plans/episode-six-plans-pricing.yml
- type: RateLimits
  url: rate-limits/episode-six-rate-limits.yml
- type: Lifecycle
  url: lifecycle/episode-six-lifecycle.yml
- type: ForgeGlobalListing
  url: https://forgeglobal.com/episode-six_stock/
x-enrichment:
  date: '2026-08-12'
  status: minimal
  artifacts_added: 11
  pass: local-v1
x-coverage:
  state: gated
  reason: sales-gate
  detail: The TRITIUM API reference at docs.episodesix.com answers every path with an "Access Restricted — provide your access
    code" screen and 307-redirects docs.json, llms.txt and every deep path to /login, with the only route in being the "Request
    access to our documentation and APIs" contact-sales form at episodesix.com/access-request.
  evidence:
  - url: https://docs.episodesix.com/docs.json
    status: 307
  - url: https://docs.episodesix.com/llms.txt
    status: 307
  - url: https://docs.episodesix.com/
    status: 200
  - url: https://episodesix.com/access-request
    status: 200
  checked: '2026-08-12'

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/episode-six"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/episode-six/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/episode-six/evidence"

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.

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