For AI agents

Trading strategies on demand, for AI agents.

An AI agent hands Runbot a whole task in one prompt, or calls its tools one by one and decides for itself. Either way it pays per call, only when the job succeeds.

See how it works
01

Complete tasks

One prompt states the goal; Runbot returns the strategy, its backtest, its optimized version and an export.

02

Simple tool calls

Build, backtest, optimize, export: the user's agent reasons and calls each tool itself.

03

MCP API

Public and paid per call: an MCP server for agents that speak the Model Context Protocol, and REST endpoints.

04

Pay per call

Settled in stablecoins over x402, and only when the job succeeds.

Two ways to use it

  • Complete tasks. The agent states a goal in one prompt. Runbot builds the strategy, backtests it, optimizes it and returns it with an export.
  • Simple tool calls. Build, backtest, optimize and export are separate tools. The user's own agent reasons, calls them one by one and decides what comes next.

Prompts an agent can send

  • "Find a BTC strategy with an APR of at least 40% and a drawdown under 15%."
  • "Build a Polymarket 5-minute Up/Down strategy that never pays more than 0.60 a share."
  • "Build an ETH mean-reversion strategy on Hyperliquid and optimize it for Sharpe."
  • "Backtest this strategy on the last 365 days and compare it with the last 30."
  • "Take the best variant and export it, ready to import."

A complete task, in one call

The agent sends its goal. The MCP API answers with a payment request, the agent replays the call with a signed payment, and the payment settles only if the job succeeds. The agent then polls until the job is done.

agent · complete task
# one prompt, one complete task
POST https://mcp.runbot.io/v1/quick-strategy
{ "description": "Find a BTC strategy with an APR of
    at least 40% and a drawdown under 15%" }

← 402 Payment Required · x402
# replay with a signed payment header
← 200 { "job_id": "…" }  settled only on success
# poll until completed
← completed · baseline vs optimized · export ready

Simple tool calls, driven by your agent

Here the reasoning stays with the user's agent: it picks the tools, reads each result and chooses the next step. Every call is paid on its own.

agent · tool calls
# the user's own agent plans, then calls each tool
→ build      "ETH mean reversion on Hyperliquid, 15-minute candles"
← strategy ready · first backtest: APR 18.2% · drawdown 11.4%
→ optimize   goal: APR ≥ 40% · drawdown ≤ 15%
← 2 variants · best APR 41.7% · drawdown 13.9%
→ backtest   best variant · last 365 days
← APR 38.9% · drawdown 14.2%
→ export
← import-ready strategy

Figures are illustrative. Read the Strategy Copilot docs for the endpoints and the payment flow.

What the agent gets back

  • The strategy, built by the same AI Agent as the app and checked against the engine.
  • Its backtest on real order books, with every metric.
  • Its optimized version, next to the baseline.
  • An export, ready to use.
FAQ

Frequently asked questions.

Is the Strategy Copilot an MCP server?

Yes. It exposes an MCP server for agents that speak the Model Context Protocol, and plain REST for everything else.

How is it paid?

Per call, in stablecoins over x402, and only when the job succeeds.

Where is the documentation?

On the Strategy Copilot page of the Runbot product tour.

Let's talk

Your brand. Our engine.

Tell us about your community, the markets you want to open and your timeline. We will show you the app under your brand.