API/MCP field guide

Why it matters

Skylit computes a lot of things that are hard to compute: where dealers are positioned strike by strike, which options trades were aggressive, and how much movement is priced into a chain relative to that symbol's own past. The app shows you those answers. The API and the MCP server hand you the same computed numbers so your own code — or your own AI assistant — can use them.

That matters in three ways:

• Your screen and your script agree. Both read the same series, so a rule you check in code is a rule about what the board actually showed.
• An assistant can answer in English. Over the Model Context Protocol you ask a question and the assistant picks the tool, reads the result and answers. You do not write the call.
• You can see what it costs. Calls are metered in credits, each response carries the balance left, and anything that fails is refunded.

Everything is read-only. There is no way to place, change or cancel an order through the API or the MCP server.

Where to find it

Open the Developer page in Skylit. It is where you:

• create and revoke keys — up to five on a paid plan,
• see your credit balance, your monthly allowance and the limits on your account,
• buy a credit pack,
• redeem an invite code, under Have an invite code?,
• review and disconnect any AI client you connected with Sign in with Skylit.

The full reference lives in the docs:

• API Reference — every call, its parameters, its response and its cost.
• MCP overview — the server, how to authenticate, and what the tools cover.
• Quickstart — connecting a client, with or without a key.
• Tool catalog — all 63 tools, grouped, with costs.
• Intelligence tools — the short tool list that answers a whole question in one call.
• Plans and credits — which plan reaches which data.

Read it in 30 seconds

How to use it

Over HTTP

Send your key as a bearer token and read JSON. The data divides into four groups:

• Positioning — the live per-strike gamma and vanna board for one or more symbols, with the velocity metric and Skylit's node classification; the same board at a past instant; every snapshot across a window; and the classified key levels on their own.
• Flow — scored trades, multi-exchange sweeps, bullish-versus-bearish tide, momentum against a trailing baseline of the same time of day, strike concentration, screeners for unusual volume and open-interest change, and dark pool prints.
• Volatility — implied volatility per symbol with its percentile, term structure, expected-move cones, the move in units of the implied move, surface and skew, call-versus-put premium imbalance, event implied moves, a screener over the whole universe, and daily history.
• Account and catalog — your balance and limits, the symbol catalog, and daily statistics per symbol. The account call is free.

Two of the groups also stream over Server-Sent Events, so a long-running process follows the session rather than polling it.

Price bars are served separately, on their own host; the API Reference says which.

Over MCP

The Model Context Protocol is a standard way for an AI assistant to call outside tools. Point a client at https://mcp.skylit.ai/mcp and the assistant can query Skylit in the middle of a conversation: ask "were there unusual bullish sweeps on TSLA on Friday?" and it calls the tool that answers, reads the result and replies.

Two ways to connect:

• Sign in with Skylit. Clients that support it — including Claude, Claude Code, Cursor, VS Code and ChatGPT — need only the address. The client opens a Skylit page and you click Approve. No key is ever pasted into a config file, and you can disconnect it later from the Developer page.
• A key. Headless agents, scripts and clients without sign-in send Authorization: Bearer <your key> instead.

There are 63 tools, each wrapping one call one-to-one: same sign-in, same cost, same JSON. They are grouped so an assistant can find valid symbols first and then reach for analytics.

To let an assistant read these guides instead of live data, there is a separate free docs server that needs no key: see Docs MCP.

Credits

Calls are metered in credits. One credit is $0.001, every call's cost is published on its reference page, and the cost is the same on every plan.

• Pro, Protege, Quant, Lifetime Bootcamp and the Developer plan at $349 a month include 100,000 credits a month, which reset at the start of each month and are spent before any you added yourself. The Developer plan is the API and MCP access on its own, without the web platform's trading tools.
• Initiate and Community start with 5,000 credits, once, and then run pay as you go, each with a daily ceiling.
• Credit packs start at $50 for 55,000 credits and stay valid for twelve months. Add one from the Developer page; promo codes do not apply to packs.
• Anything that fails is refunded — a rejected or errored call costs nothing, and the balance reported on it already includes the refund.

Keys

Treat a key like a password. Keep it in an environment variable, never in source control and never pasted into a shared prompt. If one leaks, revoke it on the Developer page and create another — you can hold five at once, which is enough to rotate without downtime.

Use it with other Skylit tools

• Heatseeker. The board, the key levels and the replay window you read on screen, as JSON. Useful for checking an idea against what the board actually showed at the time.
• Flowseeker. The scored flow, sweeps and tide behind the live feed, so a screen you assembled by hand can run on a schedule.
• Tempest. Volatility readings and the whole-universe screener, on plans that include Tempest. On a plan without it the volatility tools answer with a free refusal rather than a surprise charge.
• Atlas. Price bars come from their own host, so a chart you build yourself can line up with the board.

Ask Talon

Talon already reads this data inside Skylit, so you do not need a key to ask it a question in the app. The MCP server is for the assistant you run yourself — in your editor, in your terminal, or on a machine with no screen.

Good to know

• Read-only, always. No call and no tool can place, change or cancel an order.
• Beta. Tools, groupings and limits can still change. Names in the tool catalog are the stable surface; treat anything else as liable to move.
• Session guardrails on MCP. The gateway caps how many calls one assistant session may make and how many may be in flight at once. Past the cap a tool returns an error explaining the limit rather than running unbounded, and credits are only ever spent on calls that reach the data.
• A plan without a product gets a free refusal. Asking for volatility data on a plan that does not include it returns a not-entitled error and costs nothing.
• Live numbers move. A figure fetched a second ago and a figure on screen now can differ. Each response carries the time it was computed; line the two up on that rather than on wall-clock time.
• Educational. The data describes what the market is doing. It is not advice, and nothing in a response is a recommendation.

What's new

Nothing new for members yet.

Glossary

Glossary not exported yet. Run scripts/export_copy.py.