agent-budget-guard.onrender.com/api/budget/check
1.Catalog declaration
| Resource URL | https://agent-budget-guard.onrender.com/api/budget/check |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x60c402878efcecae5733a88075328aa2320c39be |
| Declared price (base units) | 30000 |
| Catalog status | delisted (since 2026-09-30 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 13:40 UTC | POST | pass | 402 | 469 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 469 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 254 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 331 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 292 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 337 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 395 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 189 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 312 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 260 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 130 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 339 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 182 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 567 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 146 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 139 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 566 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 183 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 286 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 146 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 2163 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 192 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 136 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 247 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 204 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 377 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 206 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 370 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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 |
|---|---|---|---|---|
| 08-31 12:092026-08-31 12:09 UTC | settled (amount + payee)tx from our index | 200 | 0x9516521f…8d76 | 2150 ms |
| 30000 units (≈ $0.03 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/234db026-a8d8-4d11-9938-d7199ae38bb1)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-30 | 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.