x402.forgemesh.io/lobbying-filings
1.Catalog declaration
| Resource URL | https://x402.forgemesh.io/lobbying-filings |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x850363a27f0ac6feb9c7a3ec4c1d295262df9432 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-21 01:57 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | POST | pass | 402 | 140 ms | — |
| 2026-10-17 16:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-10-16 12:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-10-14 21:40 UTC | POST | pass | 402 | 169 ms | — |
| 2026-10-13 15:40 UTC | POST | pass | 402 | 716 ms | — |
| 2026-10-12 12:40 UTC | POST | pass | 402 | 131 ms | — |
| 2026-10-11 12:40 UTC | POST | pass | 402 | 105 ms | — |
| 2026-10-10 12:40 UTC | POST | pass | 402 | 47 ms | — |
| 2026-10-09 12:40 UTC | POST | pass | 402 | 22 ms | — |
| 2026-10-08 04:40 UTC | POST | pass | 402 | 105 ms | — |
| 2026-10-07 04:40 UTC | POST | pass | 402 | 227 ms | — |
| 2026-10-06 04:41 UTC | POST | pass | 402 | 77 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-10-03 22:40 UTC | POST | pass | 402 | 61 ms | — |
| 2026-10-03 04:40 UTC | POST | pass | 402 | 176 ms | — |
| 2026-10-02 13:40 UTC | POST | pass | 402 | 56 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 135 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 251 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 31 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 63 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 53 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 18 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 199 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 37 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 30 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 180 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 41 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 323 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 50 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 2147 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 (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-10 07:002026-09-10 07:00 UTC | settled (nonce-bound) | 200 | 0x1dfbaf05…4ae1 | 2965 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose 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/05d1357e-8ec9-4aa5-855d-16188f8cf9d2)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.