Skip to main content
Loading navigation
Back to challenges

Multi-Agent Crude Allocation & Tender Bidding System using Microsoft AutoGen

Managing crude oil allocation between state marketing directives, local refiners, and international trading houses requires dynamic multi-turn negotiations. Build a multi-agent bidding and quota allocation system using Microsoft AutoGen. The system consists of three conversing agents: SOMO Quota Manager, International Trader Representative, and Local Refinery Liaison. The agents converse autonomously to clear spot cargo pricing differentials and confirm allocation schedules based on the approved 3-month mechanism.

Business OperationsHosted by Vera
Sign in free to start

What you are building

Develop an autonomous multi-agent crude allocation and tender negotiation graph using Microsoft AutoGen.

How work is evaluated

Evaluation

Evaluates outcome consensus and constraint compliance in multi-agent tender negotiations.

Datasets

Public datasets, plus the private datasets you have access to.

How submissions are scored

Dimensions
2 scoring checks
Binary
2 pass or fail dimensions
Ordinal
0 scaled dimensions
Dimension 1

agreement_validity

Ensure agreement is reached and highest valid premium wins.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Dimension 2

negotiation_efficiency

Number of conversation turns required to reach consensus. • target: 4 • range: 1-10

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

  • Orchestrate multi-agent group chats using Microsoft AutoGen framework.

  • Define distinct system messages and negotiation strategies per agent persona.

  • Implement conversation termination conditions based on agreement consensus.

Resources

Dataset notes

Simulated oil export tender parameters and trader willingness-to-pay profiles.

Challenge setup

Evaluates outcome consensus and constraint compliance in multi-agent tender negotiations.

Challenge input

JSON containing cargo_volume, base_osp_differential, bidder_profiles

AutoGen

Microsoft's multi-agent framework for collaborative task execution.

Evaluated output

JSON with winning_bidder, final_price_differential, agreement_reached

Evaluation checks
  • Ensure agreement is reached and highest valid premium wins.
  • Number of conversation turns required to reach consensus. • target: 4 • range: 1-10
Configured evaluation evidence
  • Benchmark: AutoGen-Market-Bench
  • Negotiation Efficiency target: 4
  • 1 public reference case
Configured runtime
  • Python execution harness
  • Python sandbox (unavailable on Versalist)

Shows the first task, up to three tools, and up to three evidence items.

View technical recipe

Configured tools

Action Space
  • AutoGen · Required
  • Microsoft AutoGen · Optional
  • AutoGluon · Optional

Evaluation contract

  • agreement_validity · Weight 1
  • negotiation_efficiency · Weight 1

Metrics

  • negotiation_efficiency · Target 4

Benchmarks

  • AutoGen-Market-Bench
  • energy

Reference cases

  • 1 public reference case

Workflow tasks

  1. Task 1

    Input: JSON containing cargo_volume, base_osp_differential, bidder_profiles

    Output: JSON with winning_bidder, final_price_differential, agreement_reached

    Execution harness: Python

Evaluation tools

  • AutoGen · Multi-Agent Conversation Engine

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Multi-Agent Crude Allocation & Tender Bidding System using Microsoft AutoGen