Read your results from your own tools
Torque Lift's read-only API and MCP server. Keys, limits, and a first request.
Torque Lift has a read-only API, and an MCP server built from it so an AI agent such as Claude Code can ask about your results in plain words. Early partners get a key first.
Early access
Keys go to early partners. Join the waitlist and we'll send one once you're in.
What you can read
- The actions Torque Lift took, its pull requests, the experiments it recommended and ran with their results, the weekly readouts, and your tracking plan.
- Your numbers: growth accounting, funnels, who your users are, and whether your events are arriving. Each figure carries the saved query behind it.
- Nothing here merges or approves a pull request, opens one, or changes your data. It only reads.
Keys and limits
- A key reads one team's results and no one else's. Every night we read each route as each team and fail the check if anything of another team comes back.
- Keys look like
tl_live_.... Send one as a bearer token:Authorization: Bearer $TORQUE_LIFT_KEY. - Each key gets 120 requests a minute. Past that you get a
429with aRetry-Afterheader. Every response names the API version it was made with.
Try it
Ask who your key belongs to:
curl https://api.torquelift.ai/v1/account \
-H "Authorization: Bearer $TORQUE_LIFT_KEY"The reference
Every operation below is generated from the OpenAPI file the API itself serves at /v1/openapi.json. It needs no key to read.
Account
Who your key belongs to.
Action log
Every action Torque Lift took, incidents, and what agents asked.
Pull requests
The pull requests Torque Lift opened.
Experiments
Recommendations, and experiments with their checks and results.
Readouts
The weekly readouts, as Markdown.
Tracking
The tracking plan in force, and at any commit.
Your numbers
Growth accounting, segments and funnels.
Data health
Pipeline status, events, and turned-away calls.