Developer hub

Integrate the control plane.
Use the scope your integration supports.

M2M adds federated discovery, policy, commercial state and lifecycle evidence around the service calls your software already makes. Standards & Integrations documents the reviewed customer-facing scope for each interoperability layer.

PATH 01

Build an Agent

Give software access to normalized discovery, comparison, policy explanations, quotes and lifecycle state while preserving server-authoritative controls.

Agent guide →
PATH 02

Publish a service

Normalize an existing API into the M2M Service Manifest, validate conformance and prepare only the ecosystem projections you choose.

Provider path →
PATH 03

Track interoperability

Check upstream versions, M2M profiles, integration levels and customer-facing availability without exposing internal operational detail.

Standards & Integrations →
Integration model

Discover → compare → authorize → quote → reserve → execute → evaluate → reconcile → receipt.

Your application can integrate at the stages it needs. Protocol adapters remain downstream of M2M commercial authority.

Integration availability

Check the documented scope before using an action.

Different integrations expose different customer workflows. The public matrix summarizes availability while keeping infrastructure, security controls and deployment details private.

Check Standards & Integrations →