Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-27 · today
agents.samedaydesk.com/extract/batch
1.Catalog declaration
| Resource URL | https://agents.samedaydesk.com/extract/batch |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x8904df3de6dfee6a7c8cc38619d2f17806213cee |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-09-09 01:03 UTC / 2026-09-27 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-09-092026-09-27
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-27 04:40 UTC | POST | fail | 400 | 321 ms | no_402 |
| 2026-09-26 16:40 UTC | POST | fail | 400 | 117 ms | no_402 |
| 2026-09-25 22:40 UTC | POST | fail | 400 | 235 ms | no_402 |
| 2026-09-25 04:40 UTC | POST | fail | 400 | 224 ms | no_402 |
| 2026-09-24 13:40 UTC | POST | fail | 400 | 162 ms | no_402 |
| 2026-09-23 16:40 UTC | POST | fail | 400 | 393 ms | no_402 |
| 2026-09-22 22:40 UTC | POST | fail | 400 | 301 ms | no_402 |
| 2026-09-22 04:40 UTC | POST | fail | 400 | 280 ms | no_402 |
| 2026-09-21 13:40 UTC | POST | fail | 400 | 84 ms | no_402 |
| 2026-09-20 16:40 UTC | POST | fail | 400 | 117 ms | no_402 |
| 2026-09-19 22:40 UTC | POST | fail | 400 | 53 ms | no_402 |
| 2026-09-19 11:24 UTC | POST | fail | 400 | 217 ms | no_402 |
| 2026-09-17 11:24 UTC | POST | fail | 400 | 150 ms | no_402 |
| 2026-09-13 11:24 UTC | POST | fail | 400 | 180 ms | no_402 |
| 2026-09-10 11:24 UTC | POST | fail | 400 | 209 ms | no_402 |
| 2026-09-09 11:24 UTC | POST | fail | 400 | 140 ms | no_402 |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.