api-macro-br-production.up.railway.app/v1/resumo
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://api-macro-br-production.up.railway.app/v1/resumo |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x61195a8af1f72350d85790f6edfd5d11d1fa02db |
| Declared price (base units) | 20000 |
| Catalog status | delisted (since 2026-10-06 01:01 UTC) |
| First seen / last seen | 2026-09-02 01:03 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-05 22:40 UTC | GET | fail | 404 | 166 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-10-04 13:40 UTC | GET | fail | 404 | 184 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-10-03 16:40 UTC | GET | fail | 404 | 188 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-10-02 22:40 UTC | GET | fail | 404 | 178 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 504 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 448 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 684 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 860 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 595 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 446 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 183 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 353 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 626 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 867 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 265 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 112 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 89 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 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 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 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 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 “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-08 12:092026-09-08 12:09 UTC | settled (nonce-bound) | 200 | 0xfa5da2f7…221c | Base | 2394 ms |
| 20000 units (≈ $0.02 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/cb6a1d69-e851-4d26-a1bd-d55f00a6b4e8)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-05 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-04 | 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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. 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.