Catena-X is the automotive industry’s data space standard — a numbered library of CX-xxxx specifications published by Catena-X Automotive Network e.V. that define how a supply chain shares part data, carbon footprints, quality records and digital product passports without any participant handing over its data to a central platform. The standards are public and free to read on GitHub, the reference implementation is open source at the Eclipse Foundation, and conformance is certified by nominated third-party assessment bodies. It is the most institutionally complete industry API standard in Europe, and the one whose endpoints an outside developer can never call.
Catena-X
Catena-X Automotive Network e.V. was founded on 15 May 2021 by a founding roster that reads like the German industrial economy — BMW, Mercedes-Benz, Volkswagen, Bosch, SAP, Siemens, Schaeffler, ZF, BASF, Henkel, Deutsche Telekom, Fraunhofer — with backing from the German Federal Ministry for Economic Affairs and Climate Action. It is a non-commercial association, and by 2024 it carried more than 180 member companies and organizations. What it produces is a standard library, not a product.
- Numbered standards, published in the open - The catalog is a numbered series — CX-0002 Digital Twins in Catena-X, CX-0018 Dataspace Connectivity, CX-0126 Industry Core: Part Type, CX-0128 Demand and Capacity Management Data Exchange — published at catenax-ev.github.io with no membership wall between a reader and the normative text.
- Four things a standard covers - The association frames its own work as data formats, APIs and interfaces, processes, and security, deliberately aligned to the wider GAIA-X and IDS data space frameworks rather than invented in isolation.
- Releases named after celestial bodies - CX-Jupiter, CX-Io, CX-Saturn, CX-Titan. Each release moves a set of standards forward together, so an implementer targets a release, not a scatter of individually versioned specs.
- A committee that gates the release - The Technical Committee for Standardization (TC4S) runs the review and quality-assurance phase for every standard candidate up to the final release decision, under the association’s intellectual property regulations and explicit antitrust compliance.
- Conformance is assessed by third parties - Certification runs through nominated Conformity Assessment Bodies — TÜV Rheinland and TÜV SÜD among them — working to a published Conformity Assessment Framework handbook, with a Certification Management Centre inside the association. Very few industry API standards have this layer at all.
- Reference implementation, split out - The code lives as Tractus-X at the Eclipse Foundation, so the specification body and the open-source connector are governed separately. Cofinity-X, a joint venture founded in 2023 by ten of the same industrial partners, operates the network and its marketplace.
The thing to understand about Catena-X is what “API” means here. In a data space there is no vendor endpoint to sign up for. Every participant runs its own connector and its own digital twin registry, and the standard governs the handshake between them — discovery, policy, contract negotiation, then transfer. That is a genuine advance over the alternative of bilateral EDI, and it also means the entire surface is invisible to ordinary API discovery. You can read every CX standard, download the connector, and still have nothing to call, because there is nothing to call until you are onboarded, credentialed and certified. Compare CAMARA, where the specification is downloadable and the operator endpoints are theoretically public and mostly aren’t, or NMFTA, where the contract is public and the implementation is each carrier’s problem. Catena-X is the case where the architecture, not the neglect, is what puts the endpoint out of reach.
