Fair Usage Policy

1. Purpose of This Fair Usage Policy

Certain API2Trade subscription plans are advertised or provided with unlimited MetaTrader account connections and/or unlimited API usage.

“Unlimited” means that API2Trade does not impose a fixed technical account cap as part of the standard subscription and does not automatically stop a customer from connecting additional accounts after reaching a specific number.

Unlimited usage does not, however, mean that a customer may consume unlimited infrastructure resources at a fixed price regardless of the scale, nature, intensity, or technical impact of that usage.

API2Trade operates shared and/or dedicated technical infrastructure with finite computing, memory, network, storage, MetaTrader terminal, WebSocket, database, and third-party infrastructure resources.

This Policy is therefore designed to protect:

• the stability and availability of API2Trade;
• the performance experienced by all API2Trade customers;
• the security and integrity of our infrastructure;
• the commercial sustainability of unlimited subscription plans;
• customers from arbitrary automatic service interruptions;
• API2Trade from unusually resource-intensive or abusive usage.

Our intention is to allow legitimate customers substantial flexibility to grow beyond ordinary usage levels while retaining the ability to address exceptional usage individually.

2. Plans Covered by This Policy

This Policy applies particularly to subscription plans that include unlimited or unrestricted account provisioning, including, where applicable:

• API2Trade PRO – MT4
• API2Trade PRO – MT5
• API2Trade PRO – Both Platforms
• legacy plans containing unlimited account access;
• individually negotiated plans containing unlimited account access;
• successor plans that reference this Fair Usage Policy.

Other subscription plans may also be subject to this Policy where stated in their applicable terms.

3. Meaning of “Unlimited”

Where API2Trade describes a plan as offering “unlimited accounts”, this means:

• there is no predefined hard account limit built into the subscription;
• customers may provision additional accounts without automatically purchasing an additional subscription seat;
• exceeding API2Trade's normal usage assumptions does not automatically result in account suspension;
• usage may exceed the normal usage assumptions described in this Policy;
• there is no automatic overage fee merely because a customer crosses the typical account numbers described below.

The term “unlimited” is subject to reasonable and fair usage.

It does not constitute a commitment by API2Trade to supply unlimited computing power, RAM, CPU capacity, bandwidth, database capacity, WebSocket capacity, storage, MetaTrader terminal instances, broker connections, or other technical resources for a single fixed monthly subscription price under all circumstances.

4. Normal Usage Assumptions

API2Trade's PRO plans are priced based on expected commercial usage patterns observed across ordinary API2Trade customers. For infrastructure planning and Fair Usage purposes, we currently use the following assumptions.

4.1 PRO – Single Platform

For a standard PRO subscription covering either MT4 or MT5, API2Trade assumes an ordinary usage profile of approximately 60 concurrently or regularly connected MetaTrader accounts.

This is an assumption used for capacity planning and pricing purposes. It is not a hard account limit.

A customer may exceed 60 accounts. For example, a customer may operate 70, 80, 100, or more accounts under a PRO subscription without automatically being blocked or charged an additional fee.

Usage exceeding approximately 60 accounts may, however, be subject to review under this Fair Usage Policy.

5. PRO – Both Platforms

For a PRO Both Platforms subscription, covering both MT4 and MT5 infrastructure, API2Trade assumes an ordinary usage profile of approximately 120 concurrently or regularly connected MetaTrader accounts in total.

The 120-account assumption may consist of any commercially reasonable combination of MT4 and MT5 accounts, unless otherwise agreed. For example:

• 60 MT4 + 60 MT5;
• 20 MT4 + 100 MT5;
• 100 MT4 + 20 MT5;
• or another comparable combination.

Again: 120 accounts is not a hard limit. Customers may exceed 120 connected accounts.

Usage above this level does not automatically result in additional charges, suspension, or termination. It may, however, result in a Fair Usage review.

6. Account Numbers Are Guidance, Not Automatic Limits

The account numbers contained in Sections 4 and 5 are intended to establish the usage level on which API2Trade's standard PRO pricing is commercially based.

They are not:

• technical caps;
• automatic billing thresholds;
• automatic suspension thresholds;
• guaranteed infrastructure maximums;
• a prohibition against scaling above those amounts.

API2Trade intentionally allows customers to exceed these assumptions. A customer exceeding 60 or 120 accounts will not necessarily be considered a Heavy User.

Conversely, a customer operating fewer than these account numbers may still be considered a Heavy User where its usage is exceptionally resource-intensive.

Fair Usage is determined based on the overall usage profile, not solely the number of connected accounts.

7. What We Consider When Evaluating Fair Usage

When evaluating whether usage remains commercially reasonable under an unlimited subscription, API2Trade may consider factors including:

• number of connected MetaTrader accounts;
• number of simultaneously active MetaTrader accounts;
• number of MT4 and/or MT5 terminal sessions;
• API request frequency, volume, and peak/average requests per second;
• concurrent HTTP connections;
• number of WebSocket connections and WebSocket message volume;
• account reconnection frequency and repeated authentication attempts;
• historical data requests, frequency of full-history synchronization, and amount of historical data requested;
• repeated polling of identical endpoints;
• CPU usage, memory/RAM consumption, storage usage, and database load;
• network bandwidth and broker server communication;
• number of simultaneously accessed brokers;
• number of simultaneously executed trading operations and order modification frequency;
• trade-copying intensity and synchronization frequency;
• use of automated scripts or bots;
• frequency of provisioning and deleting accounts, and account rotation;
• technical architecture of the customer's application;
• inefficient API implementations, unnecessary duplicate requests, retry loops, and malfunctioning software;
• unusually large bursts of traffic;
• usage that materially affects infrastructure available to other customers.

No single factor necessarily determines whether usage is fair. API2Trade may assess the complete technical and commercial usage profile.

8. Heavy Users

A “Heavy User” is a customer whose usage materially exceeds the ordinary usage profile contemplated by the applicable subscription plan.

A customer may be considered a Heavy User where, for example:

• a PRO customer materially and consistently exceeds approximately 60 active accounts;
• a PRO Both Platforms customer materially and consistently exceeds approximately 120 active accounts;
• infrastructure resource consumption is significantly above that of ordinary customers;
• API request volume is exceptionally high;
• the customer's architecture results in disproportionately high server load;
• the customer uses substantially more infrastructure than is commercially reasonable for the subscription price;
• continued usage at the existing level would require API2Trade to allocate significant additional infrastructure specifically for that customer.

Exceeding the stated account assumptions alone does not automatically mean that a customer is a Heavy User. We may continue allowing substantially greater usage where the technical impact remains reasonable.

9. Unlimited Usage May Exceed the Assumed Usage

API2Trade explicitly permits customers to exceed the normal usage assumptions. A customer should therefore not interpret 60 accounts on PRO, or 120 accounts on PRO Both Platforms, as a maximum permitted number of accounts.

For example, API2Trade may permit a PRO customer to operate considerably more than 60 accounts where those accounts have relatively low resource consumption. Similarly, API2Trade may permit a PRO Both Platforms customer to operate considerably more than 120 accounts.

There is no automatic overage invoice triggered solely by passing those figures.

10. Fair Usage Review

Where API2Trade identifies unusually high usage, we may conduct a Fair Usage Review. A Fair Usage Review may include an assessment of:

• active account numbers and account growth;
• average and peak infrastructure consumption;
• API request patterns and WebSocket usage;
• account activity and expected future usage;
• customer application architecture;
• commercial use case;
• infrastructure required to continue supporting the customer.

API2Trade may contact the customer to better understand the customer's use case before taking action. Where possible, our preferred approach is to work with the customer to identify an appropriate commercial or technical solution rather than immediately limiting service.

11. No Automatic Suspension for Ordinary Heavy Usage

Where usage is legitimate but unusually high, API2Trade will generally not immediately terminate or suspend the customer's service solely because the customer exceeds the normal account assumptions. Instead, API2Trade may contact the customer and discuss one or more of the following:

• technical optimization;
• API usage optimization;
• improved WebSocket usage;
• reduced unnecessary polling;
• infrastructure changes;
• dedicated infrastructure;
• additional server resources;
• a customized commercial plan;
• per-account pricing.

This provision does not apply to abuse, security threats, deliberate attacks, illegal activity, or conduct that creates an immediate risk to API2Trade infrastructure.

12. Right to Transition Heavy Users to Per-Account Pricing

Where a customer's usage substantially exceeds the usage profile contemplated by the applicable PRO subscription, API2Trade reserves the right to require the customer to transition to a per-account commercial model.

The standard Fair Usage rate is €12 per connected MetaTrader account per month, unless another rate is agreed between API2Trade and the customer.

This mechanism is intended for exceptional Heavy Users whose infrastructure requirements are no longer commercially sustainable under a standard fixed-price PRO subscription. API2Trade may propose:

• €12 per account/month;
• a combination of a base subscription fee plus per-account charges;
• a customized volume pricing agreement;
• a dedicated infrastructure agreement;
• another mutually agreed commercial structure.

API2Trade may offer volume discounts at its discretion but is under no obligation to do so unless contractually agreed.

13. Per-Account Pricing Is Not an Automatic Overage Fee

The €12 per-account model does not automatically begin the moment a customer reaches Account 61 or Account 121.

For clarity: a PRO customer reaching 61 accounts will not automatically receive an invoice for 61 × €12. A PRO Both Platforms customer reaching 121 accounts will not automatically receive an invoice for 121 × €12.

The Fair Usage process is based on sustained and material usage. API2Trade will normally first evaluate the customer's overall infrastructure usage. If API2Trade determines that the customer's scale materially exceeds the commercial scope of the standard subscription, API2Trade may contact the customer and require a change in commercial terms for future usage.

14. Notification of Pricing Change

Except in cases involving abuse, fraud, security threats, or immediate infrastructure risks, API2Trade will normally provide notice before requiring a Heavy User to transition to different pricing. The notice may include:

• the reason for the Fair Usage review;
• relevant account numbers;
• relevant usage information;
• the commercial model proposed;
• the date on which the new pricing will apply;
• available alternatives.

The customer may choose to:

• accept the proposed commercial terms;
• reduce usage;
• reduce the number of connected accounts;
• optimize its implementation;
• negotiate an alternative enterprise arrangement;
• discontinue the affected service before the new pricing becomes applicable.

Unless otherwise stated in the applicable agreement, increased Fair Usage charges will generally apply prospectively rather than retrospectively.

15. Connected Accounts

For purposes of this Policy, a “Connected Account” generally means a MetaTrader trading account that is provisioned, authenticated, connected, maintained, or otherwise actively available through API2Trade infrastructure during the applicable billing period.

API2Trade may establish additional technical rules for determining whether an account is considered active or connected.

Attempts to artificially rotate, reconnect, delete, recreate, or otherwise manipulate accounts for the purpose of avoiding applicable usage charges may be treated as circumvention of this Policy.

16. Concurrent vs. Provisioned Accounts

API2Trade may distinguish between:

• accounts provisioned within a customer's system;
• accounts currently authenticated;
• accounts currently connected;
• accounts maintaining an active MetaTrader terminal session;
• accounts actively receiving WebSocket data;
• accounts generating API traffic.

A large number of dormant account records may have a materially different infrastructure impact than the same number of continuously active MetaTrader sessions. API2Trade may take this distinction into account during a Fair Usage Review.

17. API Requests

Unless a specific contractual rate limit has been communicated, API2Trade does not intend to restrict normal legitimate API usage through arbitrary low request quotas. Customers must nevertheless design their applications efficiently. Customers should avoid:

• unnecessary polling;
• polling significantly faster than necessary;
• duplicate requests;
• requesting complete trade history repeatedly where incremental updates are available;
• opening unnecessary simultaneous connections;
• repeatedly authenticating the same account;
• unnecessary provisioning and deprovisioning;
• unnecessary requests to MetaTrader broker servers;
• uncontrolled retry loops.

API2Trade may contact customers whose API implementation causes disproportionate infrastructure load.

18. WebSocket Fair Usage

Where WebSocket functionality is included in a plan, customers may maintain WebSocket connections necessary for legitimate operation of their application.

Unlimited account access does not entitle customers to create an unlimited number of unnecessary or duplicate WebSocket connections. Customers should reuse persistent connections where technically appropriate.

API2Trade may take action where customers:

• repeatedly establish and terminate connections at excessive frequency;
• maintain large numbers of unnecessary duplicate connections;
• create connection storms;
• consume disproportionate WebSocket infrastructure;
• intentionally bypass technical controls;
• use WebSocket infrastructure in a way unrelated to the intended API2Trade service.

19. Historical Data Usage

Historical data retrieval can be significantly more resource-intensive than normal incremental account synchronization.

Customers should avoid repeatedly downloading complete account histories where the same data has already been retrieved.

API2Trade may classify repeated large historical-data synchronization as Heavy Usage where it materially increases infrastructure consumption.

20. Automated Trading and Copy-Trading Systems

API2Trade recognizes that many customers operate:

• automated trading platforms;
• trading journals;
• SaaS platforms;
• account analytics systems;
• portfolio management tools;
• copy-trading systems;
• Expert Advisor integrations;
• trade management systems;
• brokerage-related software;
• prop trading infrastructure.

Such commercial uses are permitted where allowed by the customer's subscription and applicable agreement. High-frequency automated usage may nevertheless be subject to this Fair Usage Policy. The fact that usage is generated automatically does not exempt it from Fair Usage requirements.

21. Commercial Resale and SaaS Usage

Where permitted under the applicable plan, customers may integrate API2Trade into their own commercial SaaS or software product. Unlimited accounts are intended to enable commercial scalability.

However, an unlimited subscription may not be used as a means to resell raw API2Trade infrastructure itself to an unlimited number of unrelated third parties in a manner that effectively replaces API2Trade's own commercial service unless API2Trade has agreed to that arrangement.

Customers must use API2Trade as part of their own bona fide product, application, service, or integration where required by their subscription terms.

22. Account Sharing

Unless specifically authorized by API2Trade, a single PRO subscription may not be shared between multiple unrelated companies, organizations, developers, resellers, or end businesses for the primary purpose of avoiding subscription fees.

A customer may, however, connect accounts belonging to its own users or customers where such B2B, B2B2C, SaaS, trading platform, or similar usage is permitted by the applicable subscription.

23. Prohibited Circumvention

Customers must not attempt to circumvent this Fair Usage Policy by, among other things:

• creating multiple subscriptions to distribute load where done to bypass an agreed restriction;
• constantly rotating accounts;
• manipulating account identifiers;
• deliberately disguising API volume;
• using multiple API keys to bypass technical limits;
• proxying abusive traffic through multiple IP addresses;
• creating duplicate accounts solely to avoid usage monitoring;
• interfering with monitoring systems;
• providing false information regarding usage.

Circumvention may be treated as a material violation of the Terms of Service.

24. Technical Abuse

The following activities are prohibited regardless of account quantity:

• denial-of-service attacks;
• deliberate infrastructure overload;
• penetration testing without authorization;
• exploitation of vulnerabilities;
• unauthorized access attempts;
• credential stuffing;
• abusive automated requests;
• malicious traffic;
• deliberate server exhaustion;
• attempts to disable monitoring or security systems;
• use of API2Trade infrastructure for unlawful activities.

API2Trade may suspend or restrict such activity immediately where necessary to protect its infrastructure or other customers.

25. Malfunctioning Customer Software

Customer software can occasionally create unintended excessive usage due to:

• programming bugs;
• infinite loops;
• aggressive retries;
• failed reconnection logic;
• improperly configured polling intervals;
• duplicate services;
• uncontrolled worker processes.

Where practicable, API2Trade may notify the customer after detecting such activity. However, API2Trade reserves the right to temporarily rate-limit or restrict traffic immediately where necessary to protect infrastructure.

Such temporary protective action does not necessarily mean that the customer's subscription has been terminated.

26. Broker-Side Limitations

API2Trade connects to infrastructure operated by MetaTrader brokers and other third parties. Certain limitations may therefore arise from:

• broker servers;
• MetaQuotes technology;
• trading servers;
• network routing;
• data centers;
• broker rate limits;
• maintenance;
• authentication systems;
• broker-specific restrictions.

The availability of unlimited API2Trade accounts does not guarantee that an external broker will allow unlimited simultaneous sessions, requests, authentication attempts, or operations. API2Trade is not responsible for third-party restrictions outside API2Trade's reasonable control.

API2Trade is an independent service and is not affiliated with, authorized by, or endorsed by MetaQuotes Ltd. “MetaTrader”, “MT4”, and “MT5” are registered trademarks of MetaQuotes Ltd.

27. Infrastructure Scaling

API2Trade may dynamically allocate or change infrastructure used to support customers. This may include:

• additional CPU resources;
• additional RAM;
• additional storage;
• additional application servers;
• dedicated servers;
• isolated infrastructure;
• additional networking capacity;
• distributed account processing.

Where a customer's usage requires substantial dedicated resources beyond the commercial assumptions of a standard PRO subscription, API2Trade may require an Enterprise, Dedicated, or per-account commercial arrangement.

28. Dedicated Infrastructure Does Not Mean Infinite Infrastructure

Where a subscription includes dedicated cloud or server infrastructure, “dedicated” means that designated infrastructure resources are allocated specifically to the customer according to the applicable service description.

Dedicated infrastructure remains subject to physical and technical resource limitations.

A fixed-price dedicated subscription does not constitute an obligation for API2Trade to continuously purchase unlimited additional servers or computing resources at API2Trade's own cost regardless of customer usage.

29. Temporary Traffic Spikes

API2Trade understands that trading applications may experience temporary traffic spikes during:

• major market events;
• news events;
• market opens and closes;
• volatility;
• bulk onboarding;
• broker reconnects;
• server maintenance recovery;
• synchronization events.

Temporary spikes will not ordinarily be considered a Fair Usage violation by themselves. Fair Usage reviews primarily focus on sustained, repetitive, excessive, or materially disproportionate resource consumption.

30. Growth Is Expected

The PRO subscriptions are specifically designed for businesses that expect to grow. API2Trade does not intend to penalize customers merely because their business is successful. Customers are encouraged to scale their platforms.

The purpose of this Policy is to create a reasonable mechanism for situations where a customer's scale eventually becomes sufficiently large that the economics or infrastructure requirements differ materially from those of the standard PRO subscription.

31. Example – PRO Subscription

A company subscribes to API2Trade PRO MT5. The standard commercial assumption is approximately 60 connected accounts. The customer grows to 70 accounts, then 90 accounts, then 110 accounts.

API2Trade may continue providing the same subscription without any additional charge where the customer's infrastructure usage remains technically and commercially reasonable. There is no automatic €12/account surcharge.

If the customer later grows to several hundred continuously active accounts and those accounts consume substantial dedicated infrastructure resources, API2Trade may contact the customer and initiate a Fair Usage Review. API2Trade may then propose moving the customer to a €12 per connected account/month pricing model or another individually negotiated commercial agreement.

32. Example – PRO Both Platforms

A company subscribes to PRO Both Platforms. API2Trade assumes approximately 120 connected accounts across MT4 and MT5. The customer grows to 150 accounts.

This does not automatically violate the Fair Usage Policy. The customer may continue operating under the same subscription.

If the customer's usage later grows substantially beyond the expected usage profile and requires materially greater infrastructure resources, API2Trade may contact the customer and propose alternative pricing.

33. Example – High Account Number but Low Usage

A customer has 150 provisioned accounts on a single-platform PRO subscription, but most accounts are dormant and produce very little API or WebSocket activity.

API2Trade may determine that the customer's usage remains reasonable despite materially exceeding the 60-account assumption. This illustrates why account numbers are guidelines rather than automatic limits.

34. Example – Low Account Number but Excessive Usage

A customer has only 40 connected accounts but sends an exceptionally large number of unnecessary requests every second across those accounts.

The resulting infrastructure consumption may exceed that of customers operating hundreds of normally configured accounts. API2Trade may classify this as Heavy Usage and contact the customer to optimize its implementation or discuss appropriate commercial terms.

35. Example – Temporary Growth Spike

A customer normally operates 55 accounts but temporarily provisions 90 accounts during an onboarding campaign. The account number later returns to ordinary levels.

Such a temporary event would not ordinarily trigger a commercial migration on its own.

36. Enterprise and Custom Agreements

Large customers may contact API2Trade to negotiate custom terms. Custom arrangements may include:

• volume pricing;
• reserved capacity;
• dedicated infrastructure;
• priority technical support;
• customized SLAs;
• customized account allowances;
• customized API usage terms;
• custom WebSocket infrastructure;
• fixed commercial commitments.

Where a written custom agreement conflicts with this Fair Usage Policy, the specific terms of the custom agreement will prevail to the extent of that conflict.

37. Legacy Customers

Customers with legacy plans remain subject to the terms applicable to their respective subscriptions and any grandfathered commercial conditions communicated to them.

Where a legacy plan contains unlimited usage, this Fair Usage Policy may still apply to the technical interpretation of reasonable unlimited usage unless API2Trade has expressly agreed otherwise in writing.

Any specific contractual guarantees provided to an individual customer take precedence over this general Policy.

38. Monitoring

API2Trade may monitor technical usage metrics necessary to:

• operate the service;
• ensure reliability;
• enforce security;
• detect abuse;
• investigate technical incidents;
• conduct capacity planning;
• administer this Fair Usage Policy.

Such monitoring may include infrastructure-level information regarding connections, traffic, resource usage, API calls, account sessions, and system performance. Monitoring will be conducted in accordance with applicable privacy and data protection obligations, as further described in our Privacy Policy.

39. Rate Limiting

API2Trade may implement reasonable temporary technical rate limiting where required to:

• preserve service availability;
• prevent infrastructure failures;
• stop abusive traffic;
• mitigate a software malfunction;
• protect other customers;
• respond to an attack;
• maintain network or server stability.

Temporary protective rate limiting does not alter the general unlimited account nature of an eligible PRO subscription.

40. Immediate Intervention

API2Trade may intervene without advance notice where usage:

• threatens service availability;
• creates a security risk;
• materially affects other customers;
• causes infrastructure instability;
• constitutes an attack;
• violates applicable law;
• appears fraudulent;
• is clearly malicious;
• involves deliberate circumvention of safeguards.

Intervention may include temporary connection limits, request limits, account restrictions, service isolation, or suspension where reasonably necessary.

41. Good-Faith Application

API2Trade intends to apply this Fair Usage Policy reasonably and in good faith. The purpose of the Policy is not to create hidden account limits.

The stated assumptions of approximately 60 accounts for PRO, and approximately 120 accounts for PRO Both Platforms, are intended to explain transparently the commercial usage level underlying the standard subscription price.

Customers may exceed these levels. API2Trade will primarily use this Policy where usage becomes materially disproportionate to the subscription price or creates significant infrastructure requirements.

42. No Guarantee of Identical Resource Consumption

Different MetaTrader accounts can consume substantially different amounts of infrastructure. Resource usage may differ depending on:

• broker;
• trading history size;
• number of open positions;
• number of historical orders;
• symbols;
• frequency of trading;
• synchronization behavior;
• API implementation;
• broker latency;
• WebSocket activity;
• customer polling patterns.

For this reason, API2Trade cannot establish Fair Usage solely by counting accounts.

43. Commercial Sustainability

The unlimited PRO subscription is designed to provide customers with predictable costs and substantial ability to scale. At the same time, it must remain commercially sustainable.

If a single customer consumes infrastructure resources that substantially exceed the resources contemplated by the subscription price, API2Trade is not required to indefinitely absorb the resulting infrastructure costs. In such circumstances, API2Trade may require an appropriate commercial adjustment under this Policy.

44. Changes to Usage Patterns

Customers whose expected usage will materially increase are encouraged to contact API2Trade in advance. Examples include customers planning to increase from:

• dozens to hundreds of accounts;
• hundreds to thousands of accounts;
• low-frequency analytics to high-frequency trading operations;
• occasional API access to continuously active real-time connections.

Advance coordination can help API2Trade provision suitable infrastructure and avoid service disruption.

45. Pricing Discussions

Where API2Trade contacts a Heavy User, the customer and API2Trade may discuss a commercially appropriate solution. Possible arrangements may include:

Option A – Continued PRO Subscription

Where API2Trade determines that the increased usage remains technically and commercially reasonable.

Option B – Optimization

The customer modifies its implementation to reduce unnecessary infrastructure consumption.

Option C – €12 Per Account

The customer transitions to pricing based on connected accounts at a standard rate of €12 per connected account per month.

Option D – Volume Agreement

API2Trade and the customer agree to custom volume pricing.

Option E – Dedicated/Enterprise Infrastructure

Additional infrastructure is provisioned under separately agreed commercial terms.

46. Fair Usage Does Not Create Guaranteed Capacity

Nothing in this Policy constitutes a guarantee that any particular server, broker connection, data center, network path, MetaTrader terminal, or infrastructure resource can technically support an unlimited number of accounts.

Technical capacity depends on the actual workload. API2Trade may scale, distribute, or reconfigure infrastructure as reasonably necessary.

47. Customer Responsibility

Customers are responsible for ensuring that their applications are reasonably designed and operated. Customers should:

• implement appropriate request intervals;
• use WebSockets where appropriate instead of excessive polling;
• implement exponential backoff or similar reasonable retry logic;
• avoid uncontrolled reconnect loops;
• cache data where appropriate;
• avoid repeatedly requesting unchanged information;
• properly close unused connections;
• monitor their own systems for bugs;
• protect API credentials;
• prevent unauthorized third-party use.

48. Unauthorized Credential Sharing

Customers must protect:

• API keys;
• UUIDs;
• authentication credentials;
• account credentials;
• WebSocket credentials.

Usage generated through a customer's valid credentials may be attributed to that customer unless the customer promptly reports unauthorized access. Customers should immediately notify API2Trade at [email protected] if credentials have been compromised.

49. Relationship to Subscription Description

Marketing descriptions such as “Unlimited Accounts”, “Unlimited Requests”, or “Unlimited API Usage” must be interpreted together with this Fair Usage Policy.

Such descriptions mean that API2Trade does not impose ordinary fixed usage quotas designed to prevent legitimate business scaling. They do not eliminate the Fair Usage principles contained in this Policy.

50. Material Changes to This Policy

API2Trade may update this Fair Usage Policy to reflect:

• infrastructure changes;
• new products;
• new technologies;
• changes in misuse patterns;
• operational requirements;
• commercial changes;
• legal requirements.

Where a change materially affects existing customers, API2Trade will provide notice where required by applicable law or contract. Any individually agreed contractual pricing commitments remain governed by their applicable agreement.

51. Questions About Expected Usage

Customers expecting particularly large deployments are encouraged to contact API2Trade before launch. We are happy to discuss anticipated:

• account numbers;
• API volume;
• WebSocket usage;
• infrastructure requirements;
• scaling requirements.

Large-scale usage is not prohibited. Our objective is simply to ensure that the technical and commercial arrangement remains appropriate for both API2Trade and the customer. You can reach us at [email protected].

52. Summary

For clarity, the key principles of this Fair Usage Policy are:

• PRO is built around an assumed ordinary usage of approximately 60 MetaTrader accounts.
• PRO Both Platforms is built around an assumed ordinary usage of approximately 120 MetaTrader accounts.
• These are not hard limits.
• Accounts above those amounts remain permitted.
• There is no automatic overage charge when those numbers are exceeded.
• “Unlimited” means customers can scale beyond these numbers subject to Fair Usage.
• API2Trade evaluates overall infrastructure usage, not simply account count.
• Customers with unusually high but legitimate usage may be contacted by API2Trade.
• API2Trade may ask Heavy Users to optimize their usage or enter into a different commercial arrangement.
• API2Trade reserves the right to require Heavy Users to transition to €12 per connected account per month or another mutually agreed pricing structure.
• Such changes will ordinarily be discussed with the customer before being applied.
• API2Trade reserves the right to immediately protect its infrastructure in cases of abuse, security threats, malicious activity, or serious technical risk.

The objective of this Policy is to provide customers with genuine flexibility to grow while ensuring that exceptionally large infrastructure usage remains fair and commercially sustainable for API2Trade and its customers.