x402.forgemesh.io/agent-fortune
1.Catalog declaration
| Resource URL | https://x402.forgemesh.io/agent-fortune |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x850363a27f0ac6feb9c7a3ec4c1d295262df9432 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 22:40 UTC | POST | pass | 402 | 102 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 60 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 460 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 833 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 457 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 258 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 484 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 157 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 237 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 105 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 143 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 325 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 258 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 372 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 162 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 151 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 164 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 517 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 136 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 429 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 2200 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 133 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 151 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 31 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 111 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 51 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 108 ms | — |
| 2026-09-12 16:40 UTC | POST | fail | 530 | 8 ms | no_402HTTP 530 instead of 402 to an unpaid POST. |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 293 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.
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 no_declaration- the listing declares no output schema to check the response against.
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 |
|---|---|---|---|---|
| 10-02 15:312026-10-02 15:31 UTC | settled (nonce-bound) | 200 | 0xdbcfc14e…6a9f | 1030 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-26 06:012026-09-26 06:01 UTC | settled (nonce-bound) | 200 | 0xe6f32906…1d19 | 1096 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-09 07:002026-09-09 07:00 UTC | settled (nonce-bound) | 200 | 0xa7b892eb…43a4 | 1118 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose 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/2faa4c38-3695-4984-a2ac-51481cb8e314)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.