Skip to main content
The AskFutures web app talks to a private HTTP backend. That backend is not a third-party API — it’s an internal interface, and its endpoints are not a supported, stable contract for outside callers.
Don’t build against the internal HTTP endpoints. They are private, can change without notice, and aren’t documented as callable contracts. The MCP tools are the supported public mapping of what the app can do.

​
What this means

  • The MCP server is the public surface. Anything you’d want to do programmatically — sessions, strategies, backtests, optimization, reference data — is exposed as an MCP tool. Use those.
  • The HTTP backend is an implementation detail. The web app uses it; the MCP server uses it on your behalf. It’s not for you to call directly.
  • No endpoint contracts here. We deliberately don’t publish request/response schemas for the internal endpoints, because they aren’t a promise we keep for external integrations.

​
How the layers fit

The browser app and the MCP server are both clients of the same private backend. You sit on the MCP side. The MCP tools are a stable, intentional mapping over that backend: each tool takes care of the calls, the async polling, and the response shaping for you. So when you call create_strategy or wait_for_completion, you’re getting the supported version of what the app does — without depending on internal endpoints.
The supported public surface is the MCP server. The internal HTTP backend exists, but it’s private and outside the support boundary.

​
What to use instead

MCP tool reference

The public, documented tools — inputs and response shapes.

Developers overview

Connect a client and start driving AskFutures.

​
Next steps

Quickstart

Connect and run your first strategy programmatically.

Tools walkthrough

The MCP tools, explained as a workflow.