agents.dexl.io/v1/audio/speech
1.Catalog declaration
| Resource URL | https://agents.dexl.io/v1/audio/speech |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x820d61a720963fab63ab6e0aef4d1779eb42f6bb |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-10-26 13:05 UTC) |
| First seen / last seen | 2026-09-08 01:03 UTC / 2026-10-25 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-25 15:40 UTC | POST | fail | 502 | 517 ms | no_402HTTP 502 instead of 402 to an unpaid POST. |
| 2026-10-23 13:40 UTC | POST | pass | 402 | 936 ms | — |
| 2026-10-21 22:40 UTC | POST | pass | 402 | 1224 ms | — |
| 2026-10-20 13:40 UTC | POST | pass | 402 | 1254 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 880 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 979 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 881 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 1227 ms | — |
| 2026-10-13 03:40 UTC | POST | fail | — | 10003 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-12 03:40 UTC | POST | fail | 530 | 2282 ms | no_402HTTP 530 instead of 402 to an unpaid POST. |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 1578 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 689 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 907 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 2940 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 2628 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 865 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 675 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 711 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 709 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 617 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 591 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 627 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 630 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 706 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 296 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 649 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 347 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 550 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 885 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 936 ms | — |
3.L1 — real purchases
3 of 3 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example in the 402 (extensions.bazaar.info.output.example) counts as a declaration. When the catalog also declares an output, the example's top-level keys are required. When it does not, vet402 checks that the response is a JSON object or array, and the record page reads match (no required keys).
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Stage settled- vet402 re-read the payment on the chain. The paid request answered 202 Accepted, or HTTP 2xx with a body vet402 recorded as empty, or vet402 has no HTTP status on record, so vet402 does not call it delivered or not_delivered.
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 |
|---|---|---|---|---|---|
| 10-11 17:022026-10-11 17:02 UTC | settled (nonce-bound) | 200 | 0x040c36a1…47db | Base | 7490 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-01 12:022026-10-01 12:02 UTC | settled (nonce-bound) | 200 | 0x4bd9f113…a50b | Base | 6315 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 09-21 00:002026-09-21 00:00 UTC | settled (nonce-bound)tx from our index | — | 0x026a2568…8e05 | Base | — |
| 1000 units (≈ $0.001 USDC) · L2 —Whose side: not sorted: vet402 unprovenStage: settled | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 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/25cb1e61-13ee-4c7d-b965-e8f78bae4aed)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-26 | 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
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. 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.