Measured attributes of x402 payment facilitators: on-chain history, whether the
/supported endpoint answers, 7-day uptime and compliance declarations.
Anything we have not measured yet is marked pending, never shown as zero.
We do not publish a composite score while we correct how its inputs are measured.
What the registry measures for each facilitator: days since its first on-chain transaction, its transaction count, whether its /supported endpoint returns a valid x402 document, its 7-day uptime from hourly pings, and any KYT or OFAC declaration. Each attribute is either measured or marked pending; a missing input is never shown as zero. We do not publish a composite score while we correct how its inputs are measured. No LLM in the loop. Full rules at the methodology endpoint.
Yes. How every attribute is measured, including redirect handling, the minimum sample before uptime is shown, and the reference endpoints we check to rule out our own outages, is published as JSON at GET /registry/methodology. Every attribute comes from public on-chain data or from requests anyone can make to the facilitator's /supported endpoint.
Copy the one-line embed code from the Embed a registry badge section above. Replace YOUR_ADDRESS with the facilitator's address. Works anywhere that renders images: GitHub READMEs, Notion, npm package pages, docs sites. The badge updates as new measurements come in.
A deterministic policy engine for AI agent payments via the x402 protocol. Agents propose a payment, smart402 returns approve or deny based on rules you define. No LLM in the decision path. The Facilitator Trust Registry is one layer of the trust infrastructure we provide for the x402 ecosystem. Learn more at smart402.com.