api.postulated.store/tenders
1.Catalog declaration
| Resource URL | https://api.postulated.store/tenders |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x15c26c5a7476eb3114c95d3f93c6d48c26b9c5ff |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-10-29 13:04 UTC / 2026-11-12 18:05 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-12 13:40 UTC | GET | pass | 402 | 647 ms | — |
| 2026-11-10 04:41 UTC | GET | pass | 402 | 411 ms | — |
| 2026-11-08 04:40 UTC | GET | pass | 402 | 404 ms | — |
| 2026-11-05 22:40 UTC | GET | pass | 402 | 521 ms | — |
| 2026-11-02 22:46 UTC | GET | pass | 402 | 743 ms | — |
| 2026-10-31 16:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-10-29 22:40 UTC | GET | pass | 402 | 565 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-30 00:012026-10-30 00:01 UTC | settled (nonce-bound) | 200 | 0x936137cb…acbd | Base | 6018 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose 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/f170b8f1-7223-48f5-8b33-3650508310da)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-30 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.
About the purchase at 2026-10-30T00:01:53Z (UTC). The form starts with that time; add what you saw instead.