x402-factory.com/v1/edgar/events/material-agreement
1.Catalog declaration
| Resource URL | https://x402-factory.com/v1/edgar/events/material-agreement |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xcc42ed39a06b6cf3f484307ef76b88bf56fb305f |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 10:30 UTC | GET | pass | 402 | 9 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 9 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 28 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 374 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 35 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 11 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 11 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 28 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 17 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-09-09 14:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 9538 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 232 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 1121 ms | — |
| 2026-09-05 17:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 3531 ms | — |
| 2026-09-04 17:40 UTC | GET | pass | 402 | 947 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
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 |
|---|---|---|---|---|
| 08-19 12:122026-08-19 12:12 UTC | settled (amount + payee) | 200 | 0x06b733c4…6fea | 1358 ms |
| 20000 units (≈ $0.02 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/ac0aef00-76a9-4586-a2da-c403d66740c5)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.
About the purchase at 2026-08-19T12:12:58Z (UTC). The form starts with that time; add what you saw instead.