# CRYPTYX Signal Simulate

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

Simulates a crypto trading signal against historical data to estimate how often it would have triggered across digital assets

## Facts

- Endpoint: POST https://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-simulate-887ec60e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_q7Cw6jE74I7XAOYqDSUz-

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-simulate-887ec60e -d '<json body>'
```

Example prompt: Run a simulation on CRYPTYX signal 'rsi_oversold_extreme' with threshold_key set to 'rsi_period' and a threshold_value of 10, and tell me the estimated trigger rate and how it distributes across assets like BTC, ETH, and SOL.

## When to prefer this

Use this endpoint when you need to validate or tune a specific signal's threshold parameters before deploying it live — particularly when you want to understand historical trigger frequency across multiple crypto assets. Prefer this over live signal endpoints when the goal is backtesting or sensitivity analysis rather than real-time alerting.

## Known failure modes

- Unknown signal_id returns 404 or empty result
- Invalid threshold_value type causes 400 validation error
- Unrecognized threshold_key may return zero triggers with no error
- Payment failure via x402 returns 402 before simulation runs
- Signal with no historical data returns sample_triggers of 0 and trigger_rate of 0

## How this service works

Pre-flight threshold simulator — count how many assets would trigger at a proposed cutoff for one anchor day, with current vs proposed threshold and estimated trigger rate. Use before forking parameters. Runs across 200+ digital assets — BTC, ETH, SOL, top-cap + long-tail coverage.

## Output

Returns the number of sample triggers found in historical data (e.g. 12), a breakdown of which assets triggered the signal (e.g. BTC:3, ETH:2, SOL:2), and an overall estimated trigger rate as a decimal (e.g. 0.18 meaning 18% of periods).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "signal_id"
 ],
 "properties": {
  "signal_id": {
   "type": "string",
   "description": "Signal to simulate"
  },
  "threshold_key": {
   "type": "string",
   "description": "Parameter name"
  },
  "threshold_value": {
   "type": "number",
   "description": "Proposed value"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "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-simulate-887ec60e/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)