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

api.linkedpanda.com/agent/v1/companies/search

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.linkedpanda.com/agent/v1/companies/search
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xe740d5701749d262da5e4fcb9f814c5b6d91cf46
Declared price (base units)300000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-092026-09-28
Figure 1. Probe timeline, last 30 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-09-28 22:40 UTCPOSTpass402489 ms—
2026-09-28 04:40 UTCPOSTpass402582 ms—
2026-09-27 13:40 UTCPOSTpass402474 ms—
2026-09-26 16:40 UTCPOSTpass402460 ms—
2026-09-25 22:40 UTCPOSTpass402581 ms—
2026-09-25 04:40 UTCPOSTpass402825 ms—
2026-09-24 13:40 UTCPOSTpass402512 ms—
2026-09-23 16:40 UTCPOSTpass4021055 ms—
2026-09-22 22:40 UTCPOSTpass402705 ms—
2026-09-22 04:40 UTCPOSTpass402399 ms—
2026-09-21 13:40 UTCPOSTpass402367 ms—
2026-09-20 16:40 UTCPOSTpass402862 ms—
2026-09-19 22:40 UTCPOSTpass402346 ms—
2026-09-19 04:40 UTCPOSTpass402380 ms—
2026-09-18 16:40 UTCPOSTpass402617 ms—
2026-09-17 22:40 UTCPOSTpass402402 ms—
2026-09-17 04:40 UTCPOSTpass402354 ms—
2026-09-16 16:40 UTCPOSTpass402594 ms—
2026-09-15 16:40 UTCPOSTpass402468 ms—
2026-09-14 22:40 UTCPOSTpass402721 ms—
2026-09-14 13:40 UTCPOSTpass402425 ms—
2026-09-13 16:40 UTCPOSTpass402473 ms—
2026-09-13 04:40 UTCPOSTpass402349 ms—
2026-09-12 13:40 UTCPOSTpass4022338 ms—
2026-09-11 22:40 UTCPOSTpass402528 ms—
2026-09-11 13:40 UTCPOSTpass402191 ms—
2026-09-10 17:40 UTCPOSTpass402415 ms—
2026-09-10 05:40 UTCPOSTpass402457 ms—
2026-09-09 17:40 UTCPOSTpass402652 ms—
2026-09-09 05:40 UTCPOSTpass402671 ms—

3.L1 — real purchases

2 of 3 paid attempts settled with a receipt, and 2 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.

Terms in this table

settle_failed
vet402 signed a payment and got no settlement receipt back.
settled (amount + payee)
vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 not_checked
not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
2/3
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-12 18:02settle_failed500—3732 ms
300000 units (≈ $0.30 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven
09-01 12:08settled (amount + payee)2010x682d20f8…33e88542 ms
300000 units (≈ $0.30 USDC) · L2 not_checkedWhose side: no failure (delivered)
08-25 12:53settled (amount + payee)2010xd9ba9b1c…f73b5078 ms
300000 units (≈ $0.30 USDC) · L2 not_checkedWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/3 settled · 2 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: 2 of 3 paid attempts settled with an on-chain receipt, and 2 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. (api.linkedpanda.com · measured 2026-09-12)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/8ba8d2e2-1902-400c-a77e-c03cd1272759.svg)](https://vet402.com/observatory/e/8ba8d2e2-1902-400c-a77e-c03cd1272759)

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-09relisted{"status":"delisted"}{"status":"active"}
2026-09-08delisted{"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.

About the purchase at 2026-09-12T18:02:04Z (UTC). The form starts with that time; add what you saw instead.