234 incidents on record · 2026HeadlightsIncident reports by Ellie Harris · Melbourne
5 new this weekLibrary last updated 14 October 2026
← The incident library
HD-INC-211
Fuel retail · Brazil · 2026 · A pricing tool sold to competing fuel stations drew on their competitors' prices and was marketed with messages urging clients not to cut prices, prompting a competition case over possible algorithmic collusion

A Fuel Price Software Maker Settled With Brazil's Competition Authority Over Its Algorithm

By Ellie Harris · Filed Software in use by fuel stations in Brazil; CADE became aware of it and its marketing in January 2021 and opened an administrative case on 19 November 2024

Alleged: Intelprice Soluções de Precificação (Aprix) developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

A Fuel Price Software Maker Settled With Brazil's Competition Authority Over Its Algorithm

What happened

Brazil’s competition authority, CADE, opened an administrative case on 19 November 2024 into Aprix, pricing software sold to fuel stations by Intelprice Soluções de Precificação. According to CADE’s final report, the question was whether the software, and a recommendation to use it, could encourage competing stations to adopt uniform prices.

According to CADE’s economists, the software watched competitors’ public prices, combined them with information from the client, and recommended prices designed to maximise that client’s profit. CADE’s President described Intelprice as specialising in pricing based on artificial intelligence.

CADE’s final report quotes one of the company’s marketing messages: “baixar preço quase nunca vale a pena. Resista!” (cutting prices is almost never worth it. Resist!). The report says the marketing suggested a possible push towards uniform conduct.

On 8 April 2026 CADE’s Tribunal approved a settlement with Intelprice unanimously, according to the session certificate. Intelprice paid 70,803.40 reais. On 2 September 2026 the Tribunal closed the case against Minaspetro, a fuel retailers’ union in Minas Gerais, for insufficient evidence, and suspended the case against Intelprice pending compliance.

What an auditable version would have shown

CADE’s economists estimated statistically significant price rises after stations signed with Aprix: 0.02 to 0.03 reais a litre for petrol and ethanol and 0.01 to 0.04 reais for diesel. There was no significant effect for compressed natural gas. Their study said higher average prices did not on their own show that the software caused them.

Under the settlement, the company admitted the facts set out in a restricted history of the conduct, which the settlement heads as an acknowledgement of participation in the conduct. That history is not public. The rapporteur’s vote of September 2026 describes the acknowledgement as one of potential competitive risks. No finding of collusion has been made against any party.

According to CADE, Intelprice also supplied extracts of its source code and explanations of how its rules worked. An auditable system would make it possible to trace whose data went in, what price was recommended and which client received it.

Where the gap was

According to CADE, the same vendor was providing pricing recommendations to businesses competing with each other.

The settlement requires Intelprice to separate each client’s price and strategy data and use confidentiality clauses so sensitive information is not shared between competitors. It must not require clients to follow its suggested prices. Its compliance programme must also cover the language used in its marketing.

An EgressGate is designed to check whether data leaving a system is sensitive and whether its destination is permitted, before it leaves.

A ConductRecord keeps each recommendation, the data it drew on and the client it went to.

EgressGate and ConductRecord are Headlights designs.

What governance should have looked like

Under the settlement, CADE can inspect Intelprice’s premises and pricing system on notice and require an independent audit of its compliance measures. Intelprice must also tell CADE when its clients reach 20 percent of the market in a municipality.

Where one pricing tool serves competing businesses, best practice would be to separate each client’s data and keep a clear record of what the tool recommended and to whom.

That gives a regulator something concrete to inspect: what information went into a recommendation, where it went and whether one client’s information reached another.

Failure Pattern: according to Brazil’s competition authority, a pricing tool sold to competing fuel stations drew on their competitors’ prices and was marketed with messages urging clients not to cut prices, and its maker settled over possible coordination without any finding of collusion.

Governance Principle: a vendor whose pricing tool serves competing businesses should be able to show whose data fed each recommendation, what it recommended to whom, and that one client’s data did not reach another.

The reference implementation of EgressGate and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

Sent through Substack. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Intelprice Soluções de Precificação (Aprix) could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

Last reviewed September 2026. This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →