Implement the ACP Orders endpoint (GET /acp/orders/{orderId}) that returns order status, line items, fulfillment details, and tracking information in the ACP Order object schema
Authenticate order retrieval requests using the ACP OAuth 2.0 token issued to the buyer agent during checkout; validate that the token scope includes order read access and that the order belongs to the token's principal
Map your internal order states (pending, processing, shipped, delivered, cancelled) to the canonical ACP order status enum values; return status updates as they change
Implement the orders list endpoint (GET /acp/orders) with filtering by date range and status so agents can poll for updates across a user's order history
Emit ACP webhook events for order status changes so agent platforms can receive push notifications instead of polling; sign webhook payloads with your ACP signing key for verification
Known gotchas
The ACP Order object schema includes a fulfillment.trackingUrl field; if your logistics partner changes tracking URL formats, previously issued tracking URLs embedded in order objects may break — store the carrier and tracking number separately and construct URLs dynamically
Order ownership verification is critical; a compromised agent token must not be able to enumerate another user's order history — enforce principal-scoped filtering at the database query level, not just in application logic
ACP webhook delivery is not guaranteed; design your order status endpoint to be the authoritative source and treat webhooks as a latency optimization, not a replacement for polling
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp