# Cryptyx Signal Fork

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

Forks an existing trading signal with new parameters into an inactive version, enabling safe experimentation without disrupting live signal firing.

## Facts

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

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-1cbc73f8 -d '<json body>'
```

Example prompt: Fork the TR_MOMO_CONT_14D signal with new parameters t_thr set to 0.6 and dt_max set to -0.05 so I can test those values without touching the live signal.

## When to prefer this

Use this endpoint when you want to safely test new signal parameter configurations — such as adjusted thresholds or decay rates — without affecting the currently active production signal. It is the correct primitive for agent-driven iterative optimization and A/B experimentation on signals tracked in the Cryptyx universe.

## Known failure modes

- Unknown signal_id returns 404 not found
- Invalid parameter schema returns 400 bad request
- Insufficient USDC balance returns 402 payment required
- Duplicate fork with identical parameters may still create a new version
- Service unavailable returns 503

## Output

Returns a JSON object containing the forked signal ID (forked_signal_id), the new version number (version), confirmation that the fork is inactive (is_active: false), and the full set of new parameter values applied to the fork.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "required": [
      "signal_id",
      "params"
     ],
     "properties": {
      "params": {
       "type": "object",
       "description": "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": {
       "type": "string",
       "description": "Registered signal_id in signals.signal_registry. Uppercased before lookup (e.g., TR_MOMO_CONT_14D, VOL_COMPRESSION_7v30, FUT_FUNDING_STRESS)."
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "application/json",
 "example": {
  "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-1cbc73f8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.cryptyx.ai](https://www.zero.xyz/host/www.cryptyx.ai/llms.txt)