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

x402.browserbase.com/browser/session/sess_8f3a2b91-random-test-id/extend

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.browserbase.com/browser/session/sess_8f3a2b91-random-test-id/extend
Sourcecdp_bazaar
Declared methodPOST
Networkbase
Receiving address0x4a2bcb7b63242af10a8d4a47b8ef70b215a87c02
Declared price (base units)—
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-08-312026-09-23
Figure 1. Probe timeline, last 7 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-23 10:30 UTCPOSTfail402670 msmetadata_mismatch
2026-09-19 11:24 UTCPOSTfail402581 msmetadata_mismatch
2026-09-17 11:24 UTCPOSTfail402609 msmetadata_mismatch
2026-09-13 11:24 UTCPOSTfail402714 msmetadata_mismatch
2026-09-08 11:24 UTCPOSTfail402618 msmetadata_mismatch
2026-09-03 11:24 UTCPOSTfail402688 msmetadata_mismatch
2026-08-31 11:24 UTCPOSTfail402694 msmetadata_mismatch

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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