Algorithmic Liquidity Providers and Exchange Control Risks

Introduction

Algorithmic liquidity providers are firms, trading systems, market makers, exchanges, or automated agents that use algorithms to continuously quote buy and sell prices, manage inventories, route orders, adjust spreads, and respond to market conditions. They are particularly important in securities, commodities, foreign exchange, crypto-assets, and other electronic markets.

The competition-law concern arises when an algorithmic liquidity provider becomes sufficiently important that it can influence access to trading infrastructure, determine which orders receive liquidity, disadvantage rival venues, exchange data providers, brokers or traders, or coordinate pricing through automated systems.

The expression “exchange control risks” can therefore cover several related risks:

1. control over access to an exchange or trading venue;
2. discriminatory order routing;
3. exclusionary liquidity provision;
4. algorithmic coordination between competing liquidity providers;
5. manipulation of benchmark or reference prices;
6. preferential treatment of affiliated traders;
7. control over market data and order-book information;
8. interoperability restrictions;
9. discriminatory fee/rebate structures;
10. leveraging liquidity dominance into adjacent markets.

A crucial distinction is that algorithmic trading itself is not unlawful. The legal problem arises from the conduct, market power, coordination, discriminatory access, manipulation, or exclusionary effects associated with the algorithmic system.

I. Meaning of Algorithmic Liquidity Providers

An algorithmic liquidity provider generally performs some or all of the following functions:

1. Continuous quotation

The system automatically posts bids and offers and modifies them according to:

• market volatility;
• order-book depth;
• inventory;
• competitor prices;
• transaction costs;
• latency;
• expected order flow.

2. Automated inventory management

Algorithms determine when to acquire or dispose of securities or other assets so that the provider maintains an acceptable inventory exposure.

3. Smart order routing

Orders may be automatically directed among different exchanges or trading venues according to:

• price;
• execution probability;
• transaction fees;
• liquidity;
• latency;
• rebates.

4. Liquidity aggregation

An algorithm may aggregate liquidity from multiple exchanges and display or execute against the aggregated order book.

5. Dynamic pricing

The system may alter spreads and prices within milliseconds.

This creates a distinctive competition-law issue: the economically significant decision may be made by software rather than by a human trader.

II. Why Exchange Control Creates Competition Risks

An exchange or trading platform may possess a structurally important position because traders require access to:

• the order book;
• matching infrastructure;
• clearing;
• settlement;
• market data;
• connectivity;
• liquidity;
• benchmark prices.

If a dominant liquidity provider is vertically integrated with the exchange, it may have incentives to favour its own trading activities.

For example:

Exchange → owns market-data infrastructure → operates matching system → provides liquidity → operates affiliated trading desk.

This structure can create conflicts between neutral venue operation and commercial trading interests.

III. Principal Competition-Law Risks

1. Discriminatory Exchange Access

An exchange may provide different technical or commercial conditions to competing liquidity providers.

Examples include:

• unequal access fees;
• different latency;
• preferential connectivity;
• discriminatory API access;
• priority order processing;
• superior market-data feeds.

Where the exchange has significant market power, discriminatory access may raise abuse-of-dominance concerns.

2. Preferential Order Routing

An algorithm could systematically route orders toward an affiliated liquidity provider rather than an independent competitor.

The legal inquiry would involve:

1. whether the venue or intermediary has market power;
2. whether competing liquidity providers are foreclosed;
3. whether the routing preference is objectively justified;
4. whether consumers or traders suffer competitive harm.

IV. Algorithmic Liquidity and Tacit Coordination

One of the most difficult issues is algorithmic coordination.

Suppose several competing market makers use algorithms that:

• observe the same market information;
• react rapidly to competitors' prices;
• continuously adjust spreads;
• avoid aggressive undercutting;
• maintain similar pricing levels.

The resulting prices may become highly parallel without a conventional agreement.

Important distinction

Parallel algorithmic behaviour is not automatically collusion.

Competition law generally requires additional evidence before treating coordinated conduct as an unlawful agreement or concerted practice.

Relevant evidence may include:

• communication between firms;
• common algorithmic instructions;
• shared pricing rules;
• explicit coordination;
• algorithm providers facilitating coordination;
• deliberate exchange of competitively sensitive information.

V. Algorithmic Hub-and-Spoke Risks

A particularly important model is hub-and-spoke coordination.

Example:

Multiple liquidity providers → common algorithmic intermediary → common pricing parameters → competing exchanges/traders.

The intermediary may function as the "hub," while competing providers constitute the "spokes."

Potential concerns include:

• exchange of competitively sensitive information;
• coordinated pricing;
• common minimum spreads;
• common inventory strategies;
• restrictions on independent pricing.

The central legal question is whether the algorithm merely provides a neutral technological service or facilitates coordination among competitors.

VI. Market-Data Dependency

Liquidity providers depend heavily on information.

Important inputs include:

• real-time quotes;
• historical prices;
• order-book depth;
• transaction data;
• latency information;
• trading volumes;
• benchmark data.

An exchange controlling essential market data may potentially disadvantage competing venues or liquidity providers by:

• refusing access;
• charging discriminatory prices;
• delaying data;
• providing superior data to affiliates;
• bundling data with other services.

This brings the issue close to essential-facility and access-to-input theories.

VII. Exchange Self-Preferencing

Where an exchange operates its own liquidity-provision business, it may potentially favour that business.

Possible mechanisms include:

A. Faster access

The affiliated liquidity provider receives information earlier.

B. Better order priority

Orders belonging to the affiliated entity receive preferential treatment.

C. Lower fees

The affiliate receives rebates or lower trading costs.

D. Better data

The affiliate receives more detailed or faster market information.

E. Technical discrimination

Independent providers face inferior APIs, connectivity, or execution conditions.

The competition-law assessment depends on market structure and evidence rather than merely on the existence of vertical integration.

VIII. Predatory or Exclusionary Liquidity Provision

A dominant provider could theoretically use liquidity strategically to exclude rivals.

Possible conduct includes:

• sustained below-cost pricing where applicable;
• artificial liquidity;
• targeted rebates;
• discriminatory spreads;
• temporary aggressive pricing designed to eliminate a competitor;
• refusal to provide liquidity to competing venues.

However, aggressive competition that benefits traders is not necessarily unlawful.

The authority must distinguish:

pro-competitive liquidity competition

from

strategic exclusionary conduct.

IX. Market Manipulation and Competition Law

Algorithmic liquidity systems can also interact with market-abuse rules.

Examples include:

• spoofing;
• layering;
• wash trading;
• quote stuffing;
• momentum ignition;
• benchmark manipulation.

These may principally be addressed under securities or market-abuse legislation rather than competition law.

Nevertheless, the same conduct can sometimes create competition-law implications where it:

• excludes competitors;
• manipulates market access;
• creates artificial barriers;
• facilitates collusion.

Thus, market-abuse law and competition law may operate concurrently but pursue different objectives.

X. Relevant Case Laws

The following cases are especially useful for developing the legal principles applicable to algorithmic liquidity providers and exchange-control risks.

1. United States v. Socony-Vacuum Oil Co., 310 U.S. 150 (1940)

Principle

The U.S. Supreme Court treated concerted price stabilization among competitors as a serious antitrust problem.

Relevance

Although the case predates algorithmic trading, its fundamental principle remains relevant to automated pricing systems.

If competing liquidity providers deliberately use algorithms to implement a common pricing arrangement, the fact that software executes the arrangement does not necessarily remove the conduct from antitrust scrutiny.

Application

Algorithmic implementation should not be treated as a legal shield where there is evidence of human-directed coordination.

2. United States v. Apple Inc., 791 F.3d 290 (2d Cir. 2015)

Principle

The case demonstrates that sophisticated technological or contractual mechanisms can constitute a means through which competitors coordinate market conduct.

Relevance

The significance for algorithmic markets lies in the distinction between:

• independent technological decision-making; and
• technology deliberately structured to facilitate coordination.

Application

An algorithmic intermediary can therefore become relevant to antitrust analysis when it is intentionally used to align competitors' commercial behaviour.

3. United States v. American Airlines, Inc., 743 F.2d 1114 (5th Cir. 1984)

Principle

The case concerned alleged coordination involving airline pricing and competitive conduct.

Relevance

It is useful by analogy for algorithmic markets because modern airline and financial markets increasingly use automated pricing systems.

The legal issue remains whether independent responses to market conditions are distinguishable from coordinated conduct.

Application

Identical or parallel algorithmic outputs alone should not automatically establish an unlawful agreement.

4. United States v. Terminal Railroad Association of St. Louis, 224 U.S. 383 (1912)

Principle

The Supreme Court addressed control over an essential transportation facility and discriminatory exclusion of competitors.

Relevance to exchanges

A major exchange can possess characteristics resembling a critical infrastructure platform where market participants require access to:

• matching infrastructure;
• order books;
• clearing arrangements;
• connectivity.

Application

Where a dominant trading infrastructure controls access and excludes rivals without legitimate justification, essential-facility principles may become relevant, subject to the applicable jurisdiction's demanding requirements.

5. Lorain Journal Co. v. United States, 342 U.S. 143 (1951)

Principle

A dominant enterprise could not use its market position to exclude competitors through discriminatory dealing.

Relevance

The case is useful for analysing an exchange or dominant liquidity platform that selectively deals with market participants.

Application

An algorithmic system could theoretically operationalize discriminatory conduct by automatically:

• denying access;
• imposing discriminatory terms;
• steering transactions;
• disadvantaging rival liquidity providers.

The technological form does not necessarily change the underlying economic conduct.

6. Aspen Skiing Co. v. Aspen Highlands Skiing Corp., 472 U.S. 585 (1985)

Principle

The Supreme Court examined exclusionary conduct involving termination of a previously beneficial cooperative arrangement.

Relevance

The case is frequently discussed in relation to refusal-to-deal doctrine.

Application to exchanges

Where an exchange or dominant liquidity provider historically cooperated with another trading venue or liquidity provider and subsequently withdraws access for exclusionary reasons, the factual circumstances may become relevant.

The case does not establish a general obligation for every dominant firm to deal with competitors.

7. MCI Communications Corp. v. AT&T, 708 F.2d 1081 (7th Cir. 1983)

Principle

The Seventh Circuit developed important considerations concerning refusal to deal and essential facilities.

Relevance

The case is particularly useful for analysing access to infrastructure.

Application

For algorithmic exchanges, questions may include:

• Is the trading infrastructure practically indispensable?
• Can a competitor reasonably duplicate it?
• Is access technically feasible?
• Does denial of access substantially impair competition?
• Is there a legitimate business justification?

8. FTC v. Qualcomm Inc., 969 F.3d 974 (9th Cir. 2020)

Principle

The Ninth Circuit addressed complex technology-market conduct involving licensing, supply relationships and competitive effects.

Relevance

The case demonstrates the difficulty of applying antitrust principles to technologically complex, vertically integrated markets.

Application

Exchange-control cases may similarly require separation of:

• legitimate vertical integration;
• contractual restrictions;
• exclusionary conduct;
• effects on downstream competitors.

XI. European Competition-Law Cases of Particular Relevance

9. Bronner v. Mediaprint, C-7/97

Principle

The Court of Justice established a demanding framework for refusal-to-supply claims under Article 102 TFEU.

Relevance

It is highly relevant where a trading venue or liquidity infrastructure is alleged to be indispensable.

The Court emphasized factors including whether access is indispensable and whether duplication is realistically possible.

Application

A competing liquidity provider cannot simply characterize every important exchange as an "essential facility."

10. IMS Health GmbH & Co. OHG v Commission, C-418/01

Principle

The CJEU developed important principles concerning compulsory access to intellectual-property-related infrastructure.

Relevance

The case is useful for exchange systems involving proprietary:

• APIs;
• market-data architecture;
• trading interfaces;
• database structures.

Application

Compulsory access requires careful examination of indispensability and competitive effects.

11. Slovak Telekom a.s. v Commission, Joined Cases C-152/19 P and C-165/19 P

Principle

The CJEU considered exclusionary conduct involving access to infrastructure controlled by a dominant undertaking.

Relevance

The case is useful by analogy for dominant digital or financial infrastructure.

Application

Where a dominant exchange controls infrastructure required by competitors, discriminatory or restrictive access conditions may attract Article 102 scrutiny.

12. Deutsche Telekom AG v Commission, C-280/08 P

Principle

The CJEU upheld principles concerning margin squeeze and exclusionary conduct by a vertically integrated dominant undertaking.

Relevance to exchanges

A vertically integrated exchange could theoretically operate:

upstream trading infrastructure + downstream liquidity provision.

If the terms imposed on rival liquidity providers prevent them from competing effectively downstream, margin-squeeze reasoning may become relevant.

XII. Legal Issues Specific to Algorithmic Liquidity Providers

XIII. Attribution of Liability

A particularly difficult issue is who is legally responsible for an algorithm's conduct.

Potentially relevant actors include:

1. the exchange;
2. the liquidity provider;
3. the algorithm developer;
4. the data provider;
5. the broker;
6. the investment firm;
7. the parent company;
8. an intermediary operating a common algorithm.

The central question is whether the algorithm merely executes independent instructions or whether the underlying undertaking designed, instructed, knowingly adopted, or facilitated the problematic conduct.

XIV. Evidence in Algorithmic Exchange Cases

Competition authorities may need to examine evidence that is substantially different from traditional cartel cases.

Important evidence can include:

1. Source code

Algorithms may reveal:

• pricing rules;
• competitor-response mechanisms;
• minimum spreads;
• order-routing instructions.

2. Version histories

Changes to the algorithm can reveal when potentially problematic conduct was introduced.

3. Communications

Relevant material may include:

• emails;
• messaging applications;
• developer instructions;
• trader communications;
• meeting records.

4. Logs

High-frequency trading produces extensive logs showing:

• orders;
• cancellations;
• execution times;
• routing decisions;
• price changes.

5. API records

API access records may demonstrate discriminatory treatment.

6. Market-data records

Investigators may compare the information available to:

• affiliated traders;
• independent liquidity providers;
• competing venues.

XV. Algorithmic Transparency and Competition Law

Complete disclosure of source code is not necessarily required in every investigation.

A regulator may instead seek:

• algorithmic documentation;
• decision logs;
• parameter histories;
• audit trails;
• model governance documents;
• testing records;
• human-override procedures.

This creates an important regulatory principle:

Accountability may require explainability of the commercial decision even where disclosure of the entire algorithm is unnecessary.

XVI. Exchange Dependency and Network Effects

Exchange markets often exhibit strong network effects.

More traders → more liquidity → better execution → more traders.

This can create a self-reinforcing structure:

More liquidity

↓

More traders

↓

More transactions

↓

More market data

↓

Better algorithmic pricing

↓

More liquidity

This feedback loop can make entry difficult for competing exchanges.

Competition law therefore needs to distinguish between:

• legitimate liquidity-driven network effects; and
• artificial barriers created by exclusionary conduct.

XVII. Regulatory Overlap

Algorithmic liquidity providers can fall simultaneously within several regulatory frameworks:

Competition law

Addresses:

• collusion;
• abuse of dominance;
• exclusion;
• discriminatory access;
• foreclosure.

Securities/market-abuse law

Addresses:

• manipulation;
• spoofing;
• false markets;
• benchmark manipulation.

Financial-market regulation

Addresses:

• algorithmic trading controls;
• risk management;
• system resilience;
• supervision.

Data law

May address:

• market-data processing;
• privacy;
• portability;
• access rights.

Contract law

May address:

• exchange membership;
• API restrictions;
• trading agreements;
• data licensing.

XVIII. Compliance Framework for Algorithmic Liquidity Providers

A robust compliance programme should include:

A. Independent algorithm governance

Algorithms should have identifiable owners and documented purposes.

B. Competition-law testing

Before deployment, firms should examine whether algorithms could:

• coordinate prices;
• discriminate against rivals;
• exchange sensitive information;
• facilitate exclusion.

C. Parameter controls

Parameters capable of producing coordinated outcomes should receive heightened scrutiny.

D. Audit trails

Material algorithmic decisions should be reconstructable.

E. Change management

Material algorithm changes should be documented and approved.

F. Conflict-of-interest controls

An exchange operating its own liquidity provider should maintain safeguards against preferential treatment.

G. Equal-access controls

Comparable market participants should receive objectively justified and consistently applied access conditions.

XIX. Hypothetical Example

Assume Exchange X operates the dominant electronic market for a particular asset.

It also owns LiquidityCo, an algorithmic market maker.

LiquidityCo receives:

• order-book information 100 microseconds earlier;
• lower exchange fees;
• superior API connectivity;
• additional order-flow information.

Independent market makers subsequently experience lower execution quality and withdraw from the exchange.

Competition-law questions

1. Does Exchange X possess market power?
2. Is the relevant market the exchange market, liquidity market, or both?
3. Does the preferential treatment disadvantage competing liquidity providers?
4. Is the conduct objectively justified?
5. Does it substantially foreclose competition?
6. Does the conduct benefit Exchange X's affiliated trading business?
7. Are the advantages commercially legitimate or artificially created?
8. Does market-data control reinforce the exclusion?
9. Are traders harmed through reduced competition or higher execution costs?
10. Are financial-market rules also violated?

The fact that the preferential treatment is implemented automatically would not, by itself, eliminate competition-law scrutiny.

XX. Key Doctrinal Synthesis

The cases collectively provide several principles applicable to algorithmic liquidity and exchange-control disputes:

Principle 1 — Technology does not immunize anticompetitive conduct

An unlawful arrangement does not become lawful merely because software executes it.

Principle 2 — Parallel algorithmic behaviour requires careful analysis

Similar prices or trading strategies can result from independent optimization.

Additional evidence may be required to establish coordination.

Principle 3 — Infrastructure control can create competition concerns

Where a dominant undertaking controls indispensable infrastructure, access restrictions may require scrutiny.

Principle 4 — Vertical integration matters

An exchange that also operates a liquidity provider may create incentives for self-preferencing.

Principle 5 — Essential-facility doctrine is exceptional

Bronner and related cases demonstrate that indispensability is a demanding requirement.

Principle 6 — Evidence must follow the technology

Traditional documents may need to be supplemented by:

• source code;
• logs;
• APIs;
• algorithmic parameters;
• version histories;
• data-access records.

Conclusion

Algorithmic liquidity providers create a distinctive intersection between competition law, exchange regulation, market-abuse law and technology governance. The central legal concern is not the mere use of algorithms, high-frequency trading, or automated liquidity provision. Rather, it is whether technological systems are used to coordinate competitors, discriminate in access to trading infrastructure, favour affiliated businesses, control essential market data, foreclose competing venues, or otherwise exploit market power.

The most useful case-law foundations include Socony-Vacuum, Terminal Railroad, Lorain Journal, Aspen Skiing, MCI Communications, Qualcomm, Bronner, IMS Health, Slovak Telekom and Deutsche Telekom. These cases do not specifically establish a single doctrine called “algorithmic liquidity provider liability”; instead, they provide established principles concerning price coordination, infrastructure access, refusal to deal, vertical exclusion, discriminatory treatment and technologically complex markets that can be applied to modern algorithmic exchange structures.