It has no name.
Your agent won't mind.

A quant data engine for futures traders and the machines they run. High-dimensional market vectors, served over one documented API. No signup. No password. No dashboard tour. A key — and the docs are the interface.

everything your agent needs
$ export KEY=the-one-thing-you-bought

$ curl api.example/v1/tracks -H "Authorization: Bearer $KEY"
{"tracks":[{"name":"MNQ_flow","dims":["cvd","pressure","imbalance", …512]}]}

$ curl "api.example/v1/tracks/MNQ_flow/range?from=…&to=…&dims=cvd,pressure"
{"samples":[{"t":"2026-08-28T09:30:00Z","vec":[184,-0.42]}, …]}▌
the whole onboarding

Toss your agent a key.

That sentence is the product. Agents can't fill signup forms, verify emails, or sit through dashboard tours — and lately, neither can you. Here the key is the account.

01

Buy a key

An opaque string. It carries your entitlements — data window, rate, tier. There is nothing else to it, on purpose.

02

Hand it to your agent

Human or machine, same door. Attach an email to the key if you want receipts; the key alone signs you in regardless.

Authorization: Bearer <key>

03

Point it at the docs

The API documents itself thoroughly enough that a cold agent can operate everything from the manual alone. That's tested, not hoped.

GET /docs → the entire interface

OAuth passwords email verification seats onboarding calls a JavaScript SDK you didn't ask for
what's inside

Futures microstructure, as vectors.

Dense, named-dimension time series built from live CME futures flow — the measurements quant work actually runs on, appended as the market prints and served by time range.

Order flow

Cumulative delta, aggressor imbalance, sweep depth, trade acceleration.

dims: cvd, delta_eff, sweep…

Book state

Bid/ask lean, distance-weighted pressure, microprice drift, spread regime.

dims: pressure, micro, spread…

Session structure

Value-area position, range posture, session character, killzone flags.

dims: va_pos, day_type, kz…

Levels & context

Prior day/week/month levels, gap state, volatility regime, news lockouts.

dims: pdh_dist, gap, rv, news…
window: trailing 30+ days, through last Friday's close · your key defines your reach · appended live, never revised
built for machines

Agent-first isn't a tagline here.

Every error, every shape, every limit is documented and uniform — one error contract an agent can branch on, one auth header, raw bytes only where raw bytes make sense. If the docs and the server ever disagree, that's a bug we fix on the server's side of the argument.

Underneath: a single self-contained binary with an embedded store. No database cluster, no queue, no third-party calls sitting between your agent and its data. Fewer moving parts is the reliability strategy.

the entire error contract
# every failure, every endpoint, one shape:
{"error":"track px already exists"}   409
{"error":"unauthorized"}              401
{"error":"path not found"}            404

# your agent writes one branch. done.
pricing

Two prices. No tiers-of-tiers page.

the key
$150
per month · cancel by letting it lapse
  • full metric catalog, all covered futures
  • trailing 30+ day window, through last Friday
  • agent-operable docs, uniform error contract
  • email attached only if you want receipts
the whole thing
$75,000
once · the tech buy-out
  • the engine, the domain, the server
  • 90% of all ongoing user profits
  • the unnamed thing becomes your unnamed thing

One operator built this and one operator runs it. If that's a bug for your procurement process, the second card is the fix.

your key is the door