Skip to content
Integrations

What PTQ connects to today

Connect PTQ to your current setup. We focus on matching data streams rather than replacing your favourite platforms.

  • Alpacapaper trading
  • TradingViewPine v6 study export
  • ClaudeMCP connector
  • Market datahistorical bars, cached

Alpaca

Paper trading

US equities, paper orders from your own computer. Every fill is labelled simulated.

In your browser, PTQ simulates practice orders itself. No broker receives those orders. To send paper orders to Alpaca, connect its paper API from PTQ on your own computer. Both paths use pretend money.

Live trading runs on your own computer, not on ours. Your broker keys stay on your machine and never reach our servers. The live path is experimental today, so paper is where the work happens.

Execution: the one place an order leaves PTQ. Paper only, and every fill is labelled simulated
Execution: the one place an order leaves PTQ. Paper only, and every fill is labelled simulated

TradingView

Pine v6 study export

PTQ charts natively; export a Pine study to see signals on TradingView. Pine runs only there. Execution and risk stay in PTQ.

Pine is the language TradingView charts run on. One way only. Your entries and exits, plotted as a Pine v6 study on charts you already use. Nothing comes back the other way, and nothing executes from a chart.

your signals as a Pine v6 study on a TradingView chart. illustration, not a screenshot

Claude

MCP connector

Ask about your strategies, runs and results in plain English. Claude reads them from PTQ on your machine and answers. MCP, the Model Context Protocol, is how the two talk.

The conversation stays on your machine, like your keys. Claude reads what you ask it to. It never trades.

claude · this machine

# Model Context Protocol, on this machine

claude ⇄ MCP ⇄ PTQ OS (your machine)

you    › ask about your strategies, runs and results

claude › [reads them over MCP, answers in plain English]

# broker keys stay in your keychain. The connector never sees them

how the connector works. An illustration, not a screenshot

Market data

Historical bars

PTQ comes with past market data, already stored, so you can backtest from the first day. A backtest runs your strategy over those past prices to see what it would have done.

The app lists which markets and dates are covered. Every backtest records the data it ran on.

Backtest run: real output from the engine, run on past prices
Backtest run: real output from the engine, run on past prices
Venues

Where your orders can go

The system strictly executes orders through authorised API endpoints. Every trade action requires your explicit confirmation.

AlpacaUS equities, paper orders from your own computer. Browser practice stays inside PTQ. Live connection is experimental.

Unattended live execution is currently disabled for compliance.

PTQ takes no commission and has no commercial relationship with any venue here. Venue names are the trademarks of their owners, used only to say what PTQ connects to.

PTQ

Use what you already have

Run the same checks on every strategy before you risk real money.