Leaderboard / x402.orthogonal.com / endpoint
GET https://x402.orthogonal.com/scrapecreators/v1/twitter/profile
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
- Web scrape by llm, confidence 60%
- Latest quote
- $0.02 on Base to 0x9EdC…668d
- 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 04:02 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | eip155:143 | 0x7547…b603 | 20000 | 0x9EdC…668d | default | yes | 2h ago |
| cdp | exact | Base | 0x8335…2913 | $0.02 | 0x9EdC…668d | 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 |
|---|---|---|---|---|---|
| 5h ago | Web scrape | 60% | llm | v1 | claude-haiku-5-5: The endpoint is a Twitter profile lookup that presumably returns profile content for a handle. The description is only 'Twitter', so it is ambiguous whether it returns profile data (enrichment-like) or page content (web_scrape). Scrape-style fetch of a profile fits the taxonomy's definition of fetching a profile and returning its content, with moderate confidence due to sparse listing. |
| 27h ago | Web scrape | 60% | rules | v1 | rule web_scrape matched "scrape" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 139 ms | v2 | yes | $0.02 | 0x9EdC…668d | — |
| 9h ago | free | 402 | 147 ms | v2 | yes | $0.02 | 0x9EdC…668d | — |
| 16h ago | free | 402 | 124 ms | v2 | yes | $0.02 | 0x9EdC…668d | — |
| 22h ago | free | 402 | 133 ms | v2 | yes | $0.02 | 0x9EdC…668d | — |
| 29h ago | free | 402 | 244 ms | v2 | yes | $0.02 | 0x9EdC…668d | — |
| 36h ago | free | 402 | 127 ms | v2 | yes | $0.02 | 0x9EdC…668d | — |
| 42h ago | free | 402 | 126 ms | v2 | yes | $0.02 | 0x9EdC…668d | — |