palmyr.ai/email/temp
1.Catalog declaration
| Resource URL | https://palmyr.ai/email/temp |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | GqSs5L9aPWGJwyRQe35YKQaWMDPh3R1dMqfSEPhSgkM |
| Declared price (base units) | 500000 |
| Catalog status | delisted (since 2026-09-20 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-19 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-19 13:40 UTC | POST | pass | 402 | 493 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 382 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 517 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 388 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 2339 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 499 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 556 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 487 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 574 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 379 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 423 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 200 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 489 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 189 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 217 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 425 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 155 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 191 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-09-06 17:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-06 05:40 UTC | POST | pass | 402 | 233 ms | — |
| 2026-09-05 17:40 UTC | POST | pass | 402 | 595 ms | — |
| 2026-09-05 05:40 UTC | POST | pass | 402 | 568 ms | — |
| 2026-09-04 14:40 UTC | POST | pass | 402 | 138 ms | — |
| 2026-09-04 05:40 UTC | POST | pass | 402 | 168 ms | — |
| 2026-09-03 17:40 UTC | POST | pass | 402 | 312 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-09-02 17:40 UTC | POST | pass | 402 | 229 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 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-17 12:072026-09-17 12:07 UTC | settled (nonce-bound) | 201 | 4NAtAunBQU…B8k4 | 2174 ms |
| 500000 units (≈ $0.50 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
| 08-23 12:432026-08-23 12:43 UTC | settled (amount + payee) | 201 | oTMiqUPJbA…ygm3 | 2440 ms |
| 500000 units (≈ $0.50 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
| 08-16 12:482026-08-16 12:48 UTC | settled (amount + payee) | 201 | 0xad9e9b15…2d05 | 2036 ms |
| 500000 units (≈ $0.50 USDC) · L2 not_checkedWhose 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/b1c2afe1-b275-41c8-b4e0-78c34fdf3f0a)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-20 | 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.