{
  "ok": true,
  "tool": "ecosystem.trends",
  "schema": "trust402.ecosystem_trends.v1",
  "generatedAt": "2026-06-22T09:25:36.448Z",
  "asOfDate": "2026-06-22",
  "trendHash": "sha256:8e072510ca9167ccc9558064b36d03e85b59f56ed65c9e09373c2aa9facd1e25",
  "summary": "Base/x402 agent commerce is moving toward wallet-enabled buyer agents, marketplace discovery, approval-gated purchases, bundled paid intelligence, and verification-native receipts.",
  "sources": [
    {
      "id": "base_agents",
      "name": "Base Agents",
      "url": "https://www.base.org/agents",
      "signal": "Base positions AI agents around wallets, spend controls, x402 payments, and onchain services."
    },
    {
      "id": "base_mcp_x402",
      "name": "Base MCP x402 payments",
      "url": "https://docs.base.org/ai-agents/guides/x402-payments",
      "signal": "Base MCP uses an initiate/approve/complete flow, which is better for deliberate purchases than high-frequency tiny calls."
    },
    {
      "id": "agentic_market",
      "name": "Agentic Market",
      "url": "https://agentic.market/",
      "signal": "Agent-facing APIs are discovered, priced, and bought per result without accounts or subscriptions."
    },
    {
      "id": "agentic_market_about",
      "name": "Agentic Market About",
      "url": "https://agentic.market/about",
      "signal": "Buyers compare services by use case, price, network, and endpoint before paying in USDC."
    },
    {
      "id": "cdp_bazaar_quality",
      "name": "CDP x402 Bazaar",
      "url": "https://docs.cdp.coinbase.com/x402/bazaar",
      "signal": "Bazaar uses semantic search plus objective quality signals such as buyer reach, transaction volume, recency, and metadata quality."
    },
    {
      "id": "x402_ecosystem",
      "name": "x402 ecosystem",
      "url": "https://www.x402.org/ecosystem",
      "signal": "Infrastructure members and directories are converging around Base settlement, x402 discovery, MCP tools, and risk controls."
    },
    {
      "id": "x402_security_research",
      "name": "x402 security research",
      "url": "https://arxiv.org/abs/2605.11781",
      "signal": "Current risk research highlights authorization binding, replay protection, and web-layer handling as practical x402 concerns."
    }
  ],
  "categories": [
    {
      "id": "agentic_buyer_workflows",
      "label": "Agentic buyer workflows",
      "momentum": "high",
      "buyerNeed": "Agents need to discover, compare, pay, verify, and remember what they bought.",
      "trust402Fit": "Trust402 can sit before payment as a route scorer and after payment as a receipt/proof planner.",
      "recommendedOffers": [
        "trust.check_x402",
        "trust.score_resource",
        "trust.compare_resources",
        "reports.x402_diligence"
      ],
      "offerUrls": [
        {
          "id": "trust.check_x402",
          "url": "https://trust402.aztecbeacon.uk/api/trust/check-x402"
        },
        {
          "id": "trust.score_resource",
          "url": "https://trust402.aztecbeacon.uk/api/trust/score-resource"
        },
        {
          "id": "trust.compare_resources",
          "url": "https://trust402.aztecbeacon.uk/api/trust/compare-resources"
        },
        {
          "id": "reports.x402_diligence",
          "url": "https://trust402.aztecbeacon.uk/api/reports/x402-diligence"
        }
      ]
    },
    {
      "id": "paid_market_intelligence",
      "label": "Paid market intelligence",
      "momentum": "high",
      "buyerNeed": "Visible paid services cluster around concise research, market briefs, scanners, and decision reports.",
      "trust402Fit": "Trust402 should package endpoint diligence as a paid decision report, not only as raw endpoint checks.",
      "recommendedOffers": [
        "reports.x402_diligence",
        "trust.compare_resources",
        "procurement.quote"
      ],
      "offerUrls": [
        {
          "id": "reports.x402_diligence",
          "url": "https://trust402.aztecbeacon.uk/api/reports/x402-diligence"
        },
        {
          "id": "trust.compare_resources",
          "url": "https://trust402.aztecbeacon.uk/api/trust/compare-resources"
        },
        {
          "id": "procurement.quote",
          "url": "https://trust402.aztecbeacon.uk/api/procurement/quote"
        }
      ]
    },
    {
      "id": "bazaar_quality_recency",
      "label": "Bazaar quality and recency",
      "momentum": "high",
      "buyerNeed": "Agents need endpoints that remain discoverable, recently settled, and richly described enough for semantic search.",
      "trust402Fit": "Trust402 can publish route-level evidence, score metadata quality, and keep Radar/receipt artifacts crawlable.",
      "recommendedOffers": [
        "monitor.snapshot",
        "monitor.badge",
        "seller.readiness",
        "trust.score_resource"
      ],
      "offerUrls": [
        {
          "id": "monitor.snapshot",
          "url": "https://trust402.aztecbeacon.uk/api/monitor/snapshot"
        },
        {
          "id": "monitor.badge",
          "url": "https://trust402.aztecbeacon.uk/api/monitor/badge"
        },
        {
          "id": "seller.readiness",
          "url": "https://trust402.aztecbeacon.uk/api/seller/readiness"
        },
        {
          "id": "trust.score_resource",
          "url": "https://trust402.aztecbeacon.uk/api/trust/score-resource"
        }
      ]
    },
    {
      "id": "approval_gated_x402_mcp",
      "label": "Approval-gated x402 through MCP",
      "momentum": "high",
      "buyerNeed": "Human-approved Base MCP payments favor larger, higher-confidence purchases over noisy microcalls.",
      "trust402Fit": "Trust402 should present one clear quote, maxPayment guidance, and receipt expectations before an agent asks for approval.",
      "recommendedOffers": [
        "procurement.plan",
        "procurement.quote",
        "trust.compare_resources"
      ],
      "offerUrls": [
        {
          "id": "procurement.plan",
          "url": "https://trust402.aztecbeacon.uk/api/procurement/plan"
        },
        {
          "id": "procurement.quote",
          "url": "https://trust402.aztecbeacon.uk/api/procurement/quote"
        },
        {
          "id": "trust.compare_resources",
          "url": "https://trust402.aztecbeacon.uk/api/trust/compare-resources"
        }
      ]
    },
    {
      "id": "verification_native_clearing",
      "label": "Verification-native clearing",
      "momentum": "emerging",
      "buyerNeed": "Payment alone does not prove that the right service responded, that the result was delivered, or that no replay/binding mistake happened.",
      "trust402Fit": "Trust402 should keep emphasizing challenge binding, price checks, public discovery, result hashing, and Proof402-ready evidence.",
      "recommendedOffers": [
        "trust.check_x402",
        "monitor.snapshot",
        "reports.x402_diligence"
      ],
      "offerUrls": [
        {
          "id": "trust.check_x402",
          "url": "https://trust402.aztecbeacon.uk/api/trust/check-x402"
        },
        {
          "id": "monitor.snapshot",
          "url": "https://trust402.aztecbeacon.uk/api/monitor/snapshot"
        },
        {
          "id": "reports.x402_diligence",
          "url": "https://trust402.aztecbeacon.uk/api/reports/x402-diligence"
        }
      ]
    },
    {
      "id": "privacy_safe_payment_metadata",
      "label": "Privacy-safe payment metadata",
      "momentum": "emerging",
      "buyerNeed": "Agents need to avoid leaking private task details through payment descriptions, URLs, headers, and facilitator-visible metadata.",
      "trust402Fit": "Trust402 should continue stripping payment headers from unpaid probes and guide sellers toward minimal public metadata.",
      "recommendedOffers": [
        "trust.score_resource",
        "seller.readiness",
        "monitor.badge"
      ],
      "offerUrls": [
        {
          "id": "trust.score_resource",
          "url": "https://trust402.aztecbeacon.uk/api/trust/score-resource"
        },
        {
          "id": "seller.readiness",
          "url": "https://trust402.aztecbeacon.uk/api/seller/readiness"
        },
        {
          "id": "monitor.badge",
          "url": "https://trust402.aztecbeacon.uk/api/monitor/badge"
        }
      ]
    },
    {
      "id": "seller_hardening",
      "label": "Seller-side hardening",
      "momentum": "emerging",
      "buyerNeed": "Sellers need to prove that payment metadata, price consistency, request binding assumptions, and replay controls are safe before agents trust them.",
      "trust402Fit": "Trust402 should package seller readiness and diligence as x402 security posture checks, not just marketing readiness.",
      "recommendedOffers": [
        "seller.readiness",
        "reports.x402_diligence",
        "monitor.snapshot"
      ],
      "offerUrls": [
        {
          "id": "seller.readiness",
          "url": "https://trust402.aztecbeacon.uk/api/seller/readiness"
        },
        {
          "id": "reports.x402_diligence",
          "url": "https://trust402.aztecbeacon.uk/api/reports/x402-diligence"
        },
        {
          "id": "monitor.snapshot",
          "url": "https://trust402.aztecbeacon.uk/api/monitor/snapshot"
        }
      ]
    }
  ],
  "buyerWorkflow": [
    {
      "step": "discover",
      "description": "Read /.well-known/x402, OpenAPI, resource catalogs, and marketplace listings before considering payment.",
      "trust402Route": "/api/resources"
    },
    {
      "step": "screen",
      "description": "Check schema, price, x402 challenge, network, receipt readiness, and public seller metadata.",
      "trust402Route": "/api/trust/score-resource"
    },
    {
      "step": "compare",
      "description": "Rank 2-10 candidate resources by goal fit, risk, price, discovery completeness, and proof readiness.",
      "trust402Route": "/api/trust/compare-resources"
    },
    {
      "step": "approve",
      "description": "Ask the user or policy engine for a bounded maxPayment only after the route and quote are clear.",
      "trust402Route": "/api/procurement/quote"
    },
    {
      "step": "verify",
      "description": "Hash the purchased result, preserve public-safe evidence, and notarize only approved hashes when proof delegation is enabled.",
      "trust402Route": "/api/receipts/hash-result"
    },
    {
      "step": "monitor",
      "description": "Recheck payment-flow drift, challenge changes, and seller metadata before repeat purchases.",
      "trust402Route": "/api/monitor/snapshot"
    }
  ],
  "productMoves": [
    {
      "id": "sell_reports_not_raw_checks",
      "priority": "high",
      "action": "Position the diligence report and compare-resources flows as the main paid offers for agents with approval-gated wallets.",
      "reason": "Current buyer behavior favors actionable bundles and reports over one-off low-context checks."
    },
    {
      "id": "base_mcp_wrapper",
      "priority": "high",
      "action": "Expose a tiny MCP wrapper later with tools such as score_x402_resource and compare_x402_resources that call the existing paid endpoints.",
      "reason": "Base MCP/Hermes/Codex flows make x402 purchasing easier when the agent can call one clear tool and receive approval guidance."
    },
    {
      "id": "receipt_first_ui",
      "priority": "medium",
      "action": "Keep receipts, result hashes, and Proof402-ready metadata visible on every paid workflow.",
      "reason": "Verification-native clearing is a stronger moat than generic endpoint scoring."
    },
    {
      "id": "fresh_indexing_evidence",
      "priority": "medium",
      "action": "Refresh marketplace visibility evidence after every production deploy and avoid stale 10/10 claims.",
      "reason": "Directory indexing can regress even when production smoke and x402 smoke pass."
    },
    {
      "id": "seller_hardening_reports",
      "priority": "medium",
      "action": "Make seller readiness and diligence reports explicitly test discovery metadata, payment metadata privacy, replay assumptions, price clarity, and receipt output.",
      "reason": "Security-hardening language is now part of the x402 buying decision, especially for autonomous purchasers."
    }
  ],
  "trust402Positioning": {
    "role": "buyer-side trust, procurement, and proof-readiness layer for x402 resources",
    "bestPaidOffersNow": [
      "trust.compare_resources",
      "reports.x402_diligence",
      "procurement.quote"
    ],
    "mcpStrategy": "Add a wrapper later; keep OpenAPI/x402 endpoints as the canonical paid API.",
    "proofStrategy": "Hash results locally and delegate to Proof402 only when policy explicitly allows approved hash notarization."
  },
  "safety": {
    "publicSafe": true,
    "sendsPaymentHeaders": false,
    "paidSubcallsMade": 0,
    "liveSpendDefault": false,
    "liveSpendCurrentlyReady": true,
    "exposesSecrets": false
  },
  "avoid": [
    "Do not run unbounded autonomous spend against newly discovered x402 endpoints.",
    "Do not leak private task details in payment descriptions, URLs, payment headers, or facilitator-visible metadata.",
    "Do not claim marketplace visibility from stale evidence; keep fresh route-level checks beside launch claims.",
    "Do not force Base MCP users through manual approval for tiny repeated calls when one bundled report would be clearer."
  ],
  "links": {
    "radar": "https://trust402.aztecbeacon.uk/radar",
    "radarJson": "https://trust402.aztecbeacon.uk/radar.json",
    "ecosystemPulse": "https://trust402.aztecbeacon.uk/api/radar/ecosystem-pulse",
    "resources": "https://trust402.aztecbeacon.uk/api/resources",
    "policies": "https://trust402.aztecbeacon.uk/api/policies/spend",
    "openapi": "https://trust402.aztecbeacon.uk/openapi.json",
    "x402": "https://trust402.aztecbeacon.uk/.well-known/x402"
  }
}