Leaderboard / coord.taifoon.dev / endpoint
POST https://coord.taifoon.dev/v1/exchanges/edge_e01dbd6545e6f15a/call
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- Other by llm, confidence 30%
- Latest quote
- $0.0012 on Base to 0x3574…4f5b
- 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
- 6m ago
- Next probe
- 2026-11-18 17:21 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Base | 0x8335…2913 | $0.0012 | 0x3574…4f5b | default | yes | 14m 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 |
|---|---|---|---|---|---|
| 15h ago | Other | 30% | llm | v1 | claude-haiku-5-5: The listing proxies an MCP tool named get_agent_wallet_status for an agent wallet, but the description is vague about what the wallet status contains (balances, reputation, or activity), and the generic exchange/call wrapper gives no further detail. Low confidence, so 'other' fits best, though chain_read is a possible alternative. |
| 38h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6m ago | free | 402 | 991 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 6h ago | free | 402 | 4129 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 13h ago | free | 402 | 824 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 19h ago | free | 402 | 3227 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 26h ago | free | 402 | 249 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 32h ago | free | 402 | 3390 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 39h ago | free | 402 | 4220 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 45h ago | free | 402 | 5437 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |
| 2d ago | free | 402 | 4242 ms | v2 | yes | $0.0012 | 0x3574…4f5b | — |