Adopters

Platforms, tools, apps, and agents that have adopted Cambridge TCG standards. Empty today. The registry grows by self-declaration — the first adopter is welcome to land here.

Parent: /standards · Doctrine: docs/connections/the-distributor.md · License: CC0 1.0 Universal

No adopters yet

That's honest. The standards shipped this week; the registry is fresh ground.

Be the first.If your platform uses any of the three standards (CTCG-SKU-v1, CTCG-PRICING-v1, CTCG-UNIVERSAL-v1), you're welcome to declare it here.

How to declare

Adopt one or more of the standards (see /standards).
Make sure your implementation emits canonical forms (the reference impl at packages/sku/ handles this).
Send a note via the platform's support channel (email or repo issue) including: your platform's name, URL, kind, and which standards you adopted.
We add you to this registry, no other gate. You appear by your own description, not our classification.

Future automation: the protocol will move to a self-service POST endpoint at /api/v1/identify with kind: "adopter". See docs/connections/the-self-identification.md for the doctrine. Today: a manual message to support is the path.

What this registry is for

Adopterscan point their users at this page: "we use Cambridge TCG standards; here's the list of platforms that also do." Interop becomes visible.
Cambridge TCGlearns who's using the standards. This informs version-2 design — partner consultation becomes possible.
The TCG community can see standardisation actually happening, not just being announced. Network effects need a visible network.
Future Sophiassee the pantry's reputation grow. Each row is a row of trust.

What this registry is NOT

Not a certification.Cambridge TCG doesn't audit adopters' implementations. Adoption is self-declared. If you say you adopted, we list you.
Not a partnership.Adopting CC0 standards doesn't create any commercial relationship. Partner-tier API access is a separate path (recursion target).
Not a paywall. Listing here is free and always will be.
Not exclusive. A platform can adopt our standards andany other's. Standards interop, not compete.

Empty registry, 2026-05-12. Honest about it. Substrate awaits adopters; the door is warm to the touch.

No adopters yet

That's honest. The standards shipped this week; the registry is fresh ground.

Be the first.If your platform uses any of the three standards (CTCG-SKU-v1, CTCG-PRICING-v1, CTCG-UNIVERSAL-v1), you're welcome to declare it here.

How to declare

Adopt one or more of the standards (see /standards).

Make sure your implementation emits canonical forms (the reference impl at packages/sku/ handles this).

Send a note via the platform's support channel (email or repo issue) including: your platform's name, URL, kind, and which standards you adopted.

We add you to this registry, no other gate. You appear by your own description, not our classification.

What this registry is for

Adopterscan point their users at this page: "we use Cambridge TCG standards; here's the list of platforms that also do." Interop becomes visible.

Cambridge TCGlearns who's using the standards. This informs version-2 design — partner consultation becomes possible.

The TCG community can see standardisation actually happening, not just being announced. Network effects need a visible network.

Future Sophiassee the pantry's reputation grow. Each row is a row of trust.

What this registry is NOT

Not a certification.Cambridge TCG doesn't audit adopters' implementations. Adoption is self-declared. If you say you adopted, we list you.

Not a partnership.Adopting CC0 standards doesn't create any commercial relationship. Partner-tier API access is a separate path (recursion target).

Not a paywall. Listing here is free and always will be.

Not exclusive. A platform can adopt our standards andany other's. Standards interop, not compete.

Empty registry, 2026-05-12. Honest about it. Substrate awaits adopters; the door is warm to the touch.