# CRYPTYX Signal Fork

> CRYPTYX Signal Fork is a paid API for AI agents from cryptyx.ai, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-16).

Forks an existing trading signal with new parameter values, creating a customized variant of a digital asset intelligence signal

## Facts

- Endpoint: POST https://cryptyx.ai/api/signals/fork
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cryptyx-signal-fork-cf2a25d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__z-Tr3_e7Xg_RdyLtjlwN

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability cryptyx-signal-fork-cf2a25d4 -d '<json body>'
```

Example prompt: On CRYPTYX, fork my 14-day momentum continuation signal TR_MOMO_CONT_14D and set the trend threshold to 0.75 and the max drawdown to -0.03.

## When to prefer this

Use this endpoint when you want to experiment with variations of an existing CRYPTYX signal without modifying the original — ideal for backtesting different threshold configurations, creating personalized signal variants, or branching off a shared signal for individual tuning.

## Known failure modes

- signal_id not found — returns 404 if the referenced signal does not exist
- invalid params schema — returns 400 if parameter keys do not match the signal's expected schema
- payment failure — returns 402 if x402 payment of $0.05 USDC is not provided or invalid
- unauthorized — returns 401 if credentials are missing or expired
- conflict — returns 409 if a fork with identical parameters already exists

## How this service works

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.

## Output

Returns a new forked signal object including the generated forked_signal_id (e.g. TR_MOMO_CONT_14D), a version number, the active status of the new fork (initially false), and the parameter values used to create it (e.g. t_thr, dt_max).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "params",
  "signal_id"
 ],
 "properties": {
  "params": {
   "type": "object",
   "description": "New parameter values"
  },
  "signal_id": {
   "type": "string",
   "description": "Signal to fork"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "params": {
  "t_thr": 0.6,
  "dt_max": -0.05
 },
 "version": 42,
 "is_active": false,
 "forked_signal_id": "TR_MOMO_CONT_14D"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cryptyx-signal-fork-cf2a25d4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cryptyx.ai](https://www.zero.xyz/host/cryptyx.ai/llms.txt)