api.xona-agent.com/base-main/audio/x-text-to-speech
1.Catalog declaration
| Resource URL | https://api.xona-agent.com/base-main/audio/x-text-to-speech |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x515e7bce44baa5f6e42d16d4b5f27768e7f2f8cc |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | POST | pass | 402 | 4858 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 876 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 1168 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 3043 ms | — |
| 2026-09-25 16:40 UTC | POST | fail | — | 10002 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 1103 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 1031 ms | — |
| 2026-09-23 13:40 UTC | POST | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 5614 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 896 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 970 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 1274 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 773 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 942 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 1069 ms | — |
| 2026-09-17 16:40 UTC | POST | fail | 502 | 881 ms | no_402HTTP 502 instead of 402 to an unpaid POST. |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 923 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 976 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 824 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 936 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 1158 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 1043 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 904 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 359 ms | — |
| 2026-09-11 04:40 UTC | POST | pass | 402 | 884 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 863 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 987 ms | — |
| 2026-09-09 14:40 UTC | POST | pass | 402 | 884 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 898 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled with a receipt, and 0 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 5xx counts as settled and not as delivered — definitions.
4 of those paid attempts are held as inconclusive rather than counted against this seller (4 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-16 00:012026-09-16 00:01 UTC | settled (nonce-bound) | 400 | 0xb01027d1…2694 | 2883 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
| 08-28 12:202026-08-28 12:20 UTC | settled (amount + payee) | 400 | 0xf20f9bd7…4b80 | 2384 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
| 08-21 08:322026-08-21 08:32 UTC | settled (amount + payee) | 400 | 0xd313dfbf…2cbf | 2169 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
| 08-14 09:572026-08-14 09:57 UTC | settled (amount + payee) | 400 | 0xbed8f905…fd5e | 3371 ms |
| 10000 units (≈ $0.01 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 4/4 settled · 0 delivered · 4 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/5372b27f-6af8-4f3d-8f0f-12f6261660ce)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.
About the purchase at 2026-09-16T00:01:31Z (UTC). The form starts with that time; add what you saw instead.