V2X — Connected Mobility
Interfaces, support status and production prerequisites.
Canonical developer destinations and honest status for proposed versus available interfaces. No invented SDK readiness.
On this page
Developers
Canonical developer destinations and honest status for proposed versus available interfaces. No invented SDK readiness.
- Interface status
- Canonical destinations
- Prerequisites
- Sandbox honesty
Page contract
What, who, boundaries and next step.
- What it is
- Actual interface/support status pointers and production prerequisites.
- Who needs it
- Integration engineers.
- Problem / intended benefit
- Invented SDK readiness creates false production assumptions.
- Ciright responsibility
- Canonical developer destinations under /developers.
- Keyra responsibility
- Required for privileged developer APIs.
- Demonstrated
- Links to existing developer portal routes.
- Proposed / Unverified
- Any undocumented V2X SDK as generally available.
- Evidence
- Developer offering family Unverified for V2X-specific APIs.
Prerequisites
- Keyra verification for protected developer functions
- Approved sandbox vs production separation
Limitations
- Proposed interfaces labeled proposed
- No auto-created accounts from contact forms
Canonical destinations
Use existing Ciright developer surfaces.
Evidence posture
Demonstrated versus proposed.
Every material claim requires configuration scope, source/version, owner and review date before it can leave Unverified. Industry explanations (including 5GAA direct/network context) are not Ciright hardware proof.
Take a reliable next step.
Public education stays readable. Protected accounts, pilot records and privileged functions require Keyra verification. General corporate inquiry assurance policy is preserved until product/security owners change it.