Leaderboard / trust-agent.io / endpoint
GET https://trust-agent.io/v1/endpoint/screen
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
- x402 tooling by llm, confidence 60%
- Latest quote
- $0.005 on Base to 0x6121…e6BB
- 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
- 4h ago
- Next probe
- 2026-11-18 06:05 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.005 | 0x6121…e6BB | 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 |
|---|---|---|---|---|---|
| 26h ago | x402 tooling | 60% | llm | v1 | claude-haiku-5-5: The endpoint inspects x402 payment challenges and screens payout wallets, which fits x402 payment-header tooling, but it also performs OFAC sanctions screening and returns a risk verdict, so compliance is a plausible alternative. The x402_meta category fits best because the core function is analysing an x402 endpoint's payment requirements before payment. |
| 30h ago | x402 tooling | 60% | rules | v1 | rule x402_meta matched "x402 endpoint" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 240 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |
| 10h ago | free | 402 | 170 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |
| 17h ago | free | 402 | 261 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |
| 23h ago | free | 402 | 251 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |
| 29h ago | free | 402 | 118 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |
| 35h ago | free | 402 | 132 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |
| 42h ago | free | 402 | 134 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |
| 2d ago | free | 402 | 270 ms | v2 | yes | $0.005 | 0x6121…e6BB | — |