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

agents.withzero.xyz/api/v1/image/images/grok-imagine

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://agents.withzero.xyz/api/v1/image/images/grok-imagine
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x9811c0900fcb719bbc363a3846d2d6db2771dea8
Declared price (base units)	50000
Catalog status	active
First seen / last seen	2026-08-14 08:52 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)	17 / 1

2.Probe history

2026-08-282026-09-04

Figure 1. Probe timeline, last 7 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-04 23:40 UTC	POST	pass	402	552 ms	—
2026-09-04 14:40 UTC	POST	pass	402	595 ms	—
2026-09-03 23:40 UTC	POST	pass	402	344 ms	—
2026-09-03 14:40 UTC	POST	pass	402	463 ms	—
2026-09-02 23:40 UTC	POST	pass	402	469 ms	—
2026-09-02 14:40 UTC	POST	pass	402	434 ms	—
2026-08-28 11:00 UTC	POST	pass	402	563 ms	—

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 4xx or 5xx counts as settled and not as delivered — definitions.

1/1

Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.

L1 purchase history, newest first
Attempted at	Result	HTTP	Receipt (tx)	Latency
09-05 01:012026-09-05 01:01 UTC	settled (nonce-bound)	400	0x7b569ba4…9219	2321 ms
50000 units (≈ $0.05 USDC) · L2 not_checked

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 states a measurement, not a rating.

[![vet402 receipt](https://vet402.com/api/badge/endpoint/576bee15-37a9-4a94-93c4-be08599914af.svg)](https://vet402.com/observatory/e/576bee15-37a9-4a94-93c4-be08599914af)

4.Catalog listing events

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