Leaderboard / agents.avasis.ai / endpoint
GET https://agents.avasis.ai/v1/base/seller-revenue-audit
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
- Chain read by llm, confidence 50%
- Latest quote
- $0.1 on Base to 0x6264…1fc8
- 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
- 3h ago
- Next probe
- 2026-11-18 06:00 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.1 | 0x6264…1fc8 | default | yes | 5h 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 |
|---|---|---|---|---|---|
| 20h ago | Chain read | 50% | llm | v1 | claude-haiku-5-5: The endpoint audits a seller payTo address by reading on-chain Base USDC transferWithAuthorization settles, payers and flags, which is a public-chain read, though it also produces an analytical report. Tags emphasize x402 seller auditing, which could also fit x402_meta, but the output is derived from chain data rather than catalog or payment-header tooling. |
| 30h ago | x402 tooling | 60% | rules | v1 | rule x402_meta matched "x402 seller" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 65 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |
| 10h ago | free | 402 | 89 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |
| 17h ago | free | 402 | 72 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |
| 23h ago | free | 402 | 212 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |
| 29h ago | free | 402 | 206 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |
| 35h ago | free | 402 | 69 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |
| 41h ago | free | 402 | 81 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |
| 2d ago | free | 402 | 75 ms | v2 | yes | $0.1 | 0x6264…1fc8 | — |