aurelius-node-01.onrender.com/api/v1/supply
1.Catalog declaration
| Resource URL | https://aurelius-node-01.onrender.com/api/v1/supply |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x239de97929b20f27aa503b236d33420670bf5ad1 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC |
| Catalog-reported calls / payers (30d) | 7 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-04 17:40 UTC | GET | pass | 402 | 253 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 432 ms | — |
| 2026-09-03 23:40 UTC | GET | pass | 402 | 375 ms | — |
| 2026-09-03 14:40 UTC | GET | pass | 402 | 400 ms | — |
| 2026-09-02 23:40 UTC | GET | pass | 402 | 521 ms | — |
| 2026-09-02 14:40 UTC | GET | pass | 402 | 844 ms | — |
| 2026-08-24 11:11 UTC | GET | pass | 402 | 128 ms | — |
3.L1 — real purchases
0 of 2 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 4xx or 5xx counts as settled and not as delivered — definitions.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 08-31 12:082026-08-31 12:08 UTC | delivered_no_receipt | 200 | — | 1026 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatch | ||||
| 08-24 23:342026-08-24 23:34 UTC | delivered_no_receipt | 200 | — | 1392 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatch | ||||
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.