Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago

x402.orthogonal.com/predictleads/v3/companies/stripe.com/financing_events

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.orthogonal.com/predictleads/v3/companies/stripe.com/financing_events
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xca37de138574432b96f92b0cd9826dadfd1cf443
Declared price (base units)40000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-09-012026-10-19
Figure 1. Probe timeline, last 19 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-10-19 16:40 UTCGETpass402136 ms—
2026-10-17 22:40 UTCGETpass402181 ms—
2026-10-16 15:40 UTCGETpass402410 ms—
2026-10-15 03:40 UTCGETpass402311 ms—
2026-10-13 21:40 UTCGETpass402581 ms—
2026-10-12 15:40 UTCGETpass402708 ms—
2026-10-11 15:40 UTCGETpass402283 ms—
2026-10-10 15:40 UTCGETpass402544 ms—
2026-10-09 15:40 UTCGETpass402458 ms—
2026-10-08 04:40 UTCGETpass402184 ms—
2026-10-07 13:40 UTCGETpass402616 ms—
2026-09-30 10:30 UTCGETpass4021271 ms—
2026-09-25 10:30 UTCGETpass40284 ms—
2026-09-20 11:24 UTCGETpass4021212 ms—
2026-09-17 12:35 UTCGETpass402283 ms—
2026-09-14 11:24 UTCGETpass402191 ms—
2026-09-10 11:24 UTCGETpass402186 ms—
2026-09-06 11:24 UTCGETpass402327 ms—
2026-09-01 23:13 UTCGETpass402132 ms—

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

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.

20–2,000 characters · 0 so far