Query Hyperliquid data in your language

Sync and async clients over httpx, with typed response models. The base install carries only the transport; the extras pull in the engine you actually want, and a missing one raises with the exact install line.

pip install "tessera-api[polars]"

export TESSERA_API_KEY="sk_..."

import tessera

client = tessera.TesseraClient()   # reads $TESSERA_API_KEY

df = client.read("gold_ohlcv_1m", "BTC", "2026-05")
print(df.select("time", "close", "cvd").tail())

rel = client.to_duckdb("gold_ohlcv_1m", ["BTC", "ETH"], "2026-05")

rel.filter("close > open").aggregate(
    "coin, avg(cvd) AS mean_cvd, count(*) AS n", "coin"
).show()

lf = client.scan(
    "gold_ohlcv_1m",
    coin=["BTC", "ETH"],
    month=tessera.MonthSpan("2026-01", "2026-05"),
    columns=["time", "close", "aggressor_delta"],
)

lf.filter(pl.col("cvd") > 0).collect()

async with tessera.AsyncTesseraClient() as client:
    df = await client.read("gold_ohlcv_1m", ["BTC", "ETH"], "2026-05")

The crate is published as tessera-api but imports as tessera. Polars is the default feature; DuckDB is opt-in, and turning it on is what swaps the engine, so Cargo.toml has to say which one you want. Needs Rust 1.85+.

cargo add tessera-api

tessera-api = { version = "0.1", default-features = false, features = ["duckdb"] }

use tessera::TesseraClient;

fn main() -> Result<(), tessera::TesseraError> {
    let client = TesseraClient::new(None)?;   // reads $TESSERA_API_KEY

    let df = client.read("gold_ohlcv_1m", "BTC", "2026-05", None)?;
    println!("{} rows", df.height());
    Ok(())
}

AsyncTesseraClient is the async mirror, for use inside a Tokio runtime — the sync client builds its own runtime for the Polars cloud reads, so it must not be constructed from one.

The same six calls, in both clients

Neither client has per-dataset methods. Everything is addressed by the same (asset, coin, month, columns) tuple, which is why the API surface stays small as datasets are added — call datasets() to discover the names.

When a span covers more than one partition, both clients append coin and month columns so every row stays attributable. Presigned URLs are short-lived (~15 minutes) — collect a lazy frame promptly, or you will get a presign-expired error rather than stale data.

What your key decides

The client does not hold entitlements; the API applies your plan to every request and filters what comes back. A span that reaches outside your slice is an error, not a silent truncation.