Leaderboard / api.ysaere.com / endpoint
POST https://api.ysaere.com/v1/intel/sam-cage
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Public data by llm, confidence 60%
- Latest quote
- $0.02 on Base to 0x5D83…0B05
- 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
- 7h ago
- Next probe
- 2026-11-18 00:07 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.02 | 0x5D83…0B05 | default | yes | 2h 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 |
|---|---|---|---|---|---|
| 17h ago | Public data | 60% | llm | v1 | claude-haiku-5-5: The endpoint looks up SAM.gov CAGE codes and UEI identifiers for a named contractor company, which is government registry data. It fits public_data best, though the listing is terse and could also be read as enrichment for company lookup. |
| 27h ago | Public data | 50% | rules | v1 | rule public_data matched "gov" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 7h ago | free | 402 | 188 ms | v2 | yes | $0.02 | 0x5D83…0B05 | — |
| 13h ago | free | 402 | 200 ms | v2 | yes | $0.02 | 0x5D83…0B05 | — |
| 19h ago | free | 402 | 396 ms | v2 | yes | $0.02 | 0x5D83…0B05 | — |
| 25h ago | free | 402 | 212 ms | v2 | yes | $0.02 | 0x5D83…0B05 | — |
| 31h ago | free | 402 | 174 ms | v2 | yes | $0.02 | 0x5D83…0B05 | — |
| 38h ago | free | 402 | 184 ms | v2 | yes | $0.02 | 0x5D83…0B05 | — |
| 44h ago | free | 402 | 141 ms | v2 | yes | $0.02 | 0x5D83…0B05 | — |