manyfish-seller.redcliff-d7368db1.westus2.azurecontainerapps.io/api/v1/content/url-to-markdown
1.Catalog declaration
| Resource URL | https://manyfish-seller.redcliff-d7368db1.westus2.azurecontainerapps.io/api/v1/content/url-to-markdown |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x9cd3f0d8a73a9a87f752f09d220652dc7de398cc |
| Declared price (base units) | 6000 |
| Catalog status | active |
| First seen / last seen | 2026-09-03 01:04 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 10:30 UTC | POST | pass | 402 | 226 ms | — |
| 2026-09-30 10:30 UTC | POST | pass | 402 | 317 ms | — |
| 2026-09-25 10:30 UTC | POST | pass | 402 | 315 ms | — |
| 2026-09-17 11:24 UTC | POST | fail | 404 | 77 ms | no_402HTTP 404 instead of 402 to an unpaid POST. |
| 2026-09-13 11:24 UTC | POST | pass | 402 | 72 ms | — |
| 2026-09-09 11:24 UTC | POST | pass | 402 | 98 ms | — |
| 2026-09-05 11:24 UTC | POST | pass | 402 | 184 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-25 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-17 | 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.