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

agent402.tools/api/skill/structured-scrape

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://agent402.tools/api/skill/structured-scrape
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0
Declared price (base units)	23000
Catalog status	active
First seen / last seen	2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)	6 / 3

2.Probe history

2026-08-222026-10-20

Figure 1. Probe timeline, last 23 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-20 04:40 UTC	POST	pass	402	190 ms	—
2026-10-18 13:40 UTC	POST	pass	402	176 ms	—
2026-10-17 04:40 UTC	POST	pass	402	264 ms	—
2026-10-15 15:40 UTC	POST	pass	402	146 ms	—
2026-10-14 12:40 UTC	POST	pass	402	256 ms	—
2026-10-12 21:40 UTC	POST	pass	402	174 ms	—
2026-10-11 21:40 UTC	POST	pass	402	144 ms	—
2026-10-10 21:40 UTC	POST	pass	402	180 ms	—
2026-10-09 21:40 UTC	POST	pass	402	513 ms	—
2026-10-08 16:40 UTC	POST	pass	402	160 ms	—
2026-10-07 16:40 UTC	POST	pass	402	122 ms	—
2026-10-06 16:40 UTC	POST	fail	402	97 ms	price_mismatchDeclared 32000 of 0x8335…2913; the 402 offered 23000 of 0x8335…2913, 23000 of 0x3c49…3359, 23000 of 0xaf88…5831, 23000 of 0x7547…b603.
2026-10-05 10:30 UTC	POST	fail	402	104 ms	price_mismatchDeclared 32000 of 0x8335…2913; the 402 offered 23000 of 0x8335…2913, 23000 of 0x3c49…3359, 23000 of 0xaf88…5831, 23000 of 0x7547…b603.
2026-09-29 10:30 UTC	POST	fail	402	85 ms	price_mismatchDeclared 32000 of 0x8335…2913; the 402 offered 23000 of 0x8335…2913, 23000 of 0x3c49…3359, 23000 of 0xaf88…5831, 23000 of 0x7547…b603.
2026-09-29 07:38 UTC	POST	fail	402	139 ms	price_mismatchDeclared 32000 of 0x8335…2913; the 402 offered 23000 of 0x8335…2913, 23000 of 0x3c49…3359, 23000 of 0xaf88…5831, 23000 of 0x7547…b603.
2026-09-26 10:30 UTC	POST	fail	402	102 ms	price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 11:24 UTC	POST	fail	402	91 ms	price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 16:19 UTC	POST	fail	402	116 ms	price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 11:24 UTC	POST	fail	402	88 ms	price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-11 11:24 UTC	POST	fail	402	87 ms	price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-07 11:24 UTC	POST	fail	402	84 ms	price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-02 11:25 UTC	POST	pass	402	122 ms	—
2026-08-22 11:02 UTC	POST	fail	402	86 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

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 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 match: the response had the 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).

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	Latency
10-11 02:302026-10-11 02:30 UTC	settled (nonce-bound)	200	0x3797be0a…524e	16533 ms
23000 units (≈ $0.02 USDC) · L2 matchWhose 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/4b4c55c4-df74-4373-b11e-6a8487739434.svg)](https://vet402.com/observatory/e/4b4c55c4-df74-4373-b11e-6a8487739434)

4.Catalog listing events

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