api.deepentresearch.com/v1/agent/chat
1.Catalog declaration
| Resource URL | https://api.deepentresearch.com/v1/agent/chat |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x4d4405566355d43416aee248d9fb5abd3b0f636d |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-10-02 01:04 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 16:40 UTC | POST | pass | 402 | 231 ms | — |
| 2026-10-19 13:40 UTC | POST | fail | 402 | 368 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-17 16:40 UTC | POST | fail | 402 | 223 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-16 12:40 UTC | POST | fail | 402 | 392 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-14 21:40 UTC | POST | fail | 402 | 639 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-13 15:40 UTC | POST | fail | 402 | 1052 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-12 12:40 UTC | POST | fail | 402 | 439 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-11 12:40 UTC | POST | fail | 402 | 493 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-10 12:40 UTC | POST | fail | 402 | 546 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-09 12:40 UTC | POST | fail | 402 | 490 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-07 22:40 UTC | POST | fail | 402 | 600 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-07 04:40 UTC | POST | fail | 402 | 331 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-06 04:41 UTC | POST | fail | 402 | 473 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-04 16:40 UTC | POST | fail | 402 | 439 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-03 22:40 UTC | POST | fail | 402 | 681 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-03 04:40 UTC | POST | fail | 402 | 553 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-02 10:30 UTC | POST | fail | 402 | 494 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
| 2026-10-02 04:40 UTC | POST | fail | 402 | 327 ms | metadata_mismatchDeclared payTo 0xaf4e…c2e8 on eip155:8453; the 402 offered 0x4d44…636D on eip155:8453, 0x4d44…636D on eip155:8453. |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 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
settle_failed- vet402 signed a payment and got no settlement receipt back.
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 |
|---|---|---|---|---|
| 10-20 18:022026-10-20 18:02 UTC | settle_failed | — | — | 20325 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: not sorted: awaiting on-chain verification | ||||
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.