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 is listed with 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.

🌐 Visit website 📡 Profile data on GitHub

22.5/100 emerging ▬ flat Agent 25/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessApproval

2 APIs 1 MCP Servers

Company Payments Card IssuingIssuer ProcessingLedger Banking Financial Services Embedded Finance Fintech Virtual Accounts Virtual Cards Credit Prepaid Multi-Currency

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 22.5/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 5.4 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.5 / 9

Regulatory Posture 4.8 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/episode-six/"><img src="https://apis.io/badge/episode-six/card.svg" alt="Episode Six on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 28.6 — up to +14.3 composite points
Access Clarity scores 31.6 — up to +13.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/episode-six/apis.yml: open an issue on github.com/api-evangelist/episode-six to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	19.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

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

Episode Six API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Episode Six Plans Pricing

0 plans

PLANS

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

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Compliance

OAuthScopes

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 5

The organization behind the API

Website

Blog

BlogRSS

Careers

Newsroom

Other 2

Properties that don't map to a standard resource type

CookiePolicy

CookiePolicy

ForgeGlobalListing

ForgeGlobalListing

Source (apis.yml)

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
  probe_state: gated
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  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'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: vercel
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
- Financial-Services
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: episode-six: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: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'

Episode Six API — frequently asked questions

Does Episode Six have an API?

Yes. APIs.io lists 2 APIs from Episode Six, including Episode Six TRITIUM Platform API and Episode Six Documentation MCP Server.

How do I authenticate with the Episode Six API?

Episode Six documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Episode Six Authentication.

Does Episode Six have an MCP server?

Yes. APIs.io lists 1 MCP server for Episode Six: 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 issuing / ledger) MCP s

Is the Episode Six API ready for AI agents?

Episode Six has a Kin Score of 22.5 out of 100 (emerging) and an Agent Readiness score of 24.7 (agent-aware), scored by API Evangelist on 2026-11-06.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.