Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today

micro-saas-agent.onrender.com/api/agent

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://micro-saas-agent.onrender.com/api/agent
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xb4527dccac81eb73d4988a51a4cb1fbbf2c3cabd
Declared price (base units)	20000
Catalog status	active
First seen / last seen	2026-08-28 01:12 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)	1 / 1

2.Probe history

2026-09-082026-10-20

Figure 1. Probe timeline, last 30 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 at	Method	Verdict	HTTP	Latency	Reason
2026-10-20 10:30 UTC	POST	pass	402	27 ms	—
2026-09-26 22:40 UTC	POST	pass	402	137 ms	—
2026-09-26 04:40 UTC	POST	pass	402	89 ms	—
2026-09-25 13:40 UTC	POST	pass	402	46 ms	—
2026-09-24 16:40 UTC	POST	pass	402	137 ms	—
2026-09-23 22:40 UTC	POST	pass	402	57 ms	—
2026-09-23 04:40 UTC	POST	pass	402	41 ms	—
2026-09-22 16:40 UTC	POST	pass	402	284 ms	—
2026-09-21 22:40 UTC	POST	pass	402	240 ms	—
2026-09-21 04:40 UTC	POST	pass	402	204 ms	—
2026-09-20 13:40 UTC	POST	pass	402	185 ms	—
2026-09-19 16:40 UTC	POST	pass	402	47 ms	—
2026-09-18 22:40 UTC	POST	pass	402	106 ms	—
2026-09-18 04:40 UTC	POST	pass	402	119 ms	—
2026-09-17 16:40 UTC	POST	pass	402	78 ms	—
2026-09-16 22:40 UTC	POST	pass	402	54 ms	—
2026-09-15 22:40 UTC	POST	pass	402	50 ms	—
2026-09-15 13:40 UTC	POST	pass	402	245 ms	—
2026-09-14 16:40 UTC	POST	pass	402	47 ms	—
2026-09-14 04:40 UTC	POST	pass	402	70 ms	—
2026-09-13 13:40 UTC	POST	pass	402	1589 ms	—
2026-09-12 22:40 UTC	POST	pass	402	174 ms	—
2026-09-12 13:40 UTC	POST	pass	402	256 ms	—
2026-09-11 16:40 UTC	POST	pass	402	102 ms	—
2026-09-11 04:40 UTC	POST	pass	402	51 ms	—
2026-09-10 17:40 UTC	POST	pass	402	204 ms	—
2026-09-09 23:40 UTC	POST	pass	402	133 ms	—
2026-09-09 14:40 UTC	POST	pass	402	82 ms	—
2026-09-08 23:40 UTC	POST	pass	402	99 ms	—
2026-09-08 14:40 UTC	POST	pass	402	61 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 (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's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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 at	Result	HTTP	On-chain tx	Latency
09-08 12:082026-09-08 12:08 UTC	settled (nonce-bound)	200	0x4d6b9a6f…c7b9	1241 ms
50000 units (≈ $0.05 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 receipt](https://vet402.com/api/badge/endpoint/2f914193-f851-435d-8a61-42407b7cf5e0.svg)](https://vet402.com/observatory/e/2f914193-f851-435d-8a61-42407b7cf5e0)

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
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.