api.getemboss.ai/pay/fill
1.Catalog declaration
| Resource URL | https://api.getemboss.ai/pay/fill |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x57a4ba72d5cf3f4fe01c65a23aa449522d063869 |
| Declared price (base units) | 70000 |
| Catalog status | active |
| First seen / last seen | 2026-09-06 01:03 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 22:40 UTC | POST | pass | 402 | 117 ms | — |
| 2026-10-19 13:40 UTC | POST | pass | 402 | 134 ms | — |
| 2026-10-17 22:40 UTC | POST | pass | 402 | 626 ms | — |
| 2026-10-16 15:40 UTC | POST | pass | 402 | 222 ms | — |
| 2026-10-14 21:40 UTC | POST | pass | 402 | 336 ms | — |
| 2026-10-13 21:40 UTC | POST | pass | 402 | 175 ms | — |
| 2026-10-12 12:40 UTC | POST | pass | 402 | 414 ms | — |
| 2026-10-11 12:40 UTC | POST | pass | 402 | 218 ms | — |
| 2026-10-10 12:40 UTC | POST | pass | 402 | 179 ms | — |
| 2026-10-09 12:40 UTC | POST | pass | 402 | 156 ms | — |
| 2026-10-08 04:40 UTC | POST | pass | 402 | 307 ms | — |
| 2026-10-07 04:40 UTC | POST | pass | 402 | 57 ms | — |
| 2026-10-06 04:41 UTC | POST | pass | 402 | 173 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 122 ms | — |
| 2026-10-04 04:40 UTC | POST | pass | 402 | 230 ms | — |
| 2026-09-29 10:31 UTC | POST | pass | 402 | 90 ms | — |
| 2026-09-24 10:30 UTC | POST | pass | 402 | 63 ms | — |
| 2026-09-20 11:24 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 75 ms | — |
| 2026-09-13 11:24 UTC | POST | pass | 402 | 78 ms | — |
| 2026-09-10 11:24 UTC | POST | fail | 400 | 79 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-06 11:24 UTC | POST | pass | 402 | 211 ms | — |
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
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.