api.agentcamo.xyz/sessions
1.Catalog declaration
| Resource URL | https://api.agentcamo.xyz/sessions |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x93958d39d88eb8372bb9c1c82c0d6c0c332848af |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-30 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 36 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 16:40 UTC | POST | fail | 525 | 497 ms | no_402HTTP 525 instead of 402 to an unpaid POST. |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 177 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 432 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 683 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 163 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 254 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 961 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 372 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 2223 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 221 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 170 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 164 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 178 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 138 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 135 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 535 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 239 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 155 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 256 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 199 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 218 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 234 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-10 11:24 UTC | POST | pass | 402 | 195 ms | — |
| 2026-08-24 11:11 UTC | POST | fail | 402 | 306 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 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 |
|---|---|---|---|---|
| 09-10 19:002026-09-10 19:00 UTC | settled (nonce-bound) | 201 | 0x4f884d1a…38f7 | 1262 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/5dd2f68a-9cf4-4477-a675-3c3e9c31c77d)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-30 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-10 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-02 | 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.