palmyr.ai/social/twitter/username
1.Catalog declaration
| Resource URL | https://palmyr.ai/social/twitter/username |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | GqSs5L9aPWGJwyRQe35YKQaWMDPh3R1dMqfSEPhSgkM |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 16:40 UTC | POST | pass | 402 | 545 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 535 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 523 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 280 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 174 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 1067 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 509 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 492 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 495 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 443 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 502 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 547 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 2157 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 369 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 456 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 523 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 584 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 503 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 504 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 430 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 608 ms | — |
| 2026-09-03 17:40 UTC | POST | pass | 402 | 316 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 255 ms | — |
| 2026-09-02 17:40 UTC | POST | pass | 402 | 258 ms | — |
| 2026-09-02 05:40 UTC | POST | pass | 402 | 393 ms | — |
| 2026-09-01 23:40 UTC | POST | pass | 402 | 447 ms | — |
| 2026-08-17 10:39 UTC | POST | pass | 402 | 417 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 0 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.
3 of those paid attempts are held as inconclusive rather than counted against this seller (3 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).
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).
settled_4xx- held_reason in the export: the payment settled, then the paid request got a 4xx.
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) | 400 | 2Ch7PMXKCE…Ceu3 | 2177 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted (held) | ||||
| 08-24 23:372026-08-24 23:37 UTC | settled (amount + payee) | 400 | 4D7t9A7j6E…vgSR | 2203 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
| 08-17 12:482026-08-17 12:48 UTC | settled (amount + payee) | 400 | 0xca15c925…c278 | 1583 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 0 delivered · 3 inconclusive 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/d85f0648-19f2-4c1b-ba25-ff477675cb74)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-04 | 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.