# APEX Runner Live Fill Rate Signal

> APEX Runner Live Fill Rate 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-13).

Returns a real-time fill rate signal for crypto trading, indicating how effectively orders are being filled in current market conditions.

## Facts

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

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-live-fill-rate-signal-d7574d9a
```

Example prompt: Pull the live fill rate signal from APEX Runner right now — I want to see how efficiently orders are getting filled in the current market before my grid strategy places its next batch.

## When to prefer this

Use this endpoint when you need a real-time, point-in-time fill rate signal to inform crypto trading decisions, particularly for grid trading or AI-driven strategies on Kraken, Coinbase, or Hyperliquid. Prefer this over generic order book data when you want a pre-computed, actionable signal rather than raw market data.

## Known failure modes

- Market data unavailable — signal feed offline or exchange connectivity issue
- Payment not accepted — x402 USDC payment of $3 not processed
- Rate limit exceeded — too many signal requests in a short period
- Invalid authentication or payment header — returns 402 or 401 error

## How this service works

APEX Runner: Live Fill Rate Signal

## Output

A real-time fill rate signal indicating the current rate at which crypto orders are being filled in the market, useful for gauging execution quality and liquidity conditions for algorithmic trading decisions.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "velocity": "HIGH",
  "fills_last_hour": {
   "kraken": {
    "count": 4
   },
   "coinbase": {
    "count": 6
   },
   "hyperliquid": {
    "count": 12
   }
  },
  "most_active_pair": "BTC",
  "total_fills_hour": 22
 },
 "velocity": "string — HIGH (>=20 fills/hr) / MODERATE (>=8) / LOW (>=2) / IDLE",
 "fills_last_hour": "object — keyed by exchange (kraken/coinbase/hyperliquid), each with count, pairs array, avg_pnl",
 "most_active_pair": "string — pair with most fills across all exchanges",
 "total_fills_hour": "integer — total grid fills across all exchanges in last 60 minutes",
 "market_interpretation": "string — plain-English grid activity summary"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apex-runner-live-fill-rate-signal-d7574d9a/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)