Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-02 · 1 day ago

www.getbags.app/api/agent/link/pl-90ce47d5-ccb1-48c3-8388-379b07517b5c

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://www.getbags.app/api/agent/link/pl-90ce47d5-ccb1-48c3-8388-379b07517b5c
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x25955c4a690e13f8a5de0ce3fda34163f01f88e8
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-08-152026-10-02
Figure 1. Probe timeline, last 9 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-02 13:40 UTCPOSTpass4022250 ms—
2026-10-01 16:40 UTCPOSTpass402486 ms—
2026-09-30 22:40 UTCPOSTpass402560 ms—
2026-09-30 04:40 UTCPOSTpass4021953 ms—
2026-09-29 10:31 UTCPOSTpass4021884 ms—
2026-09-24 10:30 UTCPOSTpass402788 ms—
2026-09-20 11:24 UTCPOSTpass4022018 ms—
2026-09-17 12:35 UTCPOSTpass4021374 ms—
2026-08-15 10:42 UTCPOSTfail4021637 msaccepts_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 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).
1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txLatency
10-01 00:02settled (nonce-bound)2000x5055f378…17979146 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.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (www.getbags.app · measured 2026-10-01)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/f3145d3a-a4ab-412f-87b9-cc695cc1993c.svg)](https://vet402.com/observatory/e/f3145d3a-a4ab-412f-87b9-cc695cc1993c)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-17relisted{"status":"delisted"}{"status":"active"}
2026-09-02delisted{"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.

20–2,000 characters · 0 so far