agenttalk.skyemeta.com/api/agenttalk/declare
1.Catalog declaration
| Resource URL | https://agenttalk.skyemeta.com/api/agenttalk/declare |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x40f90bd19b6cec99661f310a1d6b6442825df3b9 |
| Declared price (base units) | 500000 |
| Catalog status | active |
| First seen / last seen | 2026-10-16 01:03 UTC / 2026-11-12 16:05 UTC |
| Catalog-reported calls / payers (30d) | 6 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-11 16:40 UTC | POST | pass | 402 | 116 ms | — |
| 2026-11-09 13:40 UTC | POST | pass | 402 | 165 ms | — |
| 2026-11-07 04:40 UTC | POST | pass | 402 | 117 ms | — |
| 2026-11-05 04:40 UTC | POST | pass | 402 | 208 ms | — |
| 2026-11-02 04:40 UTC | POST | pass | 402 | 151 ms | — |
| 2026-10-30 22:40 UTC | POST | pass | 402 | 193 ms | — |
| 2026-10-29 04:40 UTC | POST | pass | 402 | 194 ms | — |
| 2026-10-27 06:40 UTC | POST | pass | 402 | 163 ms | — |
| 2026-10-25 15:40 UTC | POST | pass | 402 | 105 ms | — |
| 2026-10-23 13:40 UTC | POST | pass | 402 | 158 ms | — |
| 2026-10-21 22:40 UTC | POST | pass | 402 | 323 ms | — |
| 2026-10-20 13:40 UTC | POST | pass | 402 | 183 ms | — |
| 2026-10-18 22:40 UTC | POST | pass | 402 | 119 ms | — |
| 2026-10-17 16:40 UTC | POST | pass | 402 | 162 ms | — |
| 2026-10-16 10:30 UTC | POST | pass | 402 | 127 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. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. 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.
About the purchase at 2026-10-26T11:30:57Z (UTC). The form starts with that time; add what you saw instead.