# CRYPTYX Signal Explain

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

Retrieves a detailed explanation of whether a specific crypto trading signal triggered for a given asset on a given date, including confidence score and contributing factors.

## Facts

- Endpoint: GET https://cryptyx.ai/api/signals/explain
- Price: $0.01/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-explain-56d66a05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RLXfTxoSvf9pSO9OgnW4Y

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-explain-56d66a05
```

Example prompt: Can you check CRYPTYX and tell me whether the TR_MOMO_CONT_14D momentum signal triggered for BTC on 2026-04-25, and what the confidence score and contributing factors were?

## When to prefer this

Use this endpoint when you need to understand the reasoning and confidence behind a specific named signal for a specific crypto asset on a specific date — not for scanning all signals or streaming live data. Ideal for post-hoc analysis, agent decision-making based on signal state, or building explainability layers on top of crypto trading logic.

## Known failure modes

- Unknown signal_id returns 404 or empty result
- Invalid asset symbol returns validation error
- Future or unavailable date returns no data
- Missing required signal_id field returns 400 bad request
- Payment failure via x402 returns 402 Payment Required

## How this service works

Factor t-score breakdown for one (asset, day) — per-class scores across the 8 factor classes plus the weighted composite. Inspect which factor classes drove the call. Coverage: pass any asset in the CRYPTYX 200+ tracked universe (BTC, ETH, SOL, top-cap + long-tail).

## Output

Returns whether the specified signal was triggered (boolean), a confidence score (0-1), the date and asset it applies to, and a breakdown of contributing factor values (e.g. TR: 1.24) that explain why the signal fired or did not.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "signal_id"
 ],
 "properties": {
  "day": {
   "type": "string",
   "description": "Date (YYYY-MM-DD)"
  },
  "asset": {
   "type": "string",
   "description": "Asset symbol (e.g. BTC, ETH, SOL)"
  },
  "signal_id": {
   "type": "string",
   "description": "Signal registry ID"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "day": "2026-04-25",
 "asset": "BTC",
 "factors": {
  "TR": 1.24
 },
 "signal_id": "TR_MOMO_CONT_14D",
 "triggered": true,
 "confidence": 0.73
}
```

## More

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