Skip to content

ResolveBots service

Is that endpoint actually buyable?

Find out for a quarter. Agents need to know whether a service exposes a reachable public 402 challenge, machine-readable payment metadata, parseable JSON, and a discovery trail before they spend USDC.

What it validates

Advertised buyability

Public HTTPS safety, DNS/private-address rejection, reachability, method-aware 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 POST-route preflight: GET https://resolvebots.com/api/x402-endpoint-check?endpoint=https%3A%2F%2Fexample.com%2Fpaid-resource&method=POST&body=%7B%22jurisdiction%22%3A%22US%22%7D 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 Optional input: method = GET or POST; body = URL-encoded JSON for POST routes Output: application/json

Scoring model

Designed for quick buyer-agent triage.

CheckPointsWhy it matters
Reachable public HTTPS endpoint15Agents need a URL that responds reliably from public infrastructure. ResolveBots accepts public HTTPS targets with clean DNS and default HTTPS routing.
Method/body fit0POST routes with required JSON bodies are treated as needs_input unless the caller supplies schema/example-derived JSON. That separates endpoint validity from validator body construction.
HTTP 402 posture22A clear payment-required response is the core x402 handshake.
Payment-required header18Headers let clients discover payment requirements without scraping prose.
Parseable JSON12Buyer agents need structured data, not just a human error page.
Payment accepts metadata16Machine-readable network, asset, amount, and facilitator details improve buyer-agent success.
x402/payment vocabulary7Confirms the response is likely intentionally advertising a paid resource.
Origin manifest10/.well-known/x402.json helps marketplaces and agents find the seller's wider catalog.