Developers

Read FirmTape's measurements from code: the live levels, the order ledger, your alerts as signed webhooks, the archive, LAB and Geo. Every reference page names the plan it needs and links back to the feature it serves.

Base URL https://firmtape.comJSON over HTTPSTimes in ETopenapi.json MCP

Quickstart

Pick the product. Each card below says which plan it needs. Finished sessions are free and need no key.
Make an API key on the account page, with the scope of that product. It is shown once; one key per machine.
Call it. curl -H "Authorization: Bearer $FIRMTAPE_LIVE_KEY" "https://firmtape.com/api/v1/levels?sym=SPX,ES"

The full quickstart, with Python and Node.

By product

LIVELIVE

Levels API

Guide: LIVE

ORDERSORDERS

Orders API and POSITIONS API

Guide: ORDERS

LABLAB

LAB API

Guide: LAB

REPLAYFREE

Archive JSON and the free MCP server

Guide: REPLAY

DATASETDATASET

Dataset files

GET /snapshots/{file}

Guide: DATASET

GEOGEO

Geo API

Guide: GEO

API keys and scopes

One name, API key, for every key a program sends. A key carries a scope: the products it opens. The prefix names the scope, so a key pasted into a chart plugin is visibly not one that spends Lab credits. Send it as Authorization: Bearer <key>.

Scope	Prefix	Opens	Plan	Made on
`live`	`ftpl_`	The levels API (`/api/v1`), the platform integrations	LIVE	Account, Integrations
`lab`	`labk_`	The LAB API (`/api/lab`, `/api/struct`), the MCP server's `lab_` tools	LAB	Account, LAB
`dataset`	`labk_`	The DATASET files (`/snapshots/<day>.json.gz`) and levels API history older than 90 days	DATASET	Account, LAB
`orders`	`ordk_`	The Orders API (`/orders/api`), the POSITIONS API (`/api/positions`), the Orders MCP server (`/orders/mcp`)	ORDERS	Account, Orders
`geo`	`gk_`	The Geo API (`geo.firmtape.com/v1`), the Geo MCP server	GEO	Account, Geo, Keys

Rotation, revocation, the signing secret and the legacy key in the address.

Across products

Errors

Branch on the status, then on a stable code. Retry only 429 and 5xx.

Rate limits

Per key or per account, read from the answer's headers.

Webhooks

Signed with HMAC-SHA256 over the timestamp and the raw body; retries, test events, the planned single format.

MCP

mcp.firmtape.com for the archive and LAB; tools, auth, limits, client setup.

Versioning

Additive changes within a version, dated; deprecations with a removal date.

For AI agents

A Markdown copy of every page, one index, the OpenAPI document.

Planned

Measurements of dealer positioning, never a forecast or a trade call. This page is built from FirmTape's public contract, the same files the OpenAPI document is built from; the tests hold them against the route code. Markdown: /docs/developers.md.