# Cryptyx Signal Threshold Simulator

> Cryptyx Signal Threshold Simulator 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).

Simulates the effect of a proposed threshold parameter change on a signal, returning projected trigger rate, sample triggers, and per-asset distribution across 5+ years of historical data — without writing to the registry.

## Facts

- Endpoint: POST https://www.cryptyx.ai/api/signals/simulate
- 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-threshold-simulator-56912e08
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_muUZ0A88VRgcuN4YT6Yun

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-threshold-simulator-56912e08 -d '<json body>'
```

Example prompt: Before I save the change, simulate what happens to signal 'momentum_rsi_14' if I set the threshold_key 'min_zscore' to 0.18 — show me the projected trigger rate and how it distributes across assets.

## When to prefer this

Use this endpoint when you want to preview the impact of a threshold parameter change on a signal before committing it to the registry. It is the right choice for sizing parameter adjustments, comparing trigger aggressiveness across values, or validating that a proposed change behaves as expected — all without side effects. Prefer this over a live registry update or a full backtest endpoint when you need a fast, read-only estimate scoped to a single threshold change.

## Known failure modes

- Unknown signal_id returns a 404 or empty result
- Invalid threshold_key not recognized for the given signal returns an error
- threshold_value out of valid range causes a validation error
- Simulation times out on very broad signals with high trigger frequency
- Missing required fields (signal_id, threshold_key, threshold_value) returns a 400 bad request
- Payment not received or x402 handshake fails, blocking the call

## Output

Returns an estimated trigger rate (e.g. 0.18), the count of sample triggers (e.g. 12), and a per-asset trigger distribution (e.g. BTC: 3, ETH: 2, SOL: 2) computed against 5+ years of historical fact data — no registry state is modified.

## 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",
      "threshold_key",
      "threshold_value"
     ],
     "properties": {
      "asof_day": {
       "type": "string",
       "description": "Optional YYYY-MM-DD lookup day. Defaults to metrics.aligned_day_1d()"
      },
      "signal_id": {
       "type": "string",
       "description": "Atomic signal registry ID, uppercased server-side (e.g. TR_MOMO_CONT_14D, FLOW_ACCUM_NETUSD_7D, VOL_COMPRESSION_7v30)"
      },
      "threshold_key": {
       "type": "string",
       "description": "Parameter name to simulate (e.g. t_thr, z_thr). Used to fetch current_threshold from signals.signal_params for comparison"
      },
      "threshold_value": {
       "type": "number",
       "description": "Proposed cutoff value. Interpreted as z-score for most signals, t-score for TR_MOMO_* signals"
      }
     }
    },
    "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": {
  "sample_triggers": 12,
  "trigger_distribution": {
   "BTC": 3,
   "ETH": 2,
   "SOL": 2
  },
  "estimated_trigger_rate": 0.18
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cryptyx-signal-threshold-simulator-56912e08/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)