# CRYPTYX Signal Backtest

> CRYPTYX Signal Backtest 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).

Backtests a specific trading signal over a historical date range, returning daily trigger events, confidence scores, trigger rate, and total event count.

## Facts

- Endpoint: POST https://cryptyx.ai/api/signals/backtest
- 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-backtest-3c63c56e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P27_lWGtr_vaj_IpFoqAa

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-backtest-3c63c56e -d '<json body>'
```

Example prompt: Backtest the CRYPTYX signal TR_MOMO_CONT_14D from January 1, 2025 to December 31, 2025 and tell me how often it triggered, what the average confidence was, and which specific days it fired.

## When to prefer this

Use this endpoint when you need to historically evaluate a specific CRYPTYX signal's reliability, trigger frequency, and confidence before deploying it in a live strategy. Prefer this over live signal endpoints when you want to understand past behavior without affecting state, especially with dryrun=true for safe evaluation.

## Known failure modes

- Invalid signal_id returns an error or empty result set
- Missing required fields (to, from, signal_id) returns 400 validation error
- Date range too large may result in timeout or rate limit
- Invalid date format causes parsing error
- Payment failure (x402) blocks the call before processing

## How this service works

Backtest any signal over up to 365 days. Returns trigger stats, per-day rows, and a 4-horizon performance block (sample size, mean/median return, hit rate, bootstrap CI, statistical significance, reliability grade). Walk-forward OOS read inlined. Runs across 200+ digital assets — BTC, ETH, SOL, top-cap + long-tail coverage.

## Output

Returns a JSON object with the date range, the signal ID, total trigger events, an overall trigger rate (fraction of days the signal fired), average confidence score, and a day-by-day array indicating whether the signal triggered and its confidence level for each date.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "to",
  "from",
  "signal_id"
 ],
 "properties": {
  "to": {
   "type": "string",
   "description": "End date (YYYY-MM-DD)"
  },
  "from": {
   "type": "string",
   "description": "Start date (YYYY-MM-DD)"
  },
  "dryrun": {
   "type": "boolean",
   "description": "Evaluate without writing"
  },
  "signal_id": {
   "type": "string",
   "description": "Signal registry ID"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "to": "2025-12-31",
 "days": [
  {
   "day": "2025-06-15",
   "triggered": true,
   "confidence": 0.81
  }
 ],
 "from": "2025-01-01",
 "signal_id": "TR_MOMO_CONT_14D",
 "total_events": 42,
 "trigger_rate": 0.15,
 "avg_confidence": 0.73
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cryptyx-signal-backtest-3c63c56e/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)