Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-09-21 · 33 days ago

api.agishub.com/v1/embed

Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://api.agishub.com/v1/embed
Source	cdp_bazaar
Declared method	POST
Catalog network	eip155:8453
Receiving address	0x23fc725e8eaa1c58900c6507ba89be99a6dfc75d
Declared price (base units)	10000
Catalog status	delisted (since 2026-09-22 01:03 UTC)
First seen / last seen	2026-09-09 01:03 UTC / 2026-09-21 01:03 UTC
Catalog-reported calls / payers (30d)	3 / 3

2.Probe history

2026-09-092026-09-21

Figure 1. Probe timeline, last 10 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-21 16:40 UTC	POST	fail	410	426 ms	no_402HTTP 410 instead of 402 to an unpaid POST.
2026-09-20 22:40 UTC	POST	fail	410	42 ms	no_402HTTP 410 instead of 402 to an unpaid POST.
2026-09-20 04:40 UTC	POST	pass	402	46 ms	—
2026-09-19 13:40 UTC	POST	pass	402	39 ms	—
2026-09-18 16:40 UTC	POST	pass	402	853 ms	—
2026-09-18 04:40 UTC	POST	pass	402	199 ms	—
2026-09-17 13:40 UTC	POST	fail	—	10005 ms	timeoutNo response headers arrived within 10 seconds.
2026-09-16 11:24 UTC	POST	pass	402	7386 ms	—
2026-09-12 11:24 UTC	POST	pass	402	6120 ms	—
2026-09-09 11:24 UTC	POST	pass	402	722 ms	—

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 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 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 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 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 mismatch: the content type was not JSON although the listing marks required keys, or the body read in full did not parse as JSON, was JSON but not an object or array, or lacked a key the listing marks as required.
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).

1/1

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	Payment chain	Latency
09-17 06:012026-09-17 06:01 UTC	settled (nonce-bound)	200	0x473c9c75…d5a0	Base	2043 ms
10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/869bdb6b-31de-44e2-89b1-272eba6a07fd.svg)](https://vet402.com/observatory/e/869bdb6b-31de-44e2-89b1-272eba6a07fd)

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-09-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

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.