edgar.apitoll.cloud/v1/edgar/filings
1.Catalog declaration
| Resource URL | https://edgar.apitoll.cloud/v1/edgar/filings |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x58bdad5e654691ac5ed4631758f3d8da00666b6c |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 46 / 27 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 614 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 693 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 432 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 399 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 423 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 465 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 420 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 763 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 383 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 322 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 327 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 311 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 521 ms | — |
| 2026-08-14 08:52 UTC | GET | fail | 402 | 97 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
2 of 2 paid attempts settled on-chain, and 2 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 match- the response had the fields the listing's output schema declares.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-25 12:022026-09-25 12:02 UTC | settled (nonce-bound) | 200 | 0xadbaff28…a479 | 1796 ms |
| 3000 units (≈ $0.003 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-19 06:012026-09-19 06:01 UTC | settled (nonce-bound) | 200 | 0x65671f10…8c5b | 1537 ms |
| 3000 units (≈ $0.003 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/b74fa00e-305c-4dcf-bcc2-e092f23b722f)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.