api.agentstools.dev/govcon/awards
1.Catalog declaration
| Resource URL | https://api.agentstools.dev/govcon/awards |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xf22e558a00d91ee12a1f50c52186fecb8ddff493 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-18 01:06 UTC / 2026-10-17 13:04 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-14 21:40 UTC | GET | pass | 402 | 470 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 462 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 531 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 491 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 665 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 535 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 766 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 562 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 253 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 568 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 766 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 653 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 580 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 470 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 660 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 663 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 420 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 765 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 480 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 564 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 553 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 430 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 435 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 131 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 181 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 130 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 317 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 259 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 201 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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.
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-16 00:012026-09-16 00:01 UTC | settled (nonce-bound) | 200 | 0x531c9743…b178 | 7932 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 01:002026-09-02 01:00 UTC | settled (amount + payee) | 200 | 0x6bec01a8…3cea | 2983 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 2/2 settled · 2 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/081482ef-ba54-4684-b1bc-2b508826c7cd)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-28 | relisted | {"status":"delisted"} | {"status":"active"} |
| 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.