Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-26 · today
vet402Back to the registerMethodology

agent402.tools/api/skill/macro-context

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://agent402.tools/api/skill/macro-context
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0
Declared price (base units)41000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)3 / 1

2.Probe history

2026-09-072026-09-26
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 atMethodVerdictHTTPLatencyReason
2026-09-26 22:40 UTCPOSTfail402127 msprice_mismatch
2026-09-26 04:40 UTCPOSTfail402145 msprice_mismatch
2026-09-25 13:40 UTCPOSTfail402261 msprice_mismatch
2026-09-24 16:40 UTCPOSTfail402116 msprice_mismatch
2026-09-23 22:40 UTCPOSTpass402105 ms—
2026-09-23 04:40 UTCPOSTpass40294 ms—
2026-09-22 13:40 UTCPOSTfail40283 msprice_mismatch
2026-09-21 22:40 UTCPOSTfail402158 msprice_mismatch
2026-09-21 04:40 UTCPOSTfail402108 msprice_mismatch
2026-09-20 13:40 UTCPOSTfail40295 msprice_mismatch
2026-09-19 16:40 UTCPOSTfail402277 msprice_mismatch
2026-09-18 22:40 UTCPOSTfail40295 msprice_mismatch
2026-09-18 04:40 UTCPOSTfail402116 msprice_mismatch
2026-09-17 16:40 UTCPOSTfail402278 msprice_mismatch
2026-09-16 22:40 UTCPOSTfail402252 msprice_mismatch
2026-09-15 22:40 UTCPOSTfail4022118 msprice_mismatch
2026-09-15 13:40 UTCPOSTfail402166 msprice_mismatch
2026-09-14 16:40 UTCPOSTfail40286 msprice_mismatch
2026-09-14 04:40 UTCPOSTfail40284 msprice_mismatch
2026-09-13 13:40 UTCPOSTfail40283 msprice_mismatch
2026-09-12 22:40 UTCPOSTfail402139 msprice_mismatch
2026-09-12 04:40 UTCPOSTfail402102 msprice_mismatch
2026-09-11 16:40 UTCPOSTfail402153 msprice_mismatch
2026-09-11 04:40 UTCPOSTfail402154 msprice_mismatch
2026-09-10 14:40 UTCPOSTfail402104 msprice_mismatch
2026-09-09 23:40 UTCPOSTfail40292 msprice_mismatch
2026-09-09 14:40 UTCPOSTfail402726 msprice_mismatch
2026-09-08 23:40 UTCPOSTfail402116 msprice_mismatch
2026-09-08 05:40 UTCPOSTfail402116 msprice_mismatch
2026-09-07 17:40 UTCPOSTfail402122 msprice_mismatch

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 5xx counts as settled and not as delivered — definitions.

A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).

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 atResultHTTPReceipt (tx)Latency
09-23 06:01settled (nonce-bound)tx from our index—0xc71452d1…855520166 ms
41000 units (≈ $0.04 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 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: 1 of 1 paid attempts settled with an on-chain receipt, and 0 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (agent402.tools · measured 2026-09-23)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/171a1cc3-85be-40c8-8f19-74da002b6679.svg)](https://vet402.com/observatory/e/171a1cc3-85be-40c8-8f19-74da002b6679)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

4.Catalog listing events

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

agent402.tools/api/skill/macro-context — L0 observations | vet402