https://x402-endpoints.onrender.com/agent/visibility-audit
Audit how discoverable an x402 agent/seller is across the agent registries (CDP Bazaar, 402index): keyword-RELEVANCE rank per category (not raw settled-volume rank), a metadata-quality score of your advertised endpoints (schema, output.example, tags, llm_usage_prompt), settle activity, a top-3 benchmark, prioritized fixes, and a DELTA vs a signed snapshot you carry back. Why am I not being found and how do I climb? GEO/AEO discovery audit for x402 sellers, Ed25519-signed.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://x402-endpoints.onrender.com/agent/visibility-audit", {
method: "GET",
});
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.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- Origin reachable
HEAD https://x402-endpoints.onrender.com/ returned 404.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through self-registered.
- Registry record checked
Registry health: healthy.
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.