Developers
An engineer should be able to find a canonical identifier and a downloadable binding from this page. Accounts are not required.
Get started
Read an industry, then a semantic type, then download the binding. The canonical identifier is the field semantic_type_id. In automotive responses it is also exposed as message_type_id.
API
GET /api/v1/industries, /api/v1/semantic-types?industry=automotive, /api/v1/mappings, /api/v1/profiles, /api/v1/releases, and /api/v1/downloads/package. The index is GET /api/v1. The description is openapi/v1.yaml, also served inside each package.
Data model
Industry, domain, semantic group, semantic type, data point, schema node, unit, standard, mapping, profile, and release. Automotive views alias those records as message group, message type, and point. Identifiers are never reused.
Registry downloads
GET /api/v1/downloads/package?industry=automotive&release=0.0.0-draft&language=c&target=headers&profile=gvxs-us-2026 returns a zip. The manifest records signature_status and conformance_status.
Language bindings
C, C++, Rust, TypeScript, and Python are generated from ingested identifiers. An empty list means the source file has not been ingested. It does not mean the identifier is zero.
Examples
curl /api/v1/messages and curl /api/v1/points are the automotive aliases. Both currently return an empty record list and the canonical status.
Validation
npm run validate:ids, validate:schemas, validate:mappings, validate:standards, validate:profiles, validate:artifacts, and validate:release. A release marked released must be signed and carry SHA-256 checksums.
Conformance
C1 Core Registry, C2 Translation, C3 Security and Trust, C4 Market Deployment. These levels are not certificates.