Your agent will confidently recommend a deprecated SDK. We give it something to cite instead.

{
  "intent": "agent-native services marketplace on Arbitrum",
  "matched_intent": "build-agentic-commerce-with-x402",
  "chain": "arbitrum-one",
  "recommended_stack": [
    { "slug": "x402",         "role": "payments_and_commerce",    "reason": "HTTP 402 flow; buyer agents pay per request with bounded spend." },
    { "slug": "erc-8004",     "role": "agent_identity_and_trust", "reason": "Public agent identity, discovery, reputation, validation." },
    { "slug": "arbitrum-one", "role": "settlement_or_execution",  "reason": "Low-cost EVM contracts, payment receipts, refund state." },
    { "slug": "goldsky",      "role": "indexing_and_data",        "reason": "Index listings, payments, fulfillment, reputation surfaces." },
    { "slug": "safe",         "role": "supporting_protocol",      "reason": "Treasury, refunds, and incident approvals via multisig." }
  ],
  "excluded_candidates": [
    { "slug": "uniswap", "reason": "Liquidity and swaps, but not the payment or agent-trust layer here." }
  ],
  "risks": [
    "ERC-8004 is draft status; track spec and contract updates before production.",
    "x402 handles payments, not fulfillment, escrow, returns, or disputes.",
    "Buyer agents need spend caps, replay-safe order IDs, and refund paths."
  ],
  "next_steps": [
    "Separate listing/order/fulfillment/refund state from x402 payment state.",
    "Register seller agents via ERC-8004 and publish MCP/A2A endpoints.",
    "Verify x402 facilitator, token, and network support on Arbitrum."
  ],
  "citations": [ "/protocols/x402.json", "/protocols/erc-8004.json", "/protocols/arbitrum-one.json" ]
}