Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-22 · today

x402.orthogonal.com/signalbase/companies

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.orthogonal.com/signalbase/companies
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0xdd51ae794f2cbbc69ef791be8aa4476d6d48c7ce
Declared price (base units)80000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-22 01:01 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-012026-10-22
Figure 1. Probe timeline, last 10 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-22 04:40 UTCGETpass402486 ms—
2026-10-04 10:30 UTCGETpass402330 ms—
2026-09-27 10:30 UTCGETpass402260 ms—
2026-09-22 11:24 UTCGETpass402204 ms—
2026-09-18 11:24 UTCGETpass402168 ms—
2026-09-16 11:24 UTCGETpass402109 ms—
2026-09-12 11:24 UTCGETpass40248 ms—
2026-09-08 11:24 UTCGETpass402223 ms—
2026-09-03 11:24 UTCGETpass40277 ms—
2026-09-01 11:24 UTCGETfail402284 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

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. We first send one confirmation email; nothing else goes out until you confirm.

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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far