Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago
apiacre.com/v1/web/email-auth
1.Catalog declaration
| Resource URL | https://apiacre.com/v1/web/email-auth |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xa0bfa4f07281c9b248dc3aed2217836bca24869b |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-15 01:36 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
2026-09-012026-10-19
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | POST | pass | 402 | 372 ms | — |
| 2026-10-18 04:40 UTC | POST | pass | 402 | 606 ms | — |
| 2026-10-16 21:40 UTC | POST | pass | 402 | 281 ms | — |
| 2026-10-15 12:40 UTC | POST | pass | 402 | 303 ms | — |
| 2026-10-14 03:40 UTC | POST | pass | 402 | 512 ms | — |
| 2026-09-30 10:30 UTC | POST | pass | 402 | 381 ms | — |
| 2026-09-25 10:30 UTC | POST | pass | 402 | 348 ms | — |
| 2026-09-20 11:24 UTC | POST | pass | 402 | 357 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 230 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 272 ms | — |
| 2026-09-10 11:24 UTC | POST | pass | 402 | 229 ms | — |
| 2026-09-06 11:24 UTC | POST | pass | 402 | 351 ms | — |
| 2026-09-01 23:14 UTC | POST | pass | 402 | 351 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-08 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-01 | delisted | {"status":"active"} | {"status":"delisted"} |
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.