The ETF Setups API

The live ETF signal board as structured data. Every active setup with its entry, stop, and targets, ready to screen, backtest, or route to a broker.

What the API returns

  • Live board. Every active ETF setup with direction, entry, stop, and targets attached.
  • Setup history. Past setups and how they resolved, so you can test your own overlays on top.
  • Universe. The ETF universe the engine tracks, so your job knows what it can query.
  • Sector context. Which corner of the market a setup sits in, for position sizing and exposure limits.
  • Webhooks. A push when a new setup posts to the board.

Typed JSON your code and your agents can read

GET /v1/signals/live
{
  "as_of": "2026-08-24T13:35:00Z",
  "setups": [
    {
      "ticker": "EXMPL",
      "state": "active",
      "direction": "long",
      "timeframe": "daily",
      "entry": 123.45,
      "stop": 118.90,
      "targets": [131.20, 138.75]
    }
  ]
}

Illustrative example. Tickers and prices are placeholders. Real values are available to API subscribers.

Get early access

We are opening access to a first group of builders and systematic traders. Add your email and tell us what you plan to build.

Questions

What is the ETF Setups API?

It is the developer interface to ETF Setups. A REST API and webhooks that expose the engine output as structured data, so you can research and trade programmatically.

Does it work with Claude and OpenAI?

Yes. Responses carry structured fields and a plain language summary, so agents can consume them directly. An MCP server is planned for early access.

Do I get the logic behind the signals?

No. The API returns the output of the engine, not the rules that produce it, so you can build on the signals without the method being exposed.

How is it priced?

It is a paid product with tiers for individual traders and for teams building on the data. Join the list for pricing and early access details.

This API provides market data and signals for informational purposes only and is not financial advice. Example responses on this page are illustrative and use placeholder values.