If you have ever asked a general-purpose AI chatbot to write a ProRealTime indicator, you know how it goes: the code looks plausible, you paste it, ProRealTime throws an error on line 4, you paste the error back, the chatbot apologises and invents a different non-existent function. Ten round trips later you give up and open the forum.
ProRealAI was built by the ProRealCode team to end that loop. It is an AI assistant that writes, fixes and explains ProBuilder, ProOrder and ProScreener code, and nothing else. This tutorial covers what it is, why it works where generic assistants fail, how to use it step by step, and how to get the most out of the free credits.
Quick links: open ProRealAI · the complete ProRealAI guide · the ProRealAI group for questions and support
Why ProRealAI is not just another chatbot
Generic AI assistants know ProBuilder badly. The language is small, its documentation is scattered, and the models have seen far more Pine Script, MQL and Python than ProBuilder. So they guess. They mix ProBuilder syntax with other platforms’, invent functions that do not exist, and forget that a variable must be defined before it is used. The result compiles maybe one time in three.
ProRealAI takes the opposite approach. It was designed for a single platform and a single family of languages, and it does not guess the syntax: it verifies it, on every answer, before a single line of code is shown. Three things make that possible, and to our knowledge no other tool does them:
1. Built by ProRealCode
ProRealCode is the reference community of ProRealTime users, with more than a decade of indicators, strategies, screeners and forum threads. Everything the community has accumulated about the platform sits behind every answer.
2. It checks before it answers
Every function, every reserved word and every DEFPARAM option is checked against the official ProBuilder, ProOrder and ProScreener documentation before the code appears on screen. If you ask for something the platform cannot do, it tells you instead of making up a function.
3. Wired live to prorealcode.com
The assistant searches the ProRealCode library, snippets and forum in real time. When a solution appears on prorealcode.com, ProRealAI can use it the same day. You are not talking to a frozen snapshot of the web.
The verification steps are shown on screen while it works (“checking the syntax”, “searching the library”…), so nothing is a black box: you can see what it looked up before it wrote the code.
How effective is it?
The honest answer: far more effective than any general assistant on ProBuilder, and not infallible. Here is what you can count on.
- 100% of the code is syntax-verified before display. Function names, reserved words and parameter options are checked against the official documentation. This removes the most common failure of generic chatbots: code that simply does not compile.
- Three languages covered: ProBuilder (indicators), ProOrder (trading systems) and ProScreener (screeners), each with its own constraints.
- Thousands of sessions have already been answered and resolved, from a first “write me an RSI” to full multi-timeframe strategies with position sizing and trailing stops.
- Seven interface languages (English, French, German, Spanish, Italian, Swedish and Dutch) and it answers in the language of the question, including languages outside those seven.
What it does not do: it does not give investment advice, it has no access to live market data, and like any AI it can still get the logic wrong even when the syntax is right. Always review and backtest the code before using it on a live account. Treat it as a very fast, very well-read ProRealCode coder sitting next to you, not as an oracle.
Step 1: sign in
ProRealAI uses your ProRealCode account, the same one you use on the forum. There is no separate sign-up and no premium membership required.
- If you do not have a ProRealCode account yet, create one for free on prorealcode.com.
- Once signed in, open ai.prorealcode.com. You are recognised automatically.
- Your credit balance is shown at the top of the screen. New accounts start with 150 free credits, topped back up to 150 every 30 days, no card required.
A built-in one-minute tutorial appears on first launch and shows where to paste each type of code in ProRealTime.
Step 2: describe what you want in plain words
No jargon is required. Type a sentence in the composer, for example:
Write an RSI divergence indicator with an EMA 200 trend filter.
If a detail is missing (which timeframe? which RSI period?), the assistant asks a question rather than assuming. The more complete your description, the fewer round trips it takes. A good request for a trading system includes:
- the market and timeframe,
- the entry and exit rules,
- the stop-loss, take-profit and trailing logic,
- position sizing and trading hours if relevant.
Step 3: read the answer, then copy, paste, test
Each code block comes with its own Copy button, the destination named (Indicator, Strategy or Screener) and the exact path to paste it into ProRealTime, for example: Code editor → Create a new indicator → Paste the code → Run.
Here is the kind of answer you get when you ask for a bullish trend screener on the EMA 50/200 crossover:
// Bullish trend screener, EMA 50/200
ema50 = ExponentialAverage[50](close)
ema200 = ExponentialAverage[200](close)
// bullish crossover EMA 50 / EMA 200
c1 = ema50 CROSSES OVER ema200
SCREENER[c1](close AS "Close")Paste it in ProScreener (Screeners → Create a screener → Paste → Run), pick your list of instruments and timeframe, and it runs first time.
Step 4: iterate in the same conversation
The conversation keeps its context, so you can continue naturally:
- “Add a trailing stop of 2 ATR.”
- “Turn this indicator into a screener.”
- “Why does the backtest never go short?”
- “Make it work on a 1-hour chart with a daily EMA.”
One thing to know: conversation memory covers the last six exchanges. For a long project, summarise where you are (“here is the current code, now I want…”) rather than relying on something you said twenty messages ago.
Fixing code that does not compile
This is where ProRealAI saves the most time. Paste the whole code and ProRealTime’s exact error message, for example:
My screener does not compile, ProRealTime says “Error line 4: the variable MyEma50 is not defined”.
The assistant locates the cause (here, a variable used before it is calculated), explains it in one sentence and returns the corrected version. It also handles the trickier cases where the code compiles but behaves wrongly: a strategy that re-enters on every bar, a system that never exits, a repainting indicator, a look-ahead bias that makes the backtest look too good.
Everything else it can do
- Write an indicator: divergences, adaptive moving averages, session levels, multi-timeframe indicators.
- Build a trading system: entries, exits, stops, position sizing, trading hours, complete ProOrder code ready to backtest.
- Create a screener: filter whole markets on your own criteria, within ProScreener’s limits.
- Convert between types: an indicator becomes a screener, a strategy condition becomes a visual indicator, without rewriting everything.
- Translate from elsewhere: paste a Pine Script (TradingView) script, a book excerpt or an article; the idea is restated in ProBuilder with its function equivalents. (Translation from ProBuilder to other platforms is not offered.)
- Audit code from the forum: paste an existing indicator or strategy and ask what could distort the results.
- Explain the platform:
TIMEFRAME,DEFPARAM, tick-by-tick versus on-close, spread and commissions, walk-forward, overfitting, with concrete examples.
Understanding credits
ProRealAI has no subscription. Every exchange consumes credits according to the work actually done: the length of the conversation, the searches it triggers and the length of the answer. A typical exchange costs about 9 credits (the median over thousands of real sessions), so the 150 free credits are roughly fifteen exchanges a month, enough to write and fix your first indicators.
If you need more, credits are bought in packs and added to your balance:
- Starter: 375 credits, €5, email support
- Plus: 1 250 credits (of which 125 free), €15, email support
- Max: 4 000 credits (of which 625 free), €45, priority support
Purchased credits never expire. Credits are deducted when the answer completes, never before, and the balance never goes negative: if an answer overruns what is left, ProRealCode covers the difference. Payment goes through Stripe with a numbered PDF invoice. The credit cost of every conversation is shown in the interface, so there are no surprises.
Three habits to get the most from your credits
- One conversation per subject. A long conversation costs more with every exchange, because the whole context is re-read. New subject, new conversation.
- One precise request. Timeframe, market, entry and exit rules, risk management: the more complete the description, the fewer round trips.
- The whole error message. For a fix, paste the code and ProRealTime’s exact message. You get a correct answer the first time.
Privacy and limits
- Your conversations are not used to train any AI model. ProRealAI relies on a third-party AI provider under a data processing agreement and the EU standard contractual clauses.
- Conversations are kept for twelve months and can be deleted at any time from the interface.
- ProRealAI is a programming aid for educational and exploratory use. It is not investment advice and issues no buy or sell signal.
Questions and support: the ProRealAI group
Questions, feedback, feature requests and support topics for ProRealAI are gathered in one place on the forum: the ProRealAI group. Join it to ask a question, report a wrong answer, share a good prompt or see what other users are building. It is also the place to follow announcements of new features. Membership is free with your ProRealCode account.
Ready to try?
Sign in with your ProRealCode account, open ai.prorealcode.com and describe your first indicator. The first 150 credits are free, and the full feature list, FAQ and pricing are on the ProRealAI guide page.
ProRealAI is also available in other languages: Français · Deutsch · Español · Italiano · Svenska · Nederlands.