# ByKaranteli Execution Slippage History

> ByKaranteli Execution Slippage History is a paid API for AI agents from bykaranteli.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Returns hourly execution slippage ladder snapshots per symbol, showing what a given order size would actually cost against the live order book at each recorded hour.

## Facts

- Endpoint: GET https://bykaranteli.com/api/x402/slippage-history
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bykaranteli-execution-slippage-history-1874a9e3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dWBqNJCWprgGGYAKixef1

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 bykaranteli-execution-slippage-history-1874a9e3
```

Example prompt: Pull the execution slippage ladder history for BTCUSDT on Binance from January 1 to January 7, 2025, limit to 500 rows, so I can model market impact costs for large orders during that period.

## When to prefer this

Choose this endpoint when you need historical, time-series execution slippage data at hourly granularity to backtest market impact models, calibrate trading algorithms, or analyze how execution costs have evolved for specific crypto symbols and venues. It is the right choice over live order book snapshots when you need reproducible historical cost data rather than current conditions, and over generic OHLCV bars when you specifically need order-size-dependent execution cost curves rather than price data.

## Known failure modes

- Missing required 'symbol' parameter may return empty rows or an error
- Time window too large may be capped by the per-dataset row limit
- Unknown or unsupported symbol/exchange combination returns empty rows
- Invalid date format for 'from' or 'to' parameters causes a parse error
- Limit exceeding the dataset cap is silently clamped to the maximum allowed value

## How this service works

Track verified crypto futures signals with live win rate, profit factor, funding data, and liquidation maps. Deterministic, auditable, operator-first.

## Output

Returns a JSON object with an 'ok' flag, a 'rows' array of hourly slippage ladder records (each containing symbol, venue, order size buckets, and their corresponding execution cost estimates), a 'count' of returned rows, and a 'dataset' identifier string. Rows are filtered by symbol, exchange, currency, and time window as specified.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "rows": [],
  "count": 500,
  "dataset": "slippage-history"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bykaranteli-execution-slippage-history-1874a9e3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bykaranteli.com](https://www.zero.xyz/host/bykaranteli.com/llms.txt)