fxapis vs MetaApi. A fair comparison, with sources.
Both are hosted APIs that run MetaTrader terminals so you don't have to. They are built for different jobs and priced in different ways. This page sets out where each is the better choice — including the things MetaApi does that fxapis does not.
Summary
MetaApi is likely the better fit if you need
- MT4 as well as MT5[9]
- Streaming prices and account updates over WebSocket, or historical candles and ticks[3]
- Copy trading with portfolios, magic-number filters and Telegram publishing (CopyFactory)[8]
- Trading statistics (MetaStats) or a risk-management API for challenges[9]
- Official SDKs in JavaScript, Python and Java[4]
- The lowest hourly hosting cost for accounts that are online only part of the time[1]
fxapis is likely the better fit if you want
- A monthly price that includes your first accounts, then a price per account, with executions pooled
- Click-to-trade: bring a member's account online when they open a signal, trade it on approval
- One order across many accounts, sized per account, with a result for each and your choice of barrier policy
- Unclear outcomes confirmed against the broker's records — never guessed — and idempotency keys on orders, closes and multi-account orders
- Close-only API keys, and closing never blocked for billing
- A small REST surface that is quick to learn, with examples in 13 languages
- A hosted MCP server: sign in from Claude or ChatGPT, read-only or trading per account
Per hour, or per month.
MetaApi
MetaApi combines a subscription with pay-as-you-go usage.[1] The Regular subscription is $30 a month and includes one MT account and a 7-day trial; Extended is $100 a month with dedicated servers and priority support; Business is custom, with an SLA.
On top, each account is billed per hour while it is deployed — running on MetaApi's servers — and per deployment, each time it is started. Prices load dynamically on metaapi.cloud; read from the rendered pricing section on 30 September 2026: $0.012 an hour and $0.072 a deployment on cloud-g2 (high reliability, their default); $0.019688 an hour and $0.118125 a deployment on cloud-g1 regular; $0.039376 an hour and $0.23625 a deployment on cloud-g1 high.[1] An undeployed account costs $0.00105 an hour, and adding a trading account costs $2.10 per unique account, charged once a month;[1] their FAQ adds that each start of an account's server is billed for at least six hours.[2] Add-ons are billed per account per hour too: CopyFactory $0.001575 on cloud-g2 ($0.1575 on cloud-g1), MetaStats $0.001575 and the risk management API $0.00315.[1] Prices exclude VAT.
At 720 hours a month, a cloud-g2 account online around the clock comes to about $8.64 a month in hosting.
fxapis
fxapis charges a monthly price that includes your first accounts — Production is $99 with 5 included — then a price per account, with opening executions pooled across them, and $7 a month for each account kept online around the clock. Closes, stop changes and cancellations are never counted. See pricing.
What that means in practice: MetaApi is cheaper on hosting. For the calculator's default — 20 accounts online around the clock and 2,000 orders a month — MetaApi on cloud-g2 comes to about $196 a month and fxapis Production to $314. For the click-to-trade pattern — the same 20 accounts started once a day and online for 2 hours — MetaApi comes to about $98, of which $41 is deployment fees; fxapis is $174, since accounts online on demand cost nothing by the hour. fxapis is priced for predictability and for what is included — multi-account orders, outcome confirmation, click-to-trade — rather than to undercut hourly hosting. Model your own numbers below.
Estimate a month on each.
Enter how many accounts you run, how long they are online each day, how often each is started on MetaApi, and how many orders you place. The formula and every assumption are shown under the result.
Production: $99.00 with 5 accounts included, plus each account beyond, always-on at $7.00 per account and any executions past the pooled allowance. Accounts online on demand cost nothing extra by the hour.
Subscription $30.00 + running accounts $164 + deployments $1.37. No per-order charge.
How these are worked out
fxapis: the cheapest published plan that allows 20 accounts and 2,000 orders, counting overage up to twice the allowance. Only orders that try to open a trade count; closes and stop changes never do.
MetaApi = subscription + (accounts − 1) × 24 h × 30 days × $0.012 + (accounts − 1) × 1 deployments × $0.072
Deployments: each time an account is started on MetaApi's servers is a deployment, and their pricing page lists a fee for each — 6 hours at the hourly rate; their billing FAQ says each start is billed for at least 6 hours. An account that comes online once a day for click-to-trade, and goes offline again, is about 30 deployments a month; one online around the clock is about one. We add the fee on top of the hours online, as the pricing page lists both; if MetaApi counts it towards the first 6 hours instead, the real figure is lower by up to (accounts − 1) × deployments × the fee. One account is treated as included in the subscription; add-ons (CopyFactory, MetaStats, risk management), the $2.10 for each unique account added, and VAT are left out.
Estimates only. Prices load dynamically on metaapi.cloud; read from the rendered pricing section on 30 September 2026, and they may have changed — check their current pricing before deciding.
Features, line by line.
MetaApi entries are as published on their site on 30 September 2026; the bracketed numbers link to each source.
| Aspect | fxapis | MetaApi |
|---|---|---|
| Platforms | MetaTrader 5 | MetaTrader 4 and 5[9] |
| Pricing | Monthly price with included accounts, then per account; executions pooled | Subscription plus per-account hourly usage[1] |
| Account online model | Always connected, on demand (offline after 15 idle minutes) or manual; prepare up to 200 at once | Deploy and undeploy each account; billed while deployed[2] |
| Time to connect | About 9.6 s, in one measured run (method) | Not published — “it can take some time”[6] |
| REST trading API | Yes | Yes[3] |
| Streaming (WebSocket) | No | YesPrices, account updates; SDK recommended[2] |
| Historical candles and ticks | No | Yes[3] |
| One order on many accounts | YesPer-account sizing, results and barrier policies | PartlyThrough CopyFactory copy trading[8] |
| Hosted copy-trading service | YesManaged copy trading: strategies and subscribers | YesCopyFactory[8] |
| Trading statistics | No | YesMetaStats[9] |
| Click-to-trade flow | YesPrepare on view, order on approval | Buildable with deploy and trade calls |
| Close-only API keys | Yestrading:reduce | Not covered in the sources we checked |
| Official SDKs | OpenAPI spec; examples in 13 languages; TypeScript and Python SDKs in progress | JavaScript, Python, Java[4] |
| Regions | EU (Amsterdam) | New York and London; custom regions paid[5] |
| Published performance | Measured: 96–110 ms to a London broker | Median 6 ms execution latency added by their servers[2] |
| SLA | By Enterprise contract | Business plan[1] |
| Manager API for brokers | No | Yes$125 per MT server a month[1] |
What MetaApi does that fxapis does not.
MetaApi is the broader platform. It supports MT4 as well as MT5.[9] Its streaming API pushes prices and account changes over WebSocket, and it serves historical candles and ticks.[3] CopyFactory goes further than fxapis's managed copy trading — portfolios, magic-number filters and Telegram publishing — and MetaStats computes trading statistics.[8] It ships official SDKs in JavaScript, Python and Java,[4] offers New York and London regions,[5] and sells a Manager API for brokers.[1]
If your product depends on any of these, MetaApi deserves a serious look.
What fxapis is built around.
fxapis does fewer things, on purpose. It is built for products that trade other people's MT5 accounts — signal services, copy trading, prop firms, trading apps — and it concentrates on the parts where mistakes cost money.
- Outcomes. An order whose result is unclear is reported as unresolved, with an instruction not to resend, then confirmed against the broker's records. Market orders, pending orders, closes and multi-account orders take an Idempotency-Key; stop changes and cancels are safe to repeat.
- Many accounts. Multi-account orders report every account separately, with a measured dispatch spread — 30 ms across 100 accounts in our benchmark.
- Click-to-trade.
preparebrings a member's account online while they read the signal. See signal providers. - Safety rails. Close-only keys, and closing never blocked for billing.
Concepts, mapped.
| Aspect | In MetaApi | In fxapis |
|---|---|---|
| Add an account | Create a trading account (provisioning API) | POST /v1/accounts |
| Keep it running | Deploy / undeploy | Modes: always_on, warm_on_demand, cold |
| Trade | RPC or streaming connection via SDK | Plain REST: POST …/orders/market |
| Account updates | Streaming synchronisation | Poll positions, deals and status |
| Copy to many accounts | CopyFactory strategies and subscribers | POST /v1/copy/strategies and /v1/copy/subscriptions, or POST /v1/execution-waves |
fxapis vs MetaApi, answered
Is fxapis cheaper than MetaApi?
Usually not on hosting cost alone. MetaApi bills per account per hour while an account is deployed, plus a fee for each deployment, and on its cloud-g2 servers that comes to less than our per-account plan price — both for accounts online around the clock and for accounts started once a day for click-to-trade. fxapis charges a monthly price that includes your first accounts, then a price per account, with opening executions pooled across them. Use the calculator on this page with your own numbers, and check MetaApi's current pricing.
Does fxapis support MT4 like MetaApi does?
No. fxapis is MetaTrader 5 only today. MetaApi supports both MT4 and MT5. If you need MT4, MetaApi or another provider that supports it is the better choice for now.
Does fxapis have streaming market data?
No. fxapis covers trading and account data over REST — orders, positions, deals and margin calculations. MetaApi offers a streaming WebSocket API with prices and account updates, and historical candles and ticks.
What is the fxapis equivalent of deploying an account?
Connection modes. An account can be always connected, on demand — online when you trade and offline again after 15 idle minutes — or manual. You can also bring up to 200 accounts online in one call with POST /v1/accounts/prepare. None of these changes the price.
What is the fxapis equivalent of CopyFactory?
Managed copy trading: mark an account as a strategy, subscribe followers in the same workspace, and fxapis checks the master every second and copies opens, closes, partial closes and stop moves, with sizing, symbol mapping and risk limits. It has no portfolios or Telegram publishing. The multi-account orders it is built on are yours to call if you would rather build your own copier.
How were the MetaApi facts on this page checked?
From MetaApi's own public pricing page, documentation and FAQ, retrieved on 30 September 2026, each linked beside the claim it supports. Prices load dynamically on metaapi.cloud, so they were read from the rendered pricing section in a browser. If something here is out of date, tell us at [email protected] and we will correct it.
Sources, retrieved 30 September 2026
- [1] MetaApi pricing
- [2] MetaApi client FAQ
- [3] MetaApi client API documentation
- [4] MetaApi SDKs
- [5] MetaApi regions
- [6] MetaApi createAccount reference
- [7] MetaApi undeployAccount reference
- [8] CopyFactory documentation
- [9] MetaApi home page
MetaApi is a trademark of its owner. This page is our own comparison, not endorsed by MetaApi. Also see MetaApi alternatives.
Try fxapis on a demo account.
Create a workspace, issue an API key and place your first MT5 order in minutes — then compare for yourself.