workbot1.oddsys.org/fx
1.Catalog declaration
| Resource URL | https://workbot1.oddsys.org/fx |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x15459498e1191d8787c83177809bd54022fa18c4 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-18 01:06 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | POST | pass | 402 | 894 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 399 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 737 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 518 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 661 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 544 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 1308 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 728 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 861 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 835 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 896 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 296 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 885 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 817 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 617 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 354 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 847 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 295 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 445 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 555 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 552 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 471 ms | — |
| 2026-09-10 11:24 UTC | POST | pass | 402 | 706 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 358 ms | — |
| 2026-09-01 23:14 UTC | POST | pass | 402 | 694 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-24 18:022026-09-24 18:02 UTC | settled (nonce-bound) | 200 | 0xa8ec7bc0…6172 | 1758 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-13 00:002026-09-13 00:00 UTC | settled (nonce-bound) | 200 | 0x278178d1…69f0 | 1778 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 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/1f7f7b49-f331-4a33-b9f4-be698f4cf049)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-09-24T18:02:04Z (UTC). The form starts with that time; add what you saw instead.