Skip to main content
Answers to the questions that come up most often in Discord and support. Each one links to the full page if you want the detail.

​
Charts and drawings

Every drawing has a sync level that decides which charts it appears on. You set it per drawing, in the drawing’s settings or from the Object Tree:
  • Local — the drawing stays on the chart you drew it on. This is the default.
  • Channel — it appears on every chart in the same linked channel.
  • Workspace — it appears on every chart in the current workspace.
  • Global — it appears on every chart, in every workspace.
This is what trips people up most often: a chart you forked and dropped into a workspace as an unlinked widget is its own chart, so a drawing made on it at the default Local level lives only there. To use the same level elsewhere, raise its sync level — to Workspace, for example — and it shows up on the other charts too.Sync works across timeframes as well as across charts, so a level drawn on the 1H stays where it belongs on the daily. See Sync tool.
Our own. We use open-source components where it makes sense, but the rendering engine (WebGL), the drawings, the indicators, the settings, and the UX are all ours. That is why the charts feel more responsive than an embedded widget — and it is also why indicators are written in Indie rather than in someone else’s language.

​
Market data

US exchanges charge licensing fees to display real-time quotes, and each licence covers a different slice of the market. For intraday US equity quotes we currently use CBOE data — the same category of licence other retail charting platforms use. It is a consolidated view rather than the primary exchange feed, so the volume printed on a bar can differ from a platform quoting a primary feed. Prices track closely; volume is where you see it.We are moving coverage onto direct exchange feeds as our brokerage integrations go live. See Markets We Cover for what is available today.
It depends on the venue. For the venues we are integrated with directly — Bybit, Binance and Exness — the data comes straight from the venue. The rest of our coverage currently arrives through a third-party market-data aggregator.Abnormal candles almost always come from the aggregated feed rather than from our side: the same print is usually present in the provider’s own API. We cannot guarantee the same quality there as on a direct connection, which is why we keep moving venues over to direct exchange feeds one at a time. Trading is offered only on venues we connect to directly.

​
Alerts

We measure it end to end — from receiving the tick from the exchange, through triggering the alert on our server, to delivering it to the server that receives your webhook. In our measurements it is typically around 300 ms, and up to about 1 second in the worst case.That is a measurement of the alert pipeline, not a guaranteed delivery time. Delivery to a messenger or an email inbox adds whatever that channel adds, and per-channel rate limits apply — see Alert limitations and delivery.
Yes — an alert can trigger on an indicator value, not only on price. See Alert trigger criteria for the conditions available.Through the AI assistant and the MCP server this also works on a private indicator of your own: once it is saved to My scripts, the alert can be created on it without publishing it to the Marketplace first. The assistant can write the indicator, save it, and set the alert in the same conversation.

​
Indicators and AI

Give the script to the AI assistant and ask it to convert it to Indie. It knows the language, compiles what it writes, and fixes the errors it finds. Work in the AI Chat, where a script can be opened in a real IDE tab and added to a chart, or in the IDE assistant if you are already in the editor.Convert one indicator at a time and say what it is supposed to do — a conversion that keeps the intent beats one that keeps the syntax. Indie is a Python subset, so most Pine logic has a direct equivalent; see Language differences with Python for what does not.
The MCP Server Setup Guide has step-by-step instructions for Claude, Claude Code, Codex, Cursor, VS Code, and any application that can run mcp-remote. In short: add https://mcp.takeprofit.com/mcp as a custom connector and sign in when prompted.Once connected, your AI application can write and validate Indie code, search the Marketplace, work with your private scripts, manage your alerts, and read and edit your watchlists.
The AI Chat is ours: it runs on the platform, draws on the hosted budget that comes with All-In (or on your own API key from Anthropic, OpenAI, or OpenRouter), and hands back charts, screens, and IDE tabs you can keep working with. The MCP server puts the same platform capabilities inside an AI application you already use — Claude, Codex, Cursor, VS Code — and runs on that application’s own subscription.

​
Platform and mobile

No but the platform can run in your phone’s browser. If you want it one tap away, add it to your home screen. It gets its own icon and opens straight into the platform, without the browser’s address bar in the way.On iPhone and iPad, in Safari:
  1. Open takeprofit.com and sign in.
  2. Tap the Share button in the toolbar — the square with the arrow pointing up.
  3. Scroll down the list and tap Add to Home Screen.
  4. Rename it if you like, then tap Add.
On Android, in Chrome:
  1. Open takeprofit.com and sign in.
  2. Tap the ⋮ menu in the top-right corner.
  3. Tap Add to Home screen, then confirm.
Other mobile browsers have the same thing under a different name — Firefox calls it Install, Samsung Internet puts Add page to in its menu. The shortcut keeps you signed in, so it opens on your workspace rather than on the login screen.
For long sessions — building a multi-widget layout, writing an indicator in the IDE, running a backtest — the desktop is still the place to work. The phone is built as a second screen for checking a setup and acting on an alert. See On your phone for what changes on a touch screen.
Question not answered here? Ask in Discord or email support@takeprofit.com.