Ordex contract

Why this page is short

Ordex publishes its own OpenAPI document, SDK, conformance vectors, and purchase verifier. Copying them here would create a second version that can drift from the first. A drifted copy of a settlement contract is worse than no copy.

So this page points at the source and documents only the boundary.

Where the contract lives

Artefact	Path in the Ordex repository
OpenAPI document	spec/openapi.json
Lifecycle specification	spec/lifecycle.md
Purchase specification	spec/purchase.md
API reference	spec/api.md
Interoperability notes	spec/interoperability.md
Conformance vectors	conformance/purchase-vectors.json
Burn vectors	conformance/rune-burn-vectors.json
SDK	sdk/
Purchase verifier	verifier/

Repository: bitcoinuniverseio/ordex, pinned in this documentation at the revision shown in the source panel above.

The boundary

Concern	Owned by
The Ordex marketplace contract, its lifecycle, and its vectors	Ordex
Atomicals collateral verification for the four protocol lanes	Marketplace v1
Atomicals allocation and burn semantics	The protocol
Which Universe surface exposes which flow	Status and limitations

Where a Universe surface wraps Ordex, the wrapper is documented on the Universe side and the contract stays where it is defined.

What to do as an integrator

1. Take the OpenAPI document from the Ordex repository at a pinned revision.
2. Generate your client from that document rather than hand writing calls.
3. Run the Ordex conformance vectors against your build.
4. Use the Ordex verifier for purchase validation rather than reimplementing it.
5. For anything touching Atomicals collateral, read Marketplace v1 as well, because the collateral rules are enforced there.

Do not

• Do not assume an Ordex route behaves the same as a Marketplace v1 route with a similar name.
• Do not mix vectors from the two contracts.
• Do not treat an Ordex listing as evidence of Atomicals ownership. Ownership is verified at settlement, against the chain.