Agent-Native Commerce defines how products, services, and transactions should be structured so AI agents can discover options, evaluate them against user intent, and complete purchases or bookings autonomously — without human-mediated UI flows.
Commerce surfaces must be reachable via structured discovery before any transaction is possible. Expose product catalogs at /.well-known/agent-discovery.json under entry_points.commerce and link to machine-readable feeds from /feed/ads.json.
Every purchasable item must carry a machine-readable offer object — either as JSON-LD Offer schema embedded in the page, or as a standalone /api/offer/{id} endpoint. Agents cannot reliably parse DOM price elements.
{"@type":"Offer","price":"49.00","priceCurrency":"USD","availability":"https://schema.org/InStock","seller":{"@type":"Organization","name":"Example Co"},"acceptedPaymentMethod":["agent-payment/1.0","stripe"]}Commerce responses must carry FCS-4.0 trust headers so agents can verify the transaction surface before committing. Minimum required: X-Agent-Protocol: FCS-4.0, X-Trust-Anchor, and X-Offer-Object.
Agents require checkout flows that complete in a single authenticated API call. Design a POST /api/checkout endpoint that accepts the full offer object + payment token — no session state, no redirect chains.
Declare transaction rate limits in /.well-known/agent.json under rate_limits.commerce so agents can batch requests appropriately and avoid unintended purchase loops.