# CRYPTYX Metric Slicer — Digital Asset Signal Threshold Analyzer

> CRYPTYX Metric Slicer — Digital Asset Signal Threshold Analyzer is a paid API for AI agents from cryptyx.ai, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Evaluates a specific crypto metric against a Z-score threshold using a comparison operator and returns historical hit rate, trigger count, and mean forward return for the given asset

## Facts

- Endpoint: POST https://cryptyx.ai/api/metrics/slicer
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cryptyx-metric-slicer-digital-asset-signal-threshold-analyzer-b67b2756
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bnPk4_HAlSt0xLn1k9oPE

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-metric-slicer-digital-asset-signal-threshold-analyzer-b67b2756 -d '<json body>'
```

Example prompt: On CRYPTYX, check how often BTC's metric 'onchain_netflow_zscore' has triggered when its Z-score is greater than 2.0, and tell me the historical hit rate and mean forward return.

## When to prefer this

Use this endpoint when you need to quantitatively evaluate how predictive a specific crypto metric is at a given Z-score threshold for a particular asset — especially for backtesting signal conditions, filtering noisy indicators, or measuring forward return after a threshold trigger. Prefer this over general price-data APIs when you need metric-level intelligence with statistical hit-rate validation.

## Known failure modes

- Unknown metric_id returns an error or empty result
- Invalid operator string (not one of gt/lt/gte/lte/abs_gt) causes a validation error
- Asset symbol not supported returns empty by_asset array
- Threshold out of meaningful Z-score range may return zero triggers
- Payment failure via x402 protocol blocks the call with a 402 response

## How this service works

Single-metric z-score backtest over 5+ years of history per asset. Triggers, trigger rate, and per-horizon forward-return and max-drawdown stats across 8 horizons (1d-365d). Pre-composite single-factor edge testing. Coverage: pass any asset in the CRYPTYX 200+ tracked universe (BTC, ETH, SOL, top-cap + long-tail).

## Output

Returns a JSON object with per-asset hit rates (array of asset/hit_rate pairs), the overall hit rate across all assets, the total number of historical triggers (n_triggers), and the mean forward return following those triggers — giving a quantitative read on signal predictiveness.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "asset",
  "operator",
  "metric_id",
  "threshold"
 ],
 "properties": {
  "asset": {
   "type": "string",
   "description": "Asset symbol"
  },
  "operator": {
   "type": "string",
   "description": "gt/lt/gte/lte/abs_gt"
  },
  "metric_id": {
   "type": "string",
   "description": "Metric ID"
  },
  "threshold": {
   "type": "number",
   "description": "Z-score threshold"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "by_asset": [
  {
   "asset": "BTC",
   "hit_rate": 0.62
  }
 ],
 "hit_rate": 0.58,
 "n_triggers": 156,
 "mean_fwd_return": 0.034
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cryptyx-metric-slicer-digital-asset-signal-threshold-analyzer-b67b2756/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)