palmyr.ai/cards
1.Catalog declaration
| Resource URL | https://palmyr.ai/cards |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | GqSs5L9aPWGJwyRQe35YKQaWMDPh3R1dMqfSEPhSgkM |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | GET | pass | 402 | 2614 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 505 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 520 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 526 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 847 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 329 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 625 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 2242 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 444 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 307 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 478 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 693 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 373 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 495 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 398 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 438 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 375 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 478 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 571 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 276 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
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-16 00:012026-09-16 00:01 UTC | settled (nonce-bound) | 200 | 35wbZTa79D…GUsj | 3292 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-24 23:372026-08-24 23:37 UTC | settled (amount + payee) | 200 | 22urF5fSq5…NLJG | 2344 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-16 12:492026-08-16 12:49 UTC | settled (amount + payee) | 200 | 0x23c2f619…b4c3 | 1236 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 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/6b11ff0c-ce17-4f4c-a56d-fa9a63d672fe)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-27 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-26 | 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.