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

x402.orthogonal.com/serper/search

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.orthogonal.com/serper/search
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x1563cde0042d17f53b23d91fd9b73ace9da26a09
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-09-262026-09-27
Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-27 04:40 UTCPOSTpass402421 ms—
2026-09-26 10:30 UTCPOSTpass402285 ms—

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-27 06:01settled (nonce-bound)2000xda15fd61…33be3009 ms
2000 units (≈ $0.002 USDC) · L2 no_declaration

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. (x402.orthogonal.com · measured 2026-09-27)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/b864a847-cb54-46f5-af92-23827955de8b.svg)](https://vet402.com/observatory/e/b864a847-cb54-46f5-af92-23827955de8b)

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-26relisted{"status":"delisted"}{"status":"active"}
2026-08-26delisted{"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.