agentforge-production-0893.up.railway.app/v1/discover/memory
1.Catalog declaration
| Resource URL | https://agentforge-production-0893.up.railway.app/v1/discover/memory |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x56cfdcc1ab02e027a11ebced1b884351ea6467ca |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-10-07 13:03 UTC) |
| First seen / last seen | 2026-09-06 01:03 UTC / 2026-10-07 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-06 22:40 UTC | POST | fail | 404 | 414 ms | no_402HTTP 404 instead of 402 to an unpaid POST. |
| 2026-10-06 04:41 UTC | POST | pass | 402 | 153 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 140 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 223 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 140 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 86 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 115 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 256 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 65 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 139 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 378 ms | — |
| 2026-09-24 10:30 UTC | POST | pass | 402 | 148 ms | — |
| 2026-09-20 11:24 UTC | POST | pass | 402 | 60 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 122 ms | — |
| 2026-09-13 11:24 UTC | POST | pass | 402 | 86 ms | — |
| 2026-09-10 11:24 UTC | POST | pass | 402 | 90 ms | — |
| 2026-09-06 11:24 UTC | POST | pass | 402 | 69 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 match (no required keys)- the declaration vet402 used marks no key as required, so vet402 checked that the response parsed as a JSON object or array, not which keys it carries.
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
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-25 12:012026-09-25 12:01 UTC | settled (nonce-bound) | 200 | 0xd62d2b12…e611 | Base | 813 ms |
| 1000 units (≈ $0.001 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: 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/ff5d05b9-494c-4ac2-bebd-9a28607809f5)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-07 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | 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.