Discover
Find normalized services and external catalog evidence without treating discovery as execution authority.
From machine intent to portable evidence.
M2M Market is the protocol-neutral control plane around a procurement lifecycle. External standards can supply discovery, agent interoperability, authorization or payment rails without replacing the canonical M2M model.
Compare
Compare price, source context, verification signals and policy eligibility across candidates.
Authorize
Apply delegated authority, organization policy and bounded spending rules before a mutating action can proceed.
Quote
Capture the commercial proposal and the protocol or rail that would apply to an eligible request.
Reserve
Bound commercial exposure before execution when the selected flow requires reservation.
Execute
Coordinate the service request and record whether the provider interaction ran; execution alone does not prove a useful outcome.
Evaluate
Apply evidence-dependent outcome criteria where the service supports meaningful verification.
Settle / reconcile
Reconcile the commercial obligation separately from service execution and outcome correctness.
Portable receipt
Carry lifecycle and evidence references forward without treating the receipt itself as a guarantee of correctness.
Four separate questions
Run, reconcile, verify, record.
Execution asks whether the service ran. Settlement/reconciliation asks whether the commercial obligation was resolved. Outcome verification asks whether available evidence satisfies service-specific criteria. Receipt carries the resulting references forward.
None of those answers automatically supplies the others.
Current production posture
Availability is stage-specific.
Discovery, policy, quote and lifecycle-read surfaces can be live while spend-capable payment, refund, external-signing and broad publication actions remain gated. The Standards Observatory is the canonical public status surface.
View capability status →For enterprises
Policy before mutation.
Organizations can apply shared budgets, approved Providers, private catalogs, approval thresholds, data-sensitivity and jurisdiction policy, kill controls and audit history at the control-plane boundary.
Security and controls →For providers
Verification depends on evidence.
M2M can coordinate execution and evaluate outcomes when a service exposes suitable evidence. It does not claim that every service can always be objectively verified.
Provider model →