Leaderboard / 402.com.tr / endpoint
GET https://402.com.tr/api/x402/address-poisoning
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- Compliance by llm, confidence 50%
- Latest quote
- $0.03 on Base to 0x973a…12d6
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- Observed
- none reported yet (opt-in wrapper telemetry)
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 2h ago
- Next probe
- 2026-11-18 06:22 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.03 | 0x973a…12d6 | default | yes | 4h ago |
Paid probes
No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.
Delivery checks
Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.
No delivery checks yet. They run inside the weekly paid probe.
Classification history
Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 12h ago | Compliance | 50% | llm | v1 | claude-haiku-5-5: The endpoint checks a recipient address for address-poisoning look-alikes, which is a wallet send-safety and scam-screening check. None of the categories is a clean fit. It is closest to compliance (screening), though chain_read or other could also apply, so confidence is moderate. |
| 29h ago | Web audit | 60% | rules | v1 | rule web_audit matched "phishing" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 385 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |
| 9h ago | free | 402 | 404 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |
| 15h ago | free | 402 | 481 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |
| 21h ago | free | 402 | 458 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |
| 28h ago | free | 402 | 415 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |
| 34h ago | free | 402 | 300 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |
| 40h ago | free | 402 | 340 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |
| 46h ago | free | 402 | 426 ms | v2 | yes | $0.03 | 0x973a…12d6 | — |