Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-02 · 1 day ago
trabotpro.it/api/a2a/x402/morning-brief/promo
1.Catalog declaration
| Resource URL | https://trabotpro.it/api/a2a/x402/morning-brief/promo |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x175562431dfcb38ab3a1762b7fc1fbc08a93bbbb |
| Declared price (base units) | 60000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 6 / 1 |
2.Probe history
2026-08-212026-10-02
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 22:40 UTC | GET | pass | 402 | 751 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 534 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 943 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 682 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 581 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 654 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 1345 ms | — |
| 2026-09-26 10:30 UTC | GET | pass | 402 | 693 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 669 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 600 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 578 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 573 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 504 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 449 ms | — |
| 2026-08-21 10:55 UTC | GET | fail | 402 | 613 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
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.