Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Triumph

Triumph (Triumph Labs, formerly Triumph Arcade) is a consumer entertainment and commerce company backed by General Catalyst, which led its $10.2M Series A — part of the $14.1M the company launched with in May 2023. Triumph began as an iOS/Unity SDK that let game developers add real-money tournaments to their games, handling payments, state-by-state regulatory eligibility (37 US states plus DC at launch), matchmaking, and payouts, and today operates two consumer apps: Triumph: Play for Cash (competitive cash gaming arcade) and Rips by Triumph (trading-card collectibles). The Triumph SDK for Swift and Unity remains documented at docs.triumpharcade.com and is distributed via CocoaPods and GitHub, with a developer dashboard at dashboard.triumpharcade.com; the company publishes no public REST API.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Triumph the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Triumph scores 27.5/100 (emerging), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 27.5/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 10.4 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Payments 6.5 / 15
Agent readiness — 10/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Triumph

Each block below is one kind of artifact we hold for Triumph. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Triumph Authentication

sdk-credentials · 5 schemes

SECURITY

Triumph Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Triumph — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/triumph · machine-readable index on apis.io