Skip to content
HTHyperTrade

HyperTrade for MetaTrader

Your terminal.
A new perspective.

Connect trading activity to your workspace with a read-only Expert Advisor. Choose the agent that matches your terminal. Your trading authority stays with you.

Made for your platform

Two terminals. One clear view.

MT4 and MT5 use different agent files. Select the package for your terminal, not your broker’s website.

Loading available agent source releases…

Read-only by design

Observe the activity.
Keep the control.

HyperTrade’s agents collect account and trade observations. They do not place, change, or close orders. Activate an installation with a one-time workspace code; never enter your broker password into HyperTrade.

A considered connection

From terminal to workspace.

01

Create the connection

Open Trading accounts, register the correct terminal login and server, and issue a one-time activation code.

02

Download and compile

Download the source ZIP for MT4 or MT5. Follow its included installation instructions, then compile the .mq4 or .mq5 file in the matching MetaEditor. Do not rename a source file to .ex4 or .ex5.

03

Allow the API origin

In MetaTrader, open Tools → Options → Expert Advisors and add your HyperTrade HTTPS API origin to the WebRequest allowlist. Use the origin supplied by your administrator.

04

Activate and verify

Attach one agent to one chart for the account, enter the activation code and API base URL, then inspect the Experts log and account connection health. Test against a demo account before using a new build in production.

Upgrading an existing installation?

Preserve the old installation files and any unsent queue before upgrading. Current packages use account-specific installations and may require a new activation code. Reconcile pending events before retiring an old installation, and do not run duplicate agents for the same account.

What is included in a source package?

Agent source, its transport include file, and installation documentation. Source packages require MetaEditor compilation and terminal testing. A source download is not a certified native binary release.

How do I verify the download?

Compare the ZIP’s SHA-256 hash with the checksum shown on its download card. In Windows PowerShell, run Get-FileHash -Algorithm SHA256 .\downloaded-package.zip. A checksum verifies package integrity; it does not replace terminal testing.

Ready to connect

Give every trade its context.

Your next step is a workspace, an account connection, and a verified terminal installation.