api.linkedpanda.com/agent/v1/jobs/search
1.Catalog declaration
| Resource URL | https://api.linkedpanda.com/agent/v1/jobs/search |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xe740d5701749d262da5e4fcb9f814c5b6d91cf46 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | POST | pass | 402 | 158 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 481 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 449 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 385 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 564 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 407 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 749 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 458 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 2582 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 397 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 249 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 140 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 1217 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 522 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 508 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 592 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 620 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 685 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 377 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 342 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 461 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 362 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 401 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 486 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 710 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 550 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 179 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 400 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 2109 ms | — |
| 2026-09-09 14:40 UTC | POST | pass | 402 | 219 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled with a receipt, and 4 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
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
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).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-10 12:092026-09-10 12:09 UTC | settled (nonce-bound) | 201 | 0x82887c8c…60f8 | 2958 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
| 08-31 12:072026-08-31 12:07 UTC | settled (amount + payee) | 201 | 0x9339ace4…8fcf | 4066 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
| 08-24 23:342026-08-24 23:34 UTC | settled (amount + payee) | 201 | 0xc83c2c90…a8ea | 4631 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
| 08-17 12:472026-08-17 12:47 UTC | settled (amount + payee) | 201 | 0x8b013db5…8628 | 9706 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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.
[](https://vet402.com/observatory/e/cdf2e412-de3e-4882-9b60-00c9bf70a69f)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.
About the purchase at 2026-08-31T12:07:39Z (UTC). The form starts with that time; add what you saw instead.