agent-treats-production.up.railway.app/api/palette
1.Catalog declaration
| Resource URL | https://agent-treats-production.up.railway.app/api/palette |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xbd65c2d2ac9d3df9ce77e5e2579b5b38efee36f0 |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-13 10:30 UTC | GET | pass | 402 | 28 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 84 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 137 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 84 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 2020 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 187 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 2165 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 454 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 39 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 224 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 76 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 269 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 238 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 260 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 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 |
|---|---|---|---|---|
| 09-05 12:072026-09-05 12:07 UTC | settled (nonce-bound) | 200 | 0xa7f8fbca…4282 | 1286 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose 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/13db57d9-3d5d-4284-bd4f-2f5f30245d31)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-11 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-27 | delisted | {"status":"active"} | {"status":"delisted"} |
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.