palmyr.ai/phone/numbers
1.Catalog declaration
| Resource URL | https://palmyr.ai/phone/numbers |
| 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-09-05 01:03 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-04 23:40 UTC | GET | pass | 402 | 2150 ms | — |
| 2026-09-04 14:40 UTC | GET | pass | 402 | 325 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 960 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 587 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 516 ms | — |
| 2026-09-01 23:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-08-14 08:52 UTC | GET | pass | 402 | 146 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 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 4xx or 5xx counts as settled and not as delivered — definitions.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 08-29 12:092026-08-29 12:09 UTC | settled (amount + payee) | 200 | 4RgAytUaQD…iJZs | 2772 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declaration | ||||
| 08-21 12:212026-08-21 12:21 UTC | settled (amount + payee) | 200 | 2pUJvQaodN…TbPc | 2929 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declaration | ||||
| 08-14 09:572026-08-14 09:57 UTC | settled (amount + payee) | 200 | 0x61108934…dabe | 1791 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declaration | ||||
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 states a measurement, not a rating.
[](https://vet402.com/observatory/e/014445cc-62fc-4961-9044-d4e67b8ae583)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.