agent-commerce-factory-jm.austriaeast.cloudapp.azure.com/v1/crypto/token-price
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://agent-commerce-factory-jm.austriaeast.cloudapp.azure.com/v1/crypto/token-price |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0xce339395d7f2ea5a5009022ef1c392fb208a989e |
| Declared price (base units) | 6000 |
| Catalog status | delisted (since 2026-10-11 13:03 UTC) |
| First seen / last seen | 2026-08-26 01:39 UTC / 2026-10-11 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-11 12:40 UTC | POST | fail | — | 188 ms | dnsThe host name did not resolve. |
| 2026-10-10 12:40 UTC | POST | fail | 502 | 324 ms | no_402HTTP 502 instead of 402 to an unpaid POST. |
| 2026-10-09 12:40 UTC | POST | pass | 402 | 228 ms | — |
| 2026-10-08 04:40 UTC | POST | pass | 402 | 209 ms | — |
| 2026-10-06 04:41 UTC | POST | pass | 402 | 459 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 630 ms | — |
| 2026-10-03 22:40 UTC | POST | pass | 402 | 759 ms | — |
| 2026-10-03 04:40 UTC | POST | pass | 402 | 646 ms | — |
| 2026-10-02 13:40 UTC | POST | pass | 402 | 479 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 561 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 363 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 815 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 1600 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 628 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 333 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 457 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 393 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 314 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 418 ms | — |
| 2026-09-22 11:25 UTC | POST | pass | 402 | 364 ms | — |
| 2026-09-19 11:24 UTC | POST | pass | 402 | 319 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 134 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 108 ms | — |
| 2026-09-09 11:24 UTC | POST | pass | 402 | 233 ms | — |
| 2026-09-04 11:24 UTC | POST | pass | 402 | 133 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 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
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 00:002026-09-25 00:00 UTC | settled (nonce-bound) | 200 | 0x37b716e4…bdf9 | Base | 1767 ms |
| 6000 units (≈ $0.006 USDC) · L2 matchWhose 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/872e28e2-0a5a-4144-9727-174b849246c6)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-11 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-10-08 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-06 | 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.