# CRYPTYX Metric Slicer Scan

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

Scans all tracked digital assets for those exceeding a specified z-score threshold on a given metric, returning the statistical extremes

## Facts

- Endpoint: GET https://cryptyx.ai/api/metrics/slicer/scan
- 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-metric-slicer-scan-f359a91c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tNnrgrEiwDxZVaX6wyvFt

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-scan-f359a91c
```

Example prompt: Scan all digital assets on CRYPTYX and give me everything where the funding_rate metric is greater than a z-score of 2.0 — I want to see which coins are statistical outliers right now.

## When to prefer this

Use this endpoint when you need to screen the entire crypto asset universe for statistical outliers on a specific metric — ideal for quant screening, anomaly detection, and signal-driven alerting workflows where you want a ranked list of extremes rather than a point-in-time lookup for one asset.

## Known failure modes

- Invalid metric_id returns an error or empty results if metric is not tracked
- Invalid operator string (not one of gt/lt/gte/lte/abs_gt) causes a validation error
- Threshold too extreme returns empty extremes array with total_scanned still populated
- Network or service unavailability returns HTTP 5xx
- Insufficient payment (x402 protocol failure) blocks the request

## How this service works

Cross-sectional z-score scanner across 200+ assets and 440+ metrics. Pick a metric and threshold; get ranked triggering assets with z, percentile, returns, composite score, and per-metric health grading. Live anomaly hunting.

## Output

Returns an array of extreme assets with their z-score and percentile rank (e.g. {z: 2.1, pctl: 0.97, asset: 'BTC'}), plus the total number of assets scanned. Filtered to only those matching the operator and threshold conditions.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "extremes": [
  {
   "z": 2.1,
   "pctl": 0.97,
   "asset": "BTC"
  }
 ],
 "total_scanned": 200
}
```

## More

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