All projects matching “address-poisoning”

Verdix: call before an agent sends funds to an EVM address on Base. Returns safe/caution/danger with reasons from OFAC sanctions, scam/phishing lists, address-poisoning lookalikes, burn-address and contract/deployer checks; quick adds address age, standard/deep on-chain behaviour. "safe" is not a guarantee. Legacy route that sells 3 tiers (a default client buys quick); new integrations should call

Checks whether a token contract address is real, matches its claimed symbol, and whether its supply figures match an independent source (CoinGecko) — before trading, coding, or reporting against it. Catches hallucinated/wrong addresses, address-poisoning impersonation, and tokenomics hallucination.

Live feed of freshly-detected malicious addresses on Base — address-poisoning seeders caught via zero-value transfer sprays, updated continuously by our on-chain collector. Poll ?since=<unix> to ingest only new threats into your agent's blocklist. Deterministic, evidence-backed, machine-readable.

Is this x402 API trustworthy? Body {url}. Returns its latest Kertivo Index endpoint trust score/grade (A, B, F, C-never-live, C-went-dark, or ungraded) and run date, plus evidence from a real paid test call: 402 status, price, payTo, settlement tx, on-chain check, HTTP status after paying, latency, schema and delivery result. Not in the index: status not_indexed. Also a public claims tally (buyer-

Did this USDC payment settle, and what is the payer's funding source? Deep Base verification: confirmations, payTo/amount match, fake-token and lookalike warnings, plus the payer's inbound USDC funding history from an index (latest 500 transfers before the payment, then up to 5 more pages; coverage.historyComplete says if that was the full history), top funders, coverage stats and a recheckable sh