Signals Fork
by CRYPTYX in Onchain & crypto
Fork a signal into an inactive parameter variant — production firing is untouched. Experimentation primitive: fork, dryrun-backtest, then activate. Returns the new version id and parameters. Runs across 200+ digital assets — BTC, ETH, SOL, top-cap + long-tail coverage.
https://cryptyx.ai/api/signals/fork- Price
- $0.05
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 267 ms
- 470 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://cryptyx.ai/api/signals/fork
Each call costs $0.05 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://cryptyx.ai/api/signals/fork
content-type: application/json
{
"params": {},
"signal_id": ""
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
params | object | Yes | Non-empty JSONB parameter object stored as the new inactive version. Keys are not validated against the signal's param schema — agent must supply the correct keys (e.g., t_thr, dt_max, vol_thr) for the target signal's geometry. |
signal_id | string | Yes | Registered signal_id in signals.signal_registry. Uppercased before lookup (e.g., TR_MOMO_CONT_14D, VOL_COMPRESSION_7v30, FUT_FUNDING_STRESS). |
Example response
The provider's example. We can't check it without paying.
{
"created_at": "2026-06-19T04:12:38.421Z",
"is_active": false,
"ok": true,
"params": {
"dt_max": -0.08,
"t_thr": 0.55
},
"signal_id": "TR_MOMO_CONT_14D",
"version": 188
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.05.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://cryptyx.ai/api/signals/fork' \
-H 'content-type: application/json' \
--data-raw '{"params":{},"signal_id":""}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://cryptyx.ai/api/signals/fork' \
-H 'content-type: application/json' \
--data-raw '{"params":{},"signal_id":""}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcryptyx.ai%2Fapi%2Fsignals%2Ffork&method=POST
const res = await pay("https://cryptyx.ai/api/signals/fork", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"params": {},
"signal_id": ""
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://cryptyx.ai/api/signals/fork",
json={
"params": {},
"signal_id": "",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 410 ms | $0.05 |
| 6 h ago | Passed | 402 | 254 ms | $0.05 |
| 11 h ago | Passed | 402 | 356 ms | $0.05 |
| 15 h ago | Passed | 402 | 320 ms | $0.05 |
| 19 h ago | Passed | 402 | 334 ms | $0.05 |
Show 10 older checks
| 23 h ago | Passed | 402 | 266 ms | $0.05 |
| 27 h ago | Passed | 402 | 180 ms | $0.05 |
| 31 h ago | Passed | 402 | 280 ms | $0.05 |
| 35 h ago | Passed | 402 | 227 ms | $0.05 |
| 39 h ago | Passed | 402 | 276 ms | $0.05 |
| 43 h ago | Passed | 402 | 275 ms | $0.05 |
| 47 h ago | Passed | 402 | 307 ms | $0.05 |
| 2 days ago | Passed | 402 | 308 ms | $0.05 |
| 2 days ago | Passed | 402 | 267 ms | $0.05 |
| 2 days ago | Passed | 402 | 217 ms | $0.05 |