What it validates
Advertised buyability
Public HTTPS safety, DNS/private-address rejection, reachability, HTTP 402 posture, payment-required header, JSON body shape, accepts[] options, x402/payment vocabulary, and origin discovery manifest.
What it returns
Agent-readable score
A JSON result with score, verdict, last_validated, advertised_works, observed headers, manifest status, and recommended next step.
What a check is not
Use the right review depth
A proof check does not pay the endpoint or certify fulfillment. For that, a Trust Index review makes a real capped purchase.
Agent contract
Paid endpoint
GET https://resolvebots.com/api/x402-endpoint-check?endpoint=https%3A%2F%2Fexample.com%2Fpaid-resource
Price: 0.25 USDC
Payment: Circle Gateway x402, returned through the 402 Payment-Required response
Input: endpoint = absolute public HTTPS URL, no credentials, default HTTPS port, public DNS only
Output: application/json
Scoring model
Designed for quick buyer-agent triage.
| Check | Points | Why it matters |
|---|---|---|
| Reachable public HTTPS endpoint | 15 | Agents need a URL that responds reliably from public infrastructure. ResolveBots accepts public HTTPS targets with clean DNS and default HTTPS routing. |
| HTTP 402 posture | 22 | A clear payment-required response is the core x402 handshake. |
| Payment-required header | 18 | Headers let clients discover payment requirements without scraping prose. |
| Parseable JSON | 12 | Buyer agents need structured data, not just a human error page. |
| Payment accepts metadata | 16 | Machine-readable network, asset, amount, and facilitator details improve buyer-agent success. |
| x402/payment vocabulary | 7 | Confirms the response is likely intentionally advertising a paid resource. |
| Origin manifest | 10 | /.well-known/x402.json helps marketplaces and agents find the seller's wider catalog. |