# CRYPTYX Signal Events Time Series

> CRYPTYX Signal Events Time Series is a paid API for AI agents from www.cryptyx.ai, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-11).

Returns a time series of signal firing events for a single crypto asset over the last N days, including signal ID, date, trigger status, and confidence.

## Facts

- Endpoint: GET https://www.cryptyx.ai/api/asset/signal-events?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cryptyx-signal-events-time-series-f44af0b9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iisKmiiXtox4xuiDZhks1

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-events-time-series-f44af0b9
```

Example prompt: Show me the CRYPTYX signal firing history for BTC over the last 30 days — I want to see which signals triggered and their confidence scores so I can backtest when VOL_COMPRESSION last fired.

## When to prefer this

Use this endpoint when you need a day-by-day audit trail of when a specific signal fired on a named asset — ideal for signal-level backtesting, 'when did X last trigger' lookups, or building a historical signal log. Prefer it over the recent-signals stream when you need asset-scoped history rather than a cross-asset event feed.

## Known failure modes

- Missing required 'symbol' query parameter returns a 400-level error
- Unknown or unsupported asset symbol returns an empty events array or 404
- Invalid 'days' value (e.g. negative or non-numeric) causes a validation error
- Payment not completed or insufficient USDC balance returns a 402 Payment Required
- Service unavailable or upstream data gap returns a 503 or partial result

## How this service works

CRYPTYX | institutional-grade crypto intelligence: 150+ signals, 440+ metrics, 200+ assets. | Per-asset triggered signal ledger over last N days (7-365, default 90), filtered to grade A/B non-anti-predictive signals only. Returns ok, symbol, days, events[] with asof_day, signal_id, name, class (one of 8: CORR/EFF/FLOW/FUT/OB/OPT/TR/VOL), direction (long/short/neutral derived from registry tags + z sign), z, confidence, horizon, grade, close_px for chart overlay, fwd_return_7d realized outcome, plus meta.ic_context=cross_sectional. Use for "when did X last fire on SOL and what happened next" backtests across ~200 assets and 143 atomic signals.

## Output

A JSON array of signal event objects for the requested asset, each containing the date (day), signal identifier (signal_id), a boolean triggered flag, and a confidence score, covering the requested lookback window.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "symbol"
     ],
     "properties": {
      "days": {
       "type": "number",
       "description": "Lookback window in days, 7-365, default 90."
      },
      "symbol": {
       "type": "string",
       "description": "Asset ticker (uppercased, trimmed). Required."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "application/json",
 "example": {
  "events": [
   {
    "day": "2026-04-25",
    "signal_id": "VOL_COMPRESSION_7v30",
    "triggered": true
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cryptyx-signal-events-time-series-f44af0b9/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)