Leaderboard / agents.dyoeway.org / endpoint
GET https://agents.dyoeway.org/merchant
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 9 probes in the last 7 days.
- Category
- Compliance by llm, confidence 50%
- Latest quote
- $0.05 on Base to 0x834b…e8AC
- 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 12:04 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.05 | 0x834b…e8AC | 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 |
|---|---|---|---|---|---|
| 31h ago | Compliance | 50% | llm | v1 | claude-haiku-5-5: The endpoint returns a scam/fraud check and trust verdict on an online store, which is a counterparty risk screening rather than a site security audit of the caller's own URL. It fits compliance (risk screening) best, though signal or web_audit could also apply; confidence is moderate. |
| 35h ago | Public data | 50% | rules | v1 | rule public_data matched "ecommerce" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 285 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 9h ago | free | 402 | 97 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 16h ago | free | 402 | 103 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 22h ago | free | 402 | 339 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 28h ago | free | 402 | 417 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 34h ago | free | 402 | 222 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 40h ago | free | 402 | 100 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 47h ago | free | 402 | 109 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |
| 2d ago | free | 402 | 102 ms | v2 | yes | $0.05 | 0x834b…e8AC | — |