cryptyx.ai/api/ai/signals
1.Catalog declaration
| Resource URL | https://cryptyx.ai/api/ai/signals |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0cd2c9724f185a029101b4aeacf3f114415c394f |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 16:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 629 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 404 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 2133 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 546 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 350 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 127 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 322 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 644 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 212 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 1928 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 317 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 334 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 1760 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 0 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-11 18:022026-09-11 18:02 UTC | settled (nonce-bound)tx from our index | — | 0x95e38b6b…1a01 | 20336 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-04 12:082026-09-04 12:08 UTC | settled (nonce-bound)tx from our index | — | 0x2fd76f80…fb3d | 20178 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 0 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/5c2ec0f7-ac0a-46ee-a12c-75560f466e9f)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.