oracles-production.up.railway.app/v1/edgar-ma/status
1.Catalog declaration
| Resource URL | https://oracles-production.up.railway.app/v1/edgar-ma/status |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc66ee26cae6cd34970f51f644f36d720826d392a |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 5 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 22:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 281 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 331 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 175 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 141 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 277 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 1794 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 107 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 905 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 444 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 558 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 959 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 244 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 513 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 289 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 520 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 619 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 108 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 match- the response had the fields the listing's output schema declares.
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-17 15:272026-09-17 15:27 UTC | settled (nonce-bound) | 200 | 0xf93bb49e…2230 | 1409 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 12:092026-09-11 12:09 UTC | settled (nonce-bound) | 200 | 0x3b2a0ec7…e9b8 | 1227 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 12:092026-09-02 12:09 UTC | settled (amount + payee) | 200 | 0xea28780f…df5f | 1435 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/c59ad244-6a98-4d05-86b9-1d96cee97bef)4.Catalog listing events
No listing changes observed.
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.