Leaderboard / dev-5090-box.tailfb4c1f.ts.net / endpoint
POST https://dev-5090-box.tailfb4c1f.ts.net/v1/regex-build
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
- Inference by llm, confidence 60%
- Latest quote
- $0.02 on Base to 0x07f3…95e3
- 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
- 2h ago
- Next probe
- 2026-11-18 11:52 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.02 | 0x07f3…95e3 | default | yes | 3h 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 |
|---|---|---|---|---|---|
| 30h ago | Inference | 60% | llm | v1 | claude-haiku-5-5: Service is named uncensored inference and the endpoint takes messages (chat-style input) and generates regex output via a model, which points to LLM output. The tag says utility.regex-build, which would suggest a deterministic utility, but the messages input and the inference service name make inference the more likely classification. |
| 34h ago | Data transform | 60% | rules | v1 | rule data_transform matched "regex" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 415 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 8h ago | free | 402 | 499 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 14h ago | free | 402 | 409 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 21h ago | free | 402 | 373 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 27h ago | free | 402 | 411 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 33h ago | free | 402 | 381 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 39h ago | free | 402 | 108 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 45h ago | free | 402 | 115 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |
| 2d ago | free | 402 | 117 ms | v2 | yes | $0.02 | 0x07f3…95e3 | — |