# The best X12 reference on the internet is free. The join it describes is unbuilt.

*31 July 2026 · the launch journal*

Three facts, each checkable today, that together explain why [the business-transaction layer](/business-transactions/) exists.

**Fact one: the best public X12 reference is free, and Stedi built it.** Segment listings, mandatory/optional flags, max-use counts, the HL loop hierarchies — across releases, at stable URLs, with a footer that says it is provided free of charge. It is the craft benchmark for reference publishing in this field, and every X12 page this site ever ships will link it for element-level detail rather than reproduce it: [stedi.com/edi/x12-004010/856](https://www.stedi.com/edi/x12-004010/856). Credit where it is due.

**Fact two: the company that built it went somewhere else — and won.** Stedi today calls itself the only programmable healthcare clearinghouse: eligibility checks, claims, a payer network in the thousands, $142M raised through a March 2026 Series C, transaction volume compounding year over year. That is a serious business, built on serious discipline. Its product surface is healthcare X12 — 270/271, 837, 835. The supply-chain documents its own reference describes so well — the 850, the 856, the 810 — are not what it sells.

**Fact three: nobody in developer EDI ships an EPCIS product.** Survey the field — the translation APIs, the managed-service providers, the parser libraries — and you find document-in, document-out machinery everywhere, and the join from documents to standardized *events* nowhere. Yet the standard for that join has existed since 2022: CBV 2.0 §7.3 defines `po`, `desadv`, `inv` and `recadv` as first-class business-transaction types, and §8.5 puts `bizTransactionList` on every EPCIS event type. The vocabulary was standardized before the market noticed the gap.

So the ground is open exactly where the standards already pave it: purchase orders, despatch advices and invoices — X12, EDIFACT, or plain JSON — compiled down to `bizTransaction` references, party GLNs and GTIN-grain lists on conformant EPCIS 2.0 events. The reference craft Stedi proved on the syntax side, applied to the join side, with the licensing posture that keeps it publishable: [EDIFACT dictionary-deep under committed per-file pins](/business-transactions/), X12 in our own words with links out, grammars self-authored and provenance-pinned.

The door is [/business-transactions/](/business-transactions/). The spec argument, with citations, is [the thesis page](/business-transactions-in-epcis/).

*Sources: stedi.com (product surface and reference pages, checked 2026-07-31); stedi.com/blog/series-c (March 2026, $142M total); CBV 2.0 §7.3 and §8.5 (GS1, ref.gs1.org).*

---

**Proof, not adjectives.** This build could not verify the gateway's test suite green, so no sentence on this page claims a passing run — the last verified run is recorded in the repository's own CI, not here. Live on this origin, no key: POST /translate, /validate, /hash. No conformance attestation has ever been issued. The dated ledger is /what-ships-today/.