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

agent402.tools/api/skill/api-health

1.Catalog declaration

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

2.Probe history

2026-09-052026-09-26
Figure 1. Probe timeline, last 29 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 UTCPOSTpass402226 ms—
2026-09-26 04:40 UTCPOSTpass402125 ms—
2026-09-25 13:40 UTCPOSTpass402313 ms—
2026-09-24 16:40 UTCPOSTpass402121 ms—
2026-09-23 22:40 UTCPOSTpass402128 ms—
2026-09-23 04:40 UTCPOSTpass402366 ms—
2026-09-22 13:40 UTCPOSTfail402388 msprice_mismatch
2026-09-21 16:40 UTCPOSTfail402241 msprice_mismatch
2026-09-20 22:40 UTCPOSTfail4021947 msprice_mismatch
2026-09-20 04:40 UTCPOSTfail402525 msprice_mismatch
2026-09-19 13:40 UTCPOSTfail40291 msprice_mismatch
2026-09-18 22:40 UTCPOSTfail402428 msprice_mismatch
2026-09-18 04:40 UTCPOSTfail4022226 msprice_mismatch
2026-09-17 13:40 UTCPOSTfail402370 msprice_mismatch
2026-09-16 16:40 UTCPOSTfail402127 msprice_mismatch
2026-09-15 22:40 UTCPOSTfail4022152 msprice_mismatch
2026-09-15 04:40 UTCPOSTfail402277 msprice_mismatch
2026-09-14 16:40 UTCPOSTfail402177 msprice_mismatch
2026-09-13 22:40 UTCPOSTfail40294 msprice_mismatch
2026-09-13 13:40 UTCPOSTfail402105 msprice_mismatch
2026-09-12 16:40 UTCPOSTfail402375 msprice_mismatch
2026-09-12 04:40 UTCPOSTfail402111 msprice_mismatch
2026-09-11 16:40 UTCPOSTfail402269 msprice_mismatch
2026-09-10 23:40 UTCPOSTfail402323 msprice_mismatch
2026-09-10 14:40 UTCPOSTfail40293 msprice_mismatch
2026-09-09 23:40 UTCPOSTfail402106 msprice_mismatch
2026-09-09 11:24 UTCPOSTfail402148 msprice_mismatch
2026-09-06 11:24 UTCPOSTfail402143 msprice_mismatch
2026-09-05 11:24 UTCPOSTfail402129 msprice_mismatch

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 1 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.

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)2000x83d97a14…8f941781 ms
5000 units (≈ $0.005 USDC) · L2 match

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: 1 of 1 paid attempts settled with an on-chain receipt, and 1 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/71dc3b2a-51d1-4121-be8c-45338509de15.svg)](https://vet402.com/observatory/e/71dc3b2a-51d1-4121-be8c-45338509de15)

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

No listing changes observed.

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.