Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-29 · today

x402engine.app/api/tts/elevenlabs

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://x402engine.app/api/tts/elevenlabs
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x7dd5be069f2d2ead75ec7c3423b116ff043c2629
Declared price (base units)	20000
Catalog status	active
First seen / last seen	2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)	79 / 5

2.Probe history

2026-08-302026-09-29

Figure 1. Probe timeline, last 18 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-29 13:40 UTC	POST	pass	402	278 ms	—
2026-09-28 16:40 UTC	POST	pass	402	222 ms	—
2026-09-27 22:40 UTC	POST	pass	402	306 ms	—
2026-09-27 04:40 UTC	POST	pass	402	187 ms	—
2026-09-26 13:40 UTC	POST	pass	402	213 ms	—
2026-09-25 16:40 UTC	POST	pass	402	2627 ms	—
2026-09-24 22:40 UTC	POST	pass	402	139 ms	—
2026-09-24 04:40 UTC	POST	pass	402	243 ms	—
2026-09-23 13:40 UTC	POST	pass	402	786 ms	—
2026-09-22 16:40 UTC	POST	pass	402	356 ms	—
2026-09-21 22:40 UTC	POST	pass	402	205 ms	—
2026-09-21 13:40 UTC	POST	pass	402	256 ms	—
2026-09-18 11:24 UTC	POST	pass	402	260 ms	—
2026-09-15 11:24 UTC	POST	pass	402	147 ms	—
2026-09-11 11:24 UTC	POST	pass	402	232 ms	—
2026-09-08 11:24 UTC	POST	pass	402	159 ms	—
2026-09-03 11:24 UTC	POST	pass	402	105 ms	—
2026-08-30 11:24 UTC	POST	fail	402	238 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

2 of 2 paid attempts settled on-chain, and 2 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.

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.
L2 no_declaration: the listing declares no output schema to check the response against.
L2 mismatch: the response lacked fields the listing's output schema declares.
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).

2/2

Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.

L1 purchase history, newest first
Attempted at	Result	HTTP	On-chain tx	Latency
09-29 18:012026-09-29 18:01 UTC	settled (nonce-bound)	200	0x3a9d2d05…5087	4049 ms
20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered)
09-22 00:002026-09-22 00:00 UTC	settled (nonce-bound)	200	0x7b779aa4…cc20	3626 ms
20000 units (≈ $0.02 USDC) · L2 mismatchWhose 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.

[![vet402 receipt](https://vet402.com/api/badge/endpoint/20b944e5-97dc-4057-bc24-a846b9ef32da.svg)](https://vet402.com/observatory/e/20b944e5-97dc-4057-bc24-a846b9ef32da)

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-08-27	settle_drop	`{"calls30d":184}`	`{"calls30d":34}`

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.