voice.forgemesh.io/v1/audio/speech
1.Catalog declaration
| Resource URL | https://voice.forgemesh.io/v1/audio/speech |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x962794fb8ad92941faf1ab446b9e30637b86f331 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 6 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | POST | pass | 402 | 142 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 97 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 194 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 166 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 96 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 281 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 546 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 212 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 103 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 118 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 291 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 71 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 92 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 92 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 77 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 63 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 114 ms | — |
| 2026-09-17 16:19 UTC | POST | pass | 402 | 420 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 74 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 212 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 305 ms | — |
| 2026-09-02 11:24 UTC | POST | fail | — | 10095 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-08-14 08:53 UTC | POST | fail | 402 | 40 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
1 of 1 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.
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 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
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-18 12:082026-09-18 12:08 UTC | settled (nonce-bound)tx from our index | — | 0x3194e8e9…cbea | — |
| 1000 units (≈ $0.001 USDC) · L2 —Whose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 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/9d078e45-01c0-4a9c-8f40-ef83772ab532)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.