recipient-check: POST /v1/recipient-check
Pre-send safety check: is this recipient a known malicious address (caught live on Base seeding address-poisoning via zero-value transfer sprays), or a look-alike of an address you trust? Checks our continuously-updated threat DB + deterministic look-alike logic. Answers an agent's 'is it safe to send here?' before every transfer.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://x402.dailyelo.com/v1/recipient-check", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"known_addresses",
"recipient"
],
"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://x402.dailyelo.com/ returned 200.
- 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.