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.
Kin Score
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.yml
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Episode Six Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
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