Verify an x402 Publisher

It calls TensorFeed's AFTA certification endpoint against the domain you enter. The endpoint fetches that domain's /.well-known/x402.json and /.well-known/agent-fair-trade.json over HTTPS, parses them, and scores six concrete compliance criteria: canonical x402 V2 manifest shape, paid items with valid accepts[] entries, per-network EIP-712 domain hints, AFTA fair-trade declaration with no-charge guarantees, signed-receipt declaration, and a published receipt-signing public key. Each check is deterministic and idempotent.

The HTTP checks run on TensorFeed servers; you trust us not to lie about what we saw. The on-chain Base mainnet verification is fully trustless if you want to re-run it yourself — install @tensorfeed/x402-base-mcp and call verify_x402_settlement or parse_x402_manifest directly from your own machine. Same logic, different trust anchor.

It is AFTA-eligible. The publisher can email [email protected] and pay the $100 USDC annual fee to be listed on tensorfeed.ai/x402-adopters with the AFTA-Certified badge. See /afta-certified for the listing details.

Each failing check carries a specific fix hint. Typical low scores: missing /.well-known/x402.json (publisher hasn't shipped an x402 manifest yet); manifest is v1 shape (Coinbase moved on to v2); missing extra.name / extra.version (the EIP-712 domain hint that prevents the FiatTokenV2 signature footgun); no AFTA manifest (publisher does not yet commit to no-charge guarantees + signed receipts).

Yes. The check endpoint is at GET /api/afta-certify/check?domain=X.com and returns JSON. Or run the verifier as an MCP server on your own machine: npx -y @tensorfeed/x402-base-mcp.

No. The check is on-demand. We do not log requests to this endpoint with PII or domain attribution. The /api/x402-registry/snapshot endpoint is a separate, opt-in crawl of x402 publishers TF tracks editorially.