voice.madebydevx.com/v1/tts
1.Catalog declaration
| Resource URL | https://voice.madebydevx.com/v1/tts |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0xb3cddccee6b150c8effd55b961afc0ecefe7f247 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-10-23 01:01 UTC / 2026-11-12 16:05 UTC |
| Catalog-reported calls / payers (30d) | 34 / 10 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-10 22:40 UTC | POST | pass | 402 | 163 ms | — |
| 2026-11-08 16:40 UTC | POST | pass | 402 | 396 ms | — |
| 2026-11-06 13:40 UTC | POST | pass | 402 | 311 ms | — |
| 2026-11-04 06:41 UTC | POST | pass | 402 | 542 ms | — |
| 2026-11-01 10:30 UTC | POST | pass | 402 | 278 ms | — |
| 2026-10-31 16:40 UTC | POST | fail | 402 | 271 ms | metadata_mismatchDeclared payTo 0xe30c…40db on eip155:8453; the 402 offered 0xB3cD…f247 on eip155:8453, 0xB3cD…f247 on eip155:137, 0xB3cD…f247 on eip155:42161, 0xB3cD…f247 on eip155:42161. |
| 2026-10-29 16:40 UTC | POST | fail | 402 | 373 ms | metadata_mismatchDeclared payTo 0xe30c…40db on eip155:8453; the 402 offered 0xB3cD…f247 on eip155:8453, 0xB3cD…f247 on eip155:137, 0xB3cD…f247 on eip155:42161, 0xB3cD…f247 on eip155:42161. |
| 2026-10-27 22:40 UTC | POST | fail | 402 | 245 ms | metadata_mismatchDeclared payTo 0xe30c…40db on eip155:8453; the 402 offered 0xB3cD…f247 on eip155:8453, 0xB3cD…f247 on eip155:137, 0xB3cD…f247 on eip155:42161, 0xB3cD…f247 on eip155:42161. |
| 2026-10-26 00:40 UTC | POST | pass | 402 | 103 ms | — |
| 2026-10-24 10:31 UTC | POST | pass | 402 | 35 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 11-01 12:012026-11-01 12:01 UTC | settled (nonce-bound) | 200 | 0x60e4c0e2…8d79 | Avalanche C-Chain | 2446 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | |||||
| 10-25 11:302026-10-25 11:30 UTC | settled (nonce-bound) | 200 | 0xa064fd06…f3c1 | Arbitrum One | 2548 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/ced24074-25a5-45ac-ba9f-4acec23e32e9)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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.
About the purchase at 2026-11-01T12:01:01Z (UTC). The form starts with that time; add what you saw instead.