# Cryptyx Signal Evaluation Engine

> Cryptyx Signal Evaluation Engine 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).

Evaluates one or all trading signals for a given day, returning triggered count, total assets considered, and per-asset breakdown with optional dryrun mode.

## Facts

- Endpoint: GET https://www.cryptyx.ai/api/signals/eval
- 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-evaluation-engine-7529a534
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aprnhcj4lfJzTmDICXRfh

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-evaluation-engine-7529a534
```

Example prompt: Run the signal eval for April 25, 2026 on signal TR_MOMO_CONT_14D in dryrun mode so I can see how many assets triggered and get the per-asset breakdown without writing to the signal log.

## When to prefer this

Use this endpoint when you need to audit or recompute signal evaluations for a specific historical day, smoke test the evaluation pipeline, or inspect how many and which assets triggered a given signal without side effects via dryrun mode. Prefer over live signal endpoints when the goal is retrospective verification or pipeline validation.

## Known failure modes

- Invalid date format (not YYYY-MM-DD) returns 400 error
- Unknown signal_id returns empty or error response
- Missing required day parameter may return default or error
- Payment not processed results in 402 response
- Future date with no data may return zero results or error

## How this service works

CRYPTYX | institutional-grade crypto intelligence: 150+ signals, 440+ metrics, 200+ assets. | Pipeline primitive that re-runs the database-side signal evaluator for a single YYYY-MM-DD day. Pass signal_id+dryrun=true → returns wouldTrigger row count from signals.signal_dryrun_count (no writes). Pass signal_id alone → executes signal_eval_day, returns insertedRows written to signal_log. Omit signal_id → executes signal_eval_all_for_day across enabled signals, returns results[] of {signal_id, inserted_rows} plus durationMs. Row counts only — no per-asset, IC, regime, or grade. Use as smoke-test or to recompute a missed eval day.

## Output

Returns a JSON object with the evaluated date, signal_id, total number of assets considered (~200), triggered count, and per-asset breakdown of signal firings. In dryrun mode, no signal_log writes occur.

## 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": [
      "day"
     ],
     "properties": {
      "day": {
       "type": "string",
       "description": "Anchor day in YYYY-MM-DD format. Required."
      },
      "dryrun": {
       "type": "string",
       "description": "Optional 'true' or 'false' (default 'false'). When 'true' AND signal_id is provided, counts would-trigger rows via signal_dryrun_count without writing to signal_log. Ignored when signal_id is omitted."
      },
      "signal_id": {
       "type": "string",
       "description": "Optional signal identifier (uppercased server-side, e.g. TR_MOMO_CONT_14D). If omitted, evaluates ALL enabled signals via signal_eval_all_for_day."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "application/json",
 "example": {
  "day": "2026-04-25",
  "signal_id": "TR_MOMO_CONT_14D",
  "total_assets": 200,
  "triggered_count": 8
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cryptyx-signal-evaluation-engine-7529a534/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)