api.dexl.io/api/agents
1.Catalog declaration
| Resource URL | https://api.dexl.io/api/agents |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0ccd097f92475d3eaf88e3b73e38a4dd4cb08667 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-30 01:02 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 21 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 604 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 704 ms | — |
| 2026-09-26 13:40 UTC | GET | fail | 502 | 505 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-09-25 22:40 UTC | GET | fail | 502 | 925 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 792 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 772 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 593 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 670 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 585 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 464 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 450 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 530 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 1553 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 666 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 1194 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 408 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 456 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 708 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 557 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 2527 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 451 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 740 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 472 ms | — |
| 2026-09-11 22:40 UTC | GET | fail | 402 | 565 ms | metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-11 04:40 UTC | GET | fail | 402 | 519 ms | metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-10 17:40 UTC | GET | fail | 402 | 211 ms | metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 229 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 382 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 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.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-19 18:002026-09-19 18:00 UTC | settled (nonce-bound) | 200 | 0x09a86b16…53ec | 3455 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-12 18:002026-09-12 18:00 UTC | settled (nonce-bound) | 200 | 0x04ad4538…56b5 | 6286 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-04 12:092026-09-04 12:09 UTC | settled (nonce-bound) | 200 | 0x623700b7…8df6 | 2300 ms |
| 1000 units (≈ $0.001 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/d8daf351-4f68-4e7a-b738-6be7ef2bef4f)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-28 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-27 | 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.
About the purchase at 2026-09-04T12:09:13Z (UTC). The form starts with that time; add what you saw instead.