page.fluidrack.com/v1/pages
1.Catalog declaration
| Resource URL | https://page.fluidrack.com/v1/pages |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xa51701c330992d1c3997551b2d69a14ac402c29e |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-27 01:15 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 1064 ms | — |
| 2026-10-18 13:40 UTC | POST | pass | 402 | 509 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 775 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 642 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 724 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 558 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 762 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 1750 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 2455 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 556 ms | — |
| 2026-10-07 13:40 UTC | POST | pass | 402 | 694 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 469 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 407 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 2359 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 483 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 485 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 625 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 386 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 900 ms | — |
| 2026-09-27 10:30 UTC | POST | pass | 402 | 493 ms | — |
| 2026-09-22 11:25 UTC | POST | pass | 402 | 439 ms | — |
| 2026-09-19 11:24 UTC | POST | pass | 402 | 443 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 497 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 376 ms | — |
| 2026-09-09 11:24 UTC | POST | pass | 402 | 503 ms | — |
| 2026-09-04 11:24 UTC | POST | pass | 402 | 396 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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-10 20:312026-10-10 20:31 UTC | settled (nonce-bound) | 200 | 0xbf2eebe1…702e | 2132 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-30 09:312026-09-30 09:31 UTC | settled (nonce-bound) | 200 | 0x06944e2d…1c88 | 1806 ms |
| 10000 units (≈ $0.01 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/086f4c8a-726c-48d9-8491-8e48d806a23a)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.