# CRYPTYX Composite Metric Slicer

> CRYPTYX Composite Metric Slicer 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).

Evaluates a composite set of user-defined metric conditions on a digital asset and returns historical hit rate, trigger count, and mean forward return statistics

## Facts

- Endpoint: POST https://cryptyx.ai/api/metrics/slicer/composite
- 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-composite-metric-slicer-fbd4ce9b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O_v3i3Q3NTyBhYf_CnFPc

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-composite-metric-slicer-fbd4ce9b -d '<json body>'
```

Example prompt: On CRYPTYX, run a composite metric slicer on BTC using these two conditions: RSI below 30 and funding rate negative — what's the historical hit rate, number of triggers, and mean forward return?

## When to prefer this

Use this endpoint when you need to backtest or evaluate a multi-condition composite signal against a specific digital asset's historical data — particularly when you want to quantify how often a set of metric conditions co-occurs and what forward return typically follows. Prefer this over single-metric lookups when your strategy involves 2–4 simultaneous indicator thresholds.

## Known failure modes

- Asset symbol not recognized — returns 4xx with invalid asset error
- Fewer than 2 or more than 4 conditions supplied — validation error
- One or more condition metrics are unknown or malformed — returns schema validation error
- Payment not attached or insufficient — 402 Payment Required
- Insufficient historical data for the asset/condition combination — may return empty or low-confidence result

## How this service works

Multi-factor z-score confluence backtest for one asset (2-4 conditions). Intersects triggered days, returns per-metric series, composite triggers, and per-horizon forward-return/drawdown stats. Validate confluence stacks before live deployment. Coverage: pass any asset in the CRYPTYX 200+ tracked universe (BTC, ETH, SOL, top-cap + long-tail).

## Output

Returns a JSON object with hit_rate (fraction of time the composite conditions fired and were followed by a positive outcome), n_triggers (total number of times the condition set was satisfied historically), and mean_fwd_return (average forward return following a trigger event).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "asset",
  "conditions"
 ],
 "properties": {
  "asset": {
   "type": "string",
   "description": "Asset symbol"
  },
  "conditions": {
   "type": "array",
   "description": "2-4 metric conditions"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "hit_rate": 0.67,
 "n_triggers": 48,
 "mean_fwd_return": 0.052
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cryptyx-composite-metric-slicer-fbd4ce9b/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)