POST /service
x402 preflight / reputation — verify BEFORE you pay. Give it an x402 endpoint_url (or a payTo address) and it returns, in one cheap deterministic call: is the resource reachable, is it present in the CDP Bazaar discovery catalog (serviceName, declared payTo, price, network, tags, last_seen), and — the key integrity check — does the payTo the endpoint actually demands in its live HTTP 402 challenge MATCH the payTo the catalog advertises (payTo_match). It runs a keyless HEAD/OPTIONS/402 probe that never moves funds, extracts the real payTo/amount/asset/network from the challenge, scores listing freshness, and — if you pass a prev snapshot {payTo,amount,lastUpdated} — flags whether the endpoint changed since you last saw it (anti-rug). Output is a 0-100 scorecard + letter grade + reason codes
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://x402meta.hergertsynthora.com/service", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"endpoint_url"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://x402meta.hergertsynthora.com/ returned 402.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
EVIDENCE
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call.