api.craigmbrown.com/v1/services/research.topic-deep-researcher
1.Catalog declaration
| Resource URL | https://api.craigmbrown.com/v1/services/research.topic-deep-researcher |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x5e709929a4ab69ec3a8811d03417869059bc4eb9 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 10:30 UTC | POST | pass | 402 | 138 ms | — |
| 2026-08-19 10:56 UTC | POST | pass | 402 | 40 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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 (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 | On-chain tx | Latency |
|---|---|---|---|---|
| 08-25 12:532026-08-25 12:53 UTC | settled (amount + payee) | 202 | 0xed8ddd8f…15b5 | 1062 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: not sorted: paid, no result in the answer | ||||
| 08-19 12:122026-08-19 12:12 UTC | settled (amount + payee) | 202 | 0x0518ef67…da7b | 1042 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: not sorted: paid, no result in the answer | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 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.
[](https://vet402.com/observatory/e/b981e2e2-81e4-4b7a-839b-4b779c517332)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-30 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-26 | delisted | {"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.