agentsonly.vip/mint
1.Catalog declaration
| Resource URL | https://agentsonly.vip/mint |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | base |
| Receiving address | 0x632730a7852e6a002fa62509c78783dd500faded |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | POST | pass | 402 | 523 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 350 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 244 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 188 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 2229 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 194 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 290 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 340 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 152 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 205 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 297 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 302 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 333 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 457 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 91 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 376 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 499 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 201 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 281 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 272 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 178 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 287 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 301 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 204 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 227 ms | — |
| 2026-09-11 04:40 UTC | POST | pass | 402 | 1299 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 5234 ms | — |
3.L1 — real purchases
3 of 4 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.
1 of the paid attempts failed on vet402's side (for example our wallet was out of USDC, or we did not send the input the listing declares). The rows stay in the table; the embeddable badge below leaves them out of its count and names them as “vet402 side”.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
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.
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-12 18:022026-09-12 18:02 UTC | settle_failed | 502 | — | 416 ms |
| 1000000 units (≈ $1.00 USDC) · L2 not_checkedWhose side: vet402's side | ||||
| 08-30 12:072026-08-30 12:07 UTC | settled (amount + payee) | 200 | 0xe90d4e69…394f | 1532 ms |
| 1000000 units (≈ $1.00 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-23 12:422026-08-23 12:42 UTC | settled (amount + payee) | 200 | 0x99934835…c06d | 5435 ms |
| 1000000 units (≈ $1.00 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-15 12:482026-08-15 12:48 UTC | settled (amount + payee) | 200 | 0x0718ee72…fd9f | 5337 ms |
| 1000000 units (≈ $1.00 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 · vet402 side 1 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/9db6b9f4-cb26-4ada-a077-c4e2636a8411)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.