# APEX Runner: Regime Micro Signal

> APEX Runner: Regime Micro Signal is a paid API for AI agents from apexrunner.ai, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-16).

Returns a micro-level market regime signal indicating current trading conditions and regime state for algorithmic decision-making.

## Facts

- Endpoint: GET https://apexrunner.ai/signals/regime-micro
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apex-runner-regime-micro-signal-afe383fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PhSINEoi5880tf_p3YL9K

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 apex-runner-regime-micro-signal-afe383fb
```

Example prompt: Pull the APEX Runner regime micro signal right now — I want to know the current market regime classification, whether it's live-trading backed, and how many trades are supporting the signal.

## When to prefer this

Use this endpoint when you need a real-time micro-level regime classification signal specifically from APEX Runner's live-trading-backed model. Prefer this over macro regime signals when you need granular, short-horizon regime context. The signal is backed by live capital deployment and actual trades, making it more actionable than purely theoretical models. Choose this when integrating regime awareness into a live algorithmic trading system that requires verified, hashed signals for auditability.

## Known failure modes

- Payment not included or insufficient — 402 Payment Required response
- Endpoint unreachable — 503 or timeout
- Invalid or expired x402 payment token — authentication failure
- No signal available for current session — empty or null signal fields
- Rate limit exceeded — 429 Too Many Requests

## How this service works

APEX Runner: Regime Micro Signal

## Output

Returns a compact regime signal object with fields: 'a' (asset), 'b' (bias or bucket), 'e' (entry condition or environment), 's' (signal label), 't' (timestamp integer), plus a nested '_apex' metadata object containing the signal string, source, version, instance ID, verify_at timestamp, signal_hash for integrity, a live_trading boolean, evolution_runs count, live_capital_deployed boolean, and trades_backing_signal count.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "a": "string — AVAX regime",
 "b": "string — BTC regime",
 "e": "string — ETH regime",
 "s": "string — SOL regime",
 "t": "integer — unix timestamp",
 "type": "json",
 "example": {
  "a": "RANGING",
  "b": "RANGING",
  "e": "TRENDING",
  "s": "CHOPPY",
  "t": 1750000000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apex-runner-regime-micro-signal-afe383fb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apexrunner.ai](https://www.zero.xyz/host/apexrunner.ai/llms.txt)