# x402 Ecosystem Intelligence - 2026-W21

Published: 2026-05-18T19:43:17Z
Week: 2026-05-18 to 2026-05-24

This weekly report tracked 4 service signal(s), 1 broken implementation pattern(s), and produced 3 scanner/docs/product task(s).

## New services

- **Agent Trust Scan is exposed in x402 discovery** (ready)
  - Impact: Agents can discover this paid endpoint through Ontario's machine-readable catalog, but continued trust depends on a fresh verification report.
  - Action: Keep a current readiness report and ensure the service profile exposes price, network, manifest, and OpenAPI evidence.
  - Repeat key: `service:ontario.agent-trust-scan` (1)
- **Agent Reputation Lookup is exposed in x402 discovery** (ready)
  - Impact: Agents can discover this paid endpoint through Ontario's machine-readable catalog, but continued trust depends on a fresh verification report.
  - Action: Keep a current readiness report and ensure the service profile exposes price, network, manifest, and OpenAPI evidence.
  - Repeat key: `service:ontario.reputation` (1)
- **Submit Agent Listing is exposed in x402 discovery** (ready)
  - Impact: Agents can discover this paid endpoint through Ontario's machine-readable catalog, but continued trust depends on a fresh verification report.
  - Action: Keep a current readiness report and ensure the service profile exposes price, network, manifest, and OpenAPI evidence.
  - Repeat key: `service:ontario.list-agent` (1)
- **List a Third-Party x402 Service is exposed in x402 discovery** (ready)
  - Impact: Agents can discover this paid endpoint through Ontario's machine-readable catalog, but continued trust depends on a fresh verification report.
  - Action: Keep a current readiness report and ensure the service profile exposes price, network, manifest, and OpenAPI evidence.
  - Repeat key: `service:ontario.list-service` (1)

## Broken implementations

- **https://ontarioprotocol.com/api/x402/list-service failed readiness as close** (close)
  - Impact: Readiness score 80/100 means agents should review or deny payment until the endpoint proves compatibility.
  - Action: A paid endpoint should reply with HTTP 402 and a payment requirements header when called without payment.
  - Repeat key: `broken:https://ontarioprotocol.com:close` (1)

## Protocol changes

- **No confirmed external x402 or MCP protocol change recorded by local monitor** (watchlist)
  - Impact: The report has a protocol-change lane, but it needs a curated source feed to avoid guessing about standards or SDK releases.
  - Action: Track x402 facilitator docs, major client SDK releases, MCP paid-tool metadata, and Bazaar-style catalog changes as explicit weekly inputs.
  - Repeat key: `protocol:source-feed-needed` (1)

## Scanner improvements

- **Promote recurring failure into scanner rule: https://ontarioprotocol.com/api/x402/list-service failed readiness as close** (candidate)
  - Impact: Each repeated failure pattern should become a deterministic verifier rule and documentation fix.
  - Action: A paid endpoint should reply with HTTP 402 and a payment requirements header when called without payment.
  - Repeat key: `scanner-rule:broken:https://ontarioprotocol.com:close` (1)

## Scanner, docs, and product tasks

- **scanner** [normal]: A paid endpoint should reply with HTTP 402 and a payment requirements header when called without payment.
  - Reason: Scanner rules should advance whenever weekly intelligence finds repeated endpoint or protocol evidence.
  - Repeat key: `scanner-rule:broken:https://ontarioprotocol.com:close`
- **docs** [normal]: Publish a short public note for this week's highest-impact x402 ecosystem finding
  - Reason: The report should create an indexable docs or answer-graph improvement every week.
  - Repeat key: `protocol:source-feed-needed`
- **product** [normal]: Follow up on the highest-risk broken paid endpoint
  - Reason: Developer mindshare depends on real endpoints and visible verification outcomes, not only internal features.
  - Repeat key: `broken:https://ontarioprotocol.com:close`

## Hermes feedback

Repeated findings are exported to `.well-known/hermes-skills/x402-ecosystem-intelligence.json` so future agents can turn market evidence into scanner rules, docs updates, and product work.