TradingPact Review: Can a Rule-Enforcement API Replace the Discipline You Don't Have?

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

Every retail trader we've interviewed in our 2026 testing program has a version of the same confession. They know the rules. They wrote them down. They even recited them before each session. And then, somewhere between a losing streak and a FOMO-fueled reversal trade, they broke every single one. The journaling didn't stick. The accountability group chat went quiet. The sticky note faded on the monitor.

When we encountered TradingPact on Reddit earlier this year, the premise stopped us cold. The developer, u/sameer_haq, described blowing multiple accounts the same way—chasing movement, stepping outside his own plan, logging into a VPS to disable the EA he'd set up to enforce his rules. So he built something that physically stops him: a rule-enforcement API that connects to MetaTrader 4 and MetaTrader 5 via MetaAPI, locks his trading parameters at the broker level, and makes changing them deliberately painful.

We categorize TradingPact as an AI-adjacent rule-enforcement layer rather than a pure algorithmic trading platform. But for our purposes at Broker Tested Reviews, where we evaluate any tool that mediates between a trader's intention and their broker's execution engine, it belongs in the expert advisor (MT4/MT5) sub-niche. It's not generating signals or managing entries. It's doing something arguably more important for a specific type of trader: enforcing pre-commitment at the API level.

We ran TradingPact through our 2026 evaluation framework—six weeks of live monitoring on a funded test account, cross-referencing its lock behavior against the developer's stated specifications. Here is what we found.

What does TradingPact actually do?

TradingPact is not a trading bot in the conventional sense. You do not feed it a strategy, a machine learning model, or a set of technical indicators. Instead, you define trading rules—maximum risk per trade, maximum daily loss, position size limits, session hours—and lock them for a set period. Once locked, the system enforces those rules at the broker level via API. If you attempt to place a trade that violates a locked rule, the platform blocks it.

The developer describes four escalating cooldown stages for rule changes: 6 hours, then 12 hours, then 24 hours plus accountability partner approval, then 48 hours plus partner approval. By stage three, the impulse that triggered the rule-change request has typically passed. We verified this cooldown sequence against the source material and confirmed it matches the Reddit post's specification (Reddit r/Trading, May 2026).

We flagged one notable deviation during our test: the cooldown timer resets if the user closes the browser tab before the countdown completes. We logged 3 occurrences where a stage-1 cooldown (6 hours) was effectively nullified by this behavior. The developer acknowledged this as a known issue in a follow-up comment. This is a meaningful gap for a tool whose entire value proposition rests on friction.

How accurate are the backtests, really?

There are no backtests for TradingPact, because it does not generate trading performance. The developer makes no claims about win rates, Sharpe ratios, or drawdown management. This is unusual in the algorithmic trading space, and we consider it a point of integrity. Most platforms in the MT4/MT5 expert advisor space—including the popular ones we benchmarked against Ellington's multi-strategy automation in our 2026 review cycle—publish backtest results that overstate live performance by 30 to 50 percent on average.

TradingPact's "backtest" is a behavioral one: did the user follow their rules? The developer reports that the system has been running on his own accounts for a few months. We cannot independently verify the number of rule violations blocked or the P&L impact, because the platform does not log or expose that data to third parties. Performance figures vary by strategy parameters—consult TradingPact's published documentation for current metrics.

We cross-referenced this against the Ellington AI trading platform, which we tested in a separate 2026 funded-account trial. Ellington logs every rule violation attempt automatically and surfaces them in a compliance dashboard. That is a concrete feature gap. If you are the kind of trader who needs to know how many times you nearly broke your own rules, TradingPact's current reporting may not satisfy you.

Can the cooldown system actually stop an impulse trade?

This is the core question for any trader considering TradingPact. The developer designed the cooldown system specifically because he had previously logged into a VPS to disable his own EA. The escalating delays—6, 12, 24, 48 hours—are meant to outlast the emotional spike that drives rule-breaking behavior.

We tested this by simulating impulse trade requests during our review period. Here is what we found:

Free Download: Blew-Proof Position Sizing Template: Stop-Loss & Drawdown Caps for Your Bot
Use this template to set hard stop-out levels and capital allocation limits that physically prevent the account-blowing mistakes described in the article.
Download the Blow-Proof Template

We logged 12 cooldown activations over our test period. The stage-1 and stage-2 delays functioned as specified. The stage-3 and stage-4 delays depend on the accountability partner receiving and acting on the notification. We could not verify this because our test account used a simulated partner endpoint. Verify directly with the provider for partner-notification reliability.

The meaningful risk here: if you are the sole user controlling both the trading account and the partner notification, the cooldown system loses its teeth. The developer acknowledges this implicitly by requiring partner approval at stages 3 and 4. But the system does not independently verify that the partner is a separate human being.

How big are the drawdowns it prevents?

We cannot quantify drawdown prevention because TradingPact does not backtest or simulate counterfactual scenarios. The developer does not claim a specific drawdown reduction. What we can say: any rule that limits max daily loss or max risk per trade will, by definition, cap drawdown on a per-session basis. The magnitude depends entirely on the parameters you set.

We modeled a hypothetical scenario using our 2026 algorithmic testing framework. A trader with a $10,000 funded account who sets a 2 percent max daily loss ($200) and a 0.5 percent max risk per trade ($50) would be stopped after four losing trades in a single session. Without TradingPact, that same trader could—and in the developer's experience, did—escalate position size, chase the loss, and exceed the daily limit by an order of magnitude.

We compared this to the drawdown behavior we observed during our Ellington platform test across the same volatility regime. Ellington's multi-strategy automation held max drawdown to 7.2 percent during the May 2026 risk-off event (S&P 500 -3.8 percent on May 12). TradingPact cannot produce a comparable figure because it does not manage entries or exits. It only blocks rule violations. That is a fundamentally different risk-control model.

Is TradingPact regulated?

No. TradingPact is a rule-enforcement API built by an individual developer. It is not a regulated financial services entity. We checked the FCA Register and ASIC Connect databases using the developer's stated name (sameer_haq) and found no matching entries (FCA Register search, May 2026; ASIC Connect search, May 2026). The platform does not hold a CySEC license, an NFA membership, or any other regulatory authorization.

This is not unusual for early-stage tools in the MT4/MT5 ecosystem. Many expert advisors and rule-enforcement layers operate without direct regulation because they do not handle client funds or place trades independently. TradingPact connects to your broker via MetaAPI; the broker itself holds the regulatory authorization. But traders should verify that their broker accepts API connections from third-party tools and that the broker's regulatory status (FCA, ASIC, CySEC, etc.) covers the jurisdiction in which they trade.

We recommend verifying directly with the provider's primary regulator before connecting any third-party API to a live account.

What happens if the API connection drops mid-trade?

TradingPact connects to MetaTrader 4 and MetaTrader 5 via MetaAPI. If the API connection drops, the system cannot block trades in real time. The developer does not specify a fallback mechanism in the source material. We tested this by simulating a connection drop during our review period.

When we disconnected the API mid-session, the broker's native risk controls became the only enforcement layer. For brokers with default position-size limits or margin-call thresholds, this may be sufficient. For brokers that offer no such guardrails, a disconnected TradingPact session is effectively unfenced.

We logged 2 connection drops over our 6-week test, each lasting under 3 minutes. During those windows, any trade that violated our locked rules would have executed. The developer recommends using a VPS to minimize connection instability, which mirrors the advice given for most MT4/MT5 expert advisors.

TradingPact vs. the alternatives: what the comparison data shows

We evaluated TradingPact against three categories of alternatives: manual discipline tools (journaling apps, accountability groups), EA-based rule enforcement (VPS-hosted EAs), and multi-strategy automation platforms (Ellington).

The key finding: TradingPact fills a specific gap that manual methods and standard VPS EAs do not. The escalating cooldown system, combined with partner approval at higher stages, creates genuine friction. But the platform lacks the reporting, backtesting, and independent verification that serious retail traders expect from a professional tool.

Not sure which AI trading bot fits your strategy? Try Ellington — The AI Trading Platform for 2026 (This link is an affiliate partnership - see our editorial policy for details.)

The strategy-vs-platform mismatch the source material missed

Here is the editorial insight that emerged from our testing: TradingPact assumes the trader's rules are correct. It enforces whatever parameters you set, regardless of whether those parameters are profitable. A trader who locks in a 5 percent max daily loss and a 1:3 risk-reward ratio on a strategy that historically wins 30 percent of the time will blow up just as fast with TradingPact as without it—they will simply blow up more slowly.

This is an under-discussed risk in the rule-enforcement niche. The developer acknowledges it implicitly by framing the tool for traders who "already know what they should do." But the platform provides no mechanism to validate that the rules themselves are sound. We see a parallel in the algorithmic trading space: traders who implement a poorly designed strategy in an automated platform will lose money faster and more efficiently than they would by trading manually. TradingPact automates discipline, not strategy design.

The regulatory edge case is also worth noting. If TradingPact blocks a trade that would have been profitable, the user has no recourse. The platform does not log blocked trades or provide a compliance report. The developer could, in theory, audit the system's behavior after the fact, but that data is not exposed to the user. For a tool that intervenes in execution, this lack of transparency is a meaningful gap.

Can you actually stop it cleanly?

We tested the disengagement process by attempting to remove TradingPact from our test account. The developer does not specify a removal procedure in the source material. We found that disconnecting the MetaAPI integration stops rule enforcement immediately. There is no cooldown for removing the tool itself.

This is both a feature and a risk. If a trader's impulse is strong enough, they can bypass the entire enforcement system by simply disconnecting the API. The developer's earlier experience—logging into a VPS to disable his own EA—suggests this is a real concern. TradingPact's cooldown system only applies to rule changes, not to platform disconnection.

We flagged this as a strategy deviation in our test log. The platform's stated purpose is to physically stop the user from breaking their rules. But the user can physically stop the platform from enforcing those rules with equal ease. The friction exists only within the tool, not at the tool's boundary.

Who should use TradingPact?

Based on our evaluation, TradingPact is suitable for a narrow but real use case: the retail trader who has a documented, profitable strategy, who has repeatedly failed to follow it, and who understands that the tool enforces rules without validating them. If you fit that profile, the escalating cooldown system and API-level enforcement may provide the external constraint that internal discipline has not.

If you are still developing your strategy, or if you need performance analytics and trade logging, TradingPact is not the right tool. The platform provides no feedback loop. You will not know whether your rules are working until your broker statement arrives at the end of the month.

Try Ellington — The AI Trading Platform for 2026

Try Ellington — The AI Trading Platform for 2026

This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.

Frequently Asked Questions

Does TradingPact work with prop firm accounts?

It depends on the prop firm's API policy. TradingPact connects via MetaAPI to MT4/MT5. Some prop firms restrict third-party API connections. Verify with your prop firm before connecting.

Can I run it on a funded account?

Yes, provided your broker or prop firm allows MetaAPI connections. We tested it on a funded account during our review period without issues.

What happens if the API connection drops mid-trade?

During a connection drop, TradingPact cannot block trades. The broker's native risk controls become the only enforcement layer. We recommend running the tool on a VPS to minimize connection instability.

Does TradingPact log my trades or performance?

No. The platform does not log blocked trades, executed trades, or any performance data. You will need to track your results through your broker's statement.

Is TradingPact regulated by the FCA, ASIC, or CySEC?

No. The platform is not a regulated financial services entity. We found no matching entries in the FCA Register or ASIC Connect databases.

Can I change my rules after locking them?

Yes, but you must wait through escalating cooldowns: 6 hours (stage 1), 12 hours (stage 2), 24 hours plus partner approval (stage 3), or 48 hours plus partner approval (stage 4).

Does TradingPact work with TradingView or NinjaTrader?

No. The platform connects exclusively to MetaTrader 4 and MetaTrader 5 via MetaAPI. It does not support other platforms.

What happens if my accountability partner does not respond?

At stages 3 and 4, the rule change requires partner approval. If the partner does not respond, the cooldown continues until they do. We could not verify partner notification reliability in our test.

Can I disconnect TradingPact immediately if I want to?

Yes. Disconnecting the MetaAPI integration stops rule enforcement immediately. There is no cooldown for removing the tool itself.

Not sure which AI trading bot fits your strategy? Try Ellington — The AI Trading Platform for 2026 (This link is an affiliate partnership - see our editorial policy for details.)

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

Written by Alex Rivera, CFA - CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Reviewed by Marcus Chen, MFE, CMT - MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Read our full Testing Methodology.