www.getbags.app/api/agent/link/pl-5f9ac407-7cb6-45b9-b4eb-8beb4f22aad3
1.Catalog declaration
| Resource URL | https://www.getbags.app/api/agent/link/pl-5f9ac407-7cb6-45b9-b4eb-8beb4f22aad3 |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0e56d32e4c556a7c429aa2dc83e3890a018c052e |
| Declared price (base units) | 10000 |
| 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 13:40 UTC | GET | pass | 402 | 930 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 2254 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 1880 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 1379 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 470 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 2110 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 674 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 1336 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 2451 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 935 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 1991 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 1861 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 634 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 1854 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 499 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 1771 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 838 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 2639 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 651 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 538 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 636 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 2551 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 2072 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 1348 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 2041 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 1796 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 579 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 415 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 1169 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 986 ms | — |
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 (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 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-04 01:022026-09-04 01:02 UTC | settled (amount + payee) | 200 | 0xa27d2b25…207f | 4072 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose 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/42ab4000-2e56-42a1-9646-4940cd4f4877)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.