Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today
api.agentic-swarm-marketplace.com/x402/v1/ecosystem-pulse
1.Catalog declaration
| Resource URL | https://api.agentic-swarm-marketplace.com/x402/v1/ecosystem-pulse |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x408f39b19266022fec03076091e59d1f4f163658 |
| Declared price (base units) | 40000 |
| Catalog status | active |
| First seen / last seen | 2026-08-16 01:07 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-09-012026-10-20
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 708 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 2315 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 423 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 333 ms | — |
| 2026-10-14 12:40 UTC | GET | fail | 502 | 626 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 333 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 525 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 350 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 593 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 559 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 616 ms | — |
| 2026-09-06 11:24 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-01 23:14 UTC | GET | pass | 402 | 205 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-07 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-10 | 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.