Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-12 · 25 days ago

agents.withzero.xyz/api/v1/audio/speech/gemini-3.1-flash-tts

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://agents.withzero.xyz/api/v1/audio/speech/gemini-3.1-flash-tts
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x4a7e38e5b2a9325e996a5a155ebdb2dd4181d974
Declared price (base units)	160000
Catalog status	delisted (since 2026-09-13 01:03 UTC)
First seen / last seen	2026-08-14 08:52 UTC / 2026-09-12 01:03 UTC
Catalog-reported calls / payers (30d)	4 / 1

2.Probe history

2026-08-252026-09-12

Figure 1. Probe timeline, last 4 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-12 11:24 UTC	POST	fail	402	1703 ms	metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-08 11:24 UTC	POST	fail	402	1365 ms	metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-03 11:24 UTC	POST	fail	402	5558 ms	metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-08-25 10:47 UTC	POST	fail	402	1262 ms	metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-09-13	delisted	`{"status":"active"}`	`{"status":"delisted"}`
2026-08-31	relisted	`{"status":"delisted"}`	`{"status":"active"}`
2026-08-30	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

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.