Leaderboard / www.mahastrategies.com / endpoint
POST https://www.mahastrategies.com/api/v1/verify/workflows/client-api-upgrade
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
- Other by llm, confidence 35%
- Latest quote
- $0.1255 on Base to 0xec84…de28
- 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 12:32 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.1255 | 0xec84…de28 | 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 |
|---|---|---|---|---|---|
| 13h ago | Other | 35% | llm | v1 | claude-haiku-5-5: The endpoint reviews API upgrade compatibility by comparing supplied request/response contracts and schema manifests, which is a developer-tooling verification workflow not matching any listed category. The description is dense and jargon-heavy, so confidence is low; 'other' fits best since no category covers schema compatibility checking. |
| 36h ago | Data transform | 60% | rules | v1 | rule data_transform matched "json schema" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 188 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 9h ago | free | 402 | 123 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 15h ago | free | 402 | 189 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 22h ago | free | 402 | 578 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 28h ago | free | 402 | 175 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 34h ago | free | 402 | 217 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 40h ago | free | 402 | 148 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 46h ago | free | 402 | 218 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |
| 2d ago | free | 402 | 126 ms | v2 | yes | $0.1255 | 0xec84…de28 | — |