Find your way around MIRRO

Use the Trading and Copy APIs to connect trading accounts to your application
Use prop-firm software for challenge evaluation, trader workspaces and a turnkey website
Use Mira AI to work on code or bring an assistant into your business
Each product has its own setup and pricing

No
Mira for business gives your business a separate workspace for knowledge, API keys, credit and support
Build with Mira is the coding workspace for projects, previews and publishing

No
The account plan covers trading APIs and hosting for the selected trading account
Mira AI uses separate credit; prop-firm services, workspace capacity and implementation follow your approved quote

Use MIRRO HQ to copy trades between your accounts or from TradingView and Telegram without coding
Use MIRRO API to build trading into your own app
Starting or running a prop firm? Explore our business platform

No
MIRRO HQ costs $6 per linked account every 30 days, with credit renewals and no hourly billing
MIRRO API offers account plans and hourly billing for uncovered connected hours
Prop-firm packages and MAX Copier programmes have their own pricing
Check the pricing for the product you are using

Yes
Usage shows connected account hours and cost estimates
Billing shows your credit, payments and posted charges in USD
You can also read the usage breakdown at GET /v1/usage

A trading account plan is 6 USD per account per 30 days, with trading APIs and connection hosting included for that account
No hourly connection charge applies while its plan is paid; it renews from your credit unless you turn renewal off
Hours no plan covers are pay as you go: per account, per hour deployed, rounded up to the hour
GET /v1/usage shows each account’s hours, charges and plan coverage
Mira AI credit and prop-firm packages are priced separately

With a plan on every account: 6 USD per account per 30 days, whatever the platform, excluding tax
Without a plan, multiply the hourly rate for your account type by the hours you expect the account to be connected: USD 0.0056 per hour for an API-platform account (cTrader, TradeLocker) and USD 0.0125 per hour for a MetaTrader terminal account (MT4 or MT5)
Standard reliability includes one terminal per MetaTrader account, without a standby terminal

Trading API requests are included in your account charges and are rate-limited per key
Read and trade limits appear on the key and at GET /v1/quotas; request an increase through API access for review
Mira AI responses use separate credit
Prop-firm API usage and any agreed overage charges follow the firm’s approved package

Billing shows the payment methods enabled for your account and country, including card or supported stablecoin options where available
Your credit balance is recorded in USD
Review the checkout currency, exchange rate and final amount before paying
Firm-owned challenge checkouts use the firm’s own payment providers and supported currencies

MetaTrader 4 and MetaTrader 5 with valid account credentials and a reachable broker server
We host their terminals
Connect cTrader through its sign-in page and TradeLocker through the broker-login flow in the console
GET /v1/platforms lists current capabilities and each connection method in selfOnboard.via
Account checks apply; live copying requires the account holder’s approval
Platform-specific order limits are listed in the API reference

No trading VPS is needed
For MetaTrader 4 and 5, MIRRO runs a cloud terminal of the right version per account
cTrader and TradeLocker connect directly
You do not need to install or maintain a trading terminal
You still run your own application and any webhook receiver; our prop-firm workspace is hosted for you

MIRRO manages the trading connections around the clock, independently of your browser or computer
Keep the account funded under its billing option and its broker access active
Trades depend on market hours, account checks and broker availability
This is not an uptime or execution-time guarantee

Add the account details or authorise access, then follow its status in the console
Initial cloud setup and broker checks can take a few minutes
Start making requests when the account is ready; a successful sign-in alone does not mean trading is enabled

Standard reliability uses one cloud terminal per MetaTrader 4 or 5 account
A standby terminal is not included
Requests for high reliability return RELIABILITY_UNAVAILABLE
cTrader and TradeLocker use their platform APIs rather than a hosted MetaTrader terminal

Yes, on any platform
An account whose firm has withdrawn access fails closed: a trade on it is refused with FIRM_UNREACHABLE rather than queued, the account page shows it, and the reason stays in the audit log

Per key, with separate read and trade buckets
The limits are on the key itself (rateLimits) and at GET /v1/quotas, and every response carries X-RateLimit-Limit and X-RateLimit-Remaining
GET /v1/capabilities reports the running release's limits
The stream allows 2 sockets per key and 4 per address, and each channel read spends one unit of the key's read bucket
Concurrency overload returns 503 API_BUSY with Retry-After; quota exhaustion returns 429

Our engineering target is under 30 ms average MIRRO processing and under 50 ms at the 99th percentile
This is a target, not a maximum-time guarantee
Broker-confirmed completion is measured separately: latencyMs runs from the command ledger to the terminal answer, while Server-Timing measures HTTP gateway handling
Broker and network delays can make completed trades take substantially longer

You are told exactly that
A command a terminal took and never answered ends expired with result.code: EXECUTION_UNKNOWN — never “rejected” — because it may have executed; read the positions and the deal history before sending it again
A temporary broker answer (requote, off quotes) is re-driven until the command expires and only then ends EXECUTION_TRANSIENT_EXHAUSTED
A late answer replaces either ending and says what it corrected
And a refusal we make ourselves, before any terminal sees the order, is EXECUTION_REFUSED, not a broker rejection

It can be unavailable, and then it says so: if we cannot read an account's book, GET /positions and GET /orders answer 503 BOOK_UNAVAILABLE rather than an empty list
An empty list means the account is flat; an error means we do not know

Connected-account secrets are encrypted and excluded from ordinary account listings
cTrader connects through its own authorization flow, so you do not enter your cTrader password into MIRRO
Credentials for newly created demo accounts can be revealed only through authorized account-delivery flows
Keep API keys and broker credentials out of public code, analytics and logs

Trade scope on a live account requires a recorded, timestamped consent from the account holder, which the API exposes and stores
Copying into prop-firm accounts is refused unless the firm's published policy permits it

Yes
Symbols are translated through a canonical instrument registry and money is converted at a cached rate
Choose sizing that fits the receiving account and review the broker’s instrument settings

Full master snapshots support reconciliation after missed messages
Only a trusted, fresh book can establish an exit
Broker outages, stale state and uncertain execution still require recovery; a dropped frame is not proof that a trade failed

Now
Sign up in the console, create a key under API access (a test key for demo accounts, a live key for live ones) and follow the quickstart: first trade on a demo account in one page, then the typed JavaScript client
Keys have specific permissions; start on a demo account before enabling live trading

The standard public account plan does not include a contractual uptime guarantee
Any service levels, support commitments or credits must be stated in your signed agreement
Published performance measurements describe the stated test conditions; they are not uptime or execution-time guarantees