Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-10-06 · 18 days ago

craft-chronicles.everygoodwork.io/-/pay/play

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://craft-chronicles.everygoodwork.io/-/pay/play
Source	cdp_bazaar
Declared method	POST
Catalog network	eip155:8453
Receiving address	0x41364b9a1313edfa3adbb375776907cde1b7a0cf
Declared price (base units)	1000000
Catalog status	delisted (since 2026-10-08 13:03 UTC)
First seen / last seen	2026-09-07 01:03 UTC / 2026-10-07 13:03 UTC
Catalog-reported calls / payers (30d)	2 / 1

2.Probe history

2026-09-132026-10-06

Figure 1. Probe timeline, last 30 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-10-06 04:41 UTC	POST	fail	402	842 ms	metadata_mismatchDeclared payTo 0x4136…a0cf on eip155:8453; the 402 offered 0x1C1E…A8D5 on eip155:8453.
2026-10-04 22:40 UTC	POST	fail	402	764 ms	metadata_mismatchDeclared payTo 0x4136…a0cf on eip155:8453; the 402 offered 0x1C1E…A8D5 on eip155:8453.
2026-10-03 22:40 UTC	POST	fail	402	853 ms	metadata_mismatchDeclared payTo 0x4136…a0cf on eip155:8453; the 402 offered 0x1C1E…A8D5 on eip155:8453.
2026-10-03 04:40 UTC	POST	fail	200	2696 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-10-02 13:40 UTC	POST	fail	200	1940 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-10-01 13:40 UTC	POST	fail	—	10002 ms	timeoutNo response headers arrived within 10 seconds.
2026-09-30 16:40 UTC	POST	fail	200	3898 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-29 16:40 UTC	POST	fail	200	3250 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-28 22:40 UTC	POST	fail	200	2350 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-28 04:40 UTC	POST	fail	200	1948 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-27 13:40 UTC	POST	fail	200	3197 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-26 16:40 UTC	POST	fail	200	1821 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-25 22:40 UTC	POST	fail	200	2219 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-25 04:40 UTC	POST	fail	200	1642 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-24 13:40 UTC	POST	fail	200	2329 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-23 16:40 UTC	POST	fail	200	2364 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-22 22:40 UTC	POST	fail	200	2374 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-22 04:40 UTC	POST	fail	200	2801 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-21 13:40 UTC	POST	fail	200	2510 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-20 16:40 UTC	POST	fail	200	2178 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-19 22:40 UTC	POST	fail	200	1759 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-19 04:40 UTC	POST	fail	200	2435 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-18 16:40 UTC	POST	fail	200	2386 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-17 22:40 UTC	POST	fail	200	1685 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-17 04:40 UTC	POST	fail	200	2099 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-16 13:40 UTC	POST	fail	200	2714 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-15 16:40 UTC	POST	fail	200	1609 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-14 22:40 UTC	POST	fail	200	1227 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-14 04:40 UTC	POST	fail	200	1480 ms	no_402HTTP 200 instead of 402 to an unpaid POST.
2026-09-13 16:40 UTC	POST	fail	200	2043 ms	no_402HTTP 200 instead of 402 to an unpaid POST.

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 no_declaration: the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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-07 19:002026-09-07 19:00 UTC	settled (nonce-bound)	200	0x5e85b4eb…4e37	Base	4908 ms
1000000 units (≈ $1.00 USDC) · L2 no_declarationWhose 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/a8e9f542-6560-4e70-ab28-a55f85c6c77b.svg)](https://vet402.com/observatory/e/a8e9f542-6560-4e70-ab28-a55f85c6c77b)

4.Catalog listing events

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