Frequently asked questions

Answers about the M2M control plane.

Core questions about discovery, authority, protocols, Provider distribution, outcome verification, receipts and integration availability.

What is M2M Market?+

M2M Market is a protocol-neutral procurement and outcome-verification control plane for machine-to-machine and AI-agent commerce. It coordinates discovery, comparison, authorization, quotes, reservations, execution evidence, outcome evaluation, commercial reconciliation and portable receipts.

Is M2M Market an MCP registry, x402 marketplace or payment rail?+

No. Those protocols and registries can interoperate with M2M, but none is the canonical M2M architecture. M2M keeps commercial authority and lifecycle evidence protocol-neutral.

What is an agent service marketplace?+

It is a machine-readable service market where autonomous software can discover and compare capabilities, pricing and source evidence. Discovery does not automatically make a service executable or purchase-eligible.

Can an agent spend without limits?+

No. Actions remain subject to delegated authority, server-side policy and the customer-facing availability of the selected integration.

How do x402, MPP and AP2 relate to M2M?+

x402 and MPP provide payment interoperability and AP2 provides agentic payment authorization/evidence. M2M can adapt those rails while preserving its canonical procurement, verification and receipt model.

Does payment success mean the result was useful?+

No. Settlement or reconciliation answers a commercial question. Outcome verification separately asks whether available service-specific evidence satisfies the configured criteria.

Does a portable receipt guarantee outcome correctness?+

No. A portable receipt carries lifecycle, commercial, execution and verification references. It is evidence, not a universal warranty.

How does M2M describe Provider verification?+

Catalog states such as indexed, source-verified and M2M-managed describe different evidence relationships. None by itself guarantees every service outcome.

Is Provider syndication available across every ecosystem?+

No. M2M supports canonical manifests, conformance, ecosystem projections and selective syndication. Availability varies by target and customer scope; universal third-party publication is not implied.

Does reputation affect service ordering?+

Reputation is a separate evidence signal. The public Standards & Integrations page describes customer-facing capability scope without exposing internal scoring or release controls.

Are refunds or AP2 transaction signing generally available?+

Availability varies by capability and use case. Standards & Integrations provides the reviewed customer-facing scope for these integrations.

Where should I check current support?+

Use Standards & Integrations for reviewed upstream protocol versions, M2M profiles, integration levels and customer-facing availability.