Skip to content
Sprint projectOct 26, 2026Warwick, UK

Do LLM Bidders Collude? A Sealed-Bid Procurement Sting

Rohit John

Submitted to AI Collusion Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Do LLM Bidders Collude? A Sealed-Bid Procurement Sting

Code (opens in new tab)
Share

We demonstrate spontaneous collusion in market environment,occurring with and without direct communication channels, implement and compare several collusion detection & deterrence methods and test collusion stability after agent replacement.

Reviews

Judging this Sprint?

Review “Do LLM Bidders Collude? A Sealed-Bid Procurement Sting”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

Only the Apart team reads this, and funders if you agree below.

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

  1. This project builds a repeated sealed-bid procurement tender with three LLM firms and public, private and ring communication channels, then measures how warnings, monitoring and replacing a participant affect overpayment. The setting is well chosen, since bid rigging is a concrete harm with established audit practice, and the paired batch with shared seeds is a sound way to compare interventions. The finding that an overseer reading all messages reduced the cartel while one reading only public chat did not is a useful result for anyone designing monitoring.

    Several results depend on modelling choices that the report should discuss more directly. Firms do not see chat from earlier jobs, so any agreement must be renegotiated each job or held in the prompt. This probably limits spontaneous cartel formation and explains why rings persist only when written into members’ prompts. The replacement experiment was run on instructed rings, so the finding that an uninformed newcomer competes immediately follows largely from the design. Running it on spontaneous cartels, which the report notes did not launch, would be the informative version.

    The interventions are hard to separate from wording effects. The talk cue, which tells firms their messages are part of their strategy, is a nudge toward coordination, so describing the resulting cartels as spontaneous overstates the case; the no-cue control (index 0.11) is the cleaner measure. The legal warning names collusion explicitly, which may trigger the model’s safety training rather than an assessment of risk. It is also unclear whether the overseer takes any action beyond its announcement. If it does not, the overseer conditions test announcement wording rather than monitoring capability. Reporting absolute differences alongside percentage changes would help, because a 173% increase from a base of 0.11 is an absolute change of 0.19.

    The Discussion cites results that are not shown. It states that an instructed ring keeps prices near the cap without chat and with bids hidden, citing Section 4.5, but that section covers the detector, and it refers to a Section 4.7 that does not exist. The scripted proposer and trusted firm are described in the Methods but their results are not reported, so the sting promised in the title is largely missing. The project-page summary says collusion occurred with and without direct communication, which contradicts the report’s finding that no cartel formed without chat. The Methods average over jobs after the first, while Figure 2 averages over jobs 4 and later. The detector relies on keyword rules that were not checked against hand-labelled examples, so its error rate is unknown. Related work should include Agrawal et al. (2025), and the introduction has several grammatical errors.

    Read full reviewShow less

Cite this project

@misc{john2026llm,
  title = {{Do LLM Bidders Collude? A Sealed-Bid Procurement Sting}},
  author = {Rohit John},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/do-llm-bidders-collude-a-sealedbid-procurement-sting-vw7b}},
  url = {https://apartresearch.com/sprints/projects/do-llm-bidders-collude-a-sealedbid-procurement-sting-vw7b}
}