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

agent.connskill.com/v1/domain-tech

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://agent.connskill.com/v1/domain-tech
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x43b85ae58f0a2505c710bc715d6f3eb16b1f63de
Declared price (base units)50000
Catalog statusactive
First seen / last seen2026-08-27 01:15 UTC / 2026-09-09 01:03 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-09-022026-09-09
Figure 1. Probe timeline, last 15 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-09 05:40 UTCPOSTpass402720 ms—
2026-09-08 17:40 UTCPOSTfail402399 msprice_mismatch
2026-09-07 23:40 UTCPOSTfail402371 msprice_mismatch
2026-09-07 14:40 UTCPOSTfail402444 msprice_mismatch
2026-09-06 23:40 UTCPOSTfail402391 msprice_mismatch
2026-09-06 14:40 UTCPOSTfail402335 msprice_mismatch
2026-09-05 23:40 UTCPOSTfail402532 msprice_mismatch
2026-09-05 14:40 UTCPOSTfail402443 msprice_mismatch
2026-09-04 23:40 UTCPOSTfail402352 msprice_mismatch
2026-09-04 14:40 UTCPOSTfail402363 msprice_mismatch
2026-09-03 23:40 UTCPOSTfail402370 msprice_mismatch
2026-09-03 14:40 UTCPOSTpass4022432 ms—
2026-09-02 23:40 UTCPOSTpass402353 ms—
2026-09-02 14:40 UTCPOSTpass402313 ms—
2026-09-02 05:40 UTCPOSTpass402416 ms—

3.L1 — real purchases

0 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.

0/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-09 07:00settle_failed400—483 ms
50000 units (≈ $0.05 USDC) · L2 not_checked

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.