x402.orthogonal.com/apollo/api/v1/mixed_companies/search
1.Catalog declaration
| Resource URL | https://x402.orthogonal.com/apollo/api/v1/mixed_companies/search |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xccd231829e24b42195b500028f8779b8f8b1131a |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 116 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-10-18 04:40 UTC | POST | pass | 402 | 168 ms | — |
| 2026-10-16 21:40 UTC | POST | pass | 402 | 308 ms | — |
| 2026-10-15 12:40 UTC | POST | pass | 402 | 156 ms | — |
| 2026-10-14 03:40 UTC | POST | pass | 402 | 250 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 276 ms | — |
| 2026-10-11 15:40 UTC | POST | pass | 402 | 97 ms | — |
| 2026-10-10 15:40 UTC | POST | pass | 402 | 95 ms | — |
| 2026-10-09 15:40 UTC | POST | pass | 402 | 123 ms | — |
| 2026-10-08 13:40 UTC | POST | pass | 402 | 262 ms | — |
| 2026-10-07 13:40 UTC | POST | pass | 402 | 579 ms | — |
| 2026-10-06 13:40 UTC | POST | pass | 402 | 311 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 181 ms | — |
| 2026-10-04 04:40 UTC | POST | pass | 402 | 143 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 61 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 246 ms | — |
| 2026-10-01 16:40 UTC | POST | pass | 402 | 347 ms | — |
| 2026-09-30 22:40 UTC | POST | pass | 402 | 122 ms | — |
| 2026-09-30 04:40 UTC | POST | pass | 402 | 267 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 435 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 435 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 342 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 303 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 2505 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 1825 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 290 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 154 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 143 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 339 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 404 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). 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.
L2 no_declaration- the listing declares no output schema to check the response against.
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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-25 18:022026-09-25 18:02 UTC | settled (nonce-bound) | 200 | 0x6a2410f4…c67c | 5279 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-15 23:492026-09-15 23:49 UTC | settled (nonce-bound) | 200 | 0x712ea6f9…9cad | 2937 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-09 19:002026-09-09 19:00 UTC | settled (nonce-bound) | 200 | 0xa87ca3e1…2775 | 13269 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/6710666d-65f4-471f-870b-604a8f33caa2)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.