voidfeed.ai/v1/tools/extract/graph
1.Catalog declaration
| Resource URL | https://voidfeed.ai/v1/tools/extract/graph |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x71033ab6ed376a0b53d1826ea632ddfec96b3661 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 5 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | GET | pass | 402 | 482 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 484 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 444 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 428 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 1020 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 433 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 335 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 653 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 852 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 585 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 551 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 491 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 581 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 367 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 480 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 493 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 482 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 315 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 324 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 2214 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 598 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 499 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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 mismatch- the response lacked 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-27 18:022026-09-27 18:02 UTC | settled (nonce-bound)tx from our index | 200 | 0x2758e9df…51a5 | 2580 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-17 18:012026-09-17 18:01 UTC | settled (nonce-bound)tx from our index | 200 | 0xa22945df…03c5 | 1957 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-11 06:012026-09-11 06:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x96d929f2…f69f | 1790 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/a761e961-48fe-4de6-8fd3-154b678df0b8)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.