passlisted in Coinbase#24 by calls of 63 on this host
0.05 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 00:08 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.05 USDC
- Networks
- 1
How has the volume on this endpoint moved?
signals fork is one of 63 listed endpoints on cryptyx.ai, tied 24th by calls with 39 others among them.
Callers of signals fork supply a json body with the fields params and signal_id.
signals fork returns json; the example shows ok, params, version, is_active, signal_id and created_at.
signals fork drew a single call from a single payer in the trailing 30 days.
The last call to signals fork came 10 days before the snapshot, 2026-10-04.
signals fork is priced at 0.05 USDC on Base.
TOLL files signals fork under market data: a POST endpoint on cryptyx.ai, listed in the Coinbase registry.
signals fork answered the sweep of 2026-10-23 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to signals fork within market data: analyze at svm402.com and q verdict resource at www.ax1.vc.
signals fork is priced above 86% of comparable listings in market data.
The wallet paid by signals fork is the payee of 66 endpoints across 2 hosts.
The seller's tags on signals fork are crypto, trading, signals and intelligence.
581 other listings in market data declare exactly the same price.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.05 USDC | exact | 0x0cD2c9…5c394f |
the checks, as of 2026-10-23 08:41 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-23 08:41 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 11:14 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 10:50 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 08:25 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 10:25 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 20:41 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 06:36 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 08:21 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 06:27 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 11:09 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 08:31 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 07:15 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 15:18 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 07:52 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 09:21 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 08:40 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 09:33 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 08:34 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 10:57 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 05:47 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 15:00 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 07:54 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:13 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:30 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 06:17 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 21:01 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 06:37 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 06:48 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 07:10 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 05:12 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 12:27 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 05:07 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 05:07 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 05:23 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:58 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:55 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:11 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:51 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 00:08 UTC · method · live
The input and output block
{
"input": {
"body": {
"params": {},
"signal_id": ""
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true,
"params": {
"t_thr": 0.55,
"dt_max": -0.08
},
"version": 188,
"is_active": false,
"signal_id": "TR_MOMO_CONT_14D",
"created_at": "2026-06-19T04:12:38.421Z"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "signals fork on cryptyx.ai", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/cryptyx-ai-api-signals-fork-6a9604/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-cryptyx-ai-api-signals-fork-6a9604-2026-10-13T14-08Z,
author = {TOLL},
title = {signals fork on cryptyx.ai},
howpublished = {\url{https://tollindex.com/e/cryptyx-ai-api-signals-fork-6a9604/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.