Geopolitical Commodity Market Intelligence Agent
The global commodity markets (copper, gold, iron ore) are highly susceptible to geopolitical shifts, economic outlooks, and speculative activities. News like Chile's election impacting copper, BRICs vs. West in gold, and China's concerns over iron ore speculation highlight the need for sophisticated intelligence. This challenge involves building an AI-powered market intelligence platform that can ingest diverse geopolitical news, economic indicators, and market sentiment data, then generate actionable insights and risk assessments for specific commodities. The platform should leverage advanced LLMs to synthesize information and an agentic framework to autonomously explore relevant data sources. This solution aims to provide real-time strategic insights for critical infrastructure and supply chain stakeholders, enabling proactive decision-making in volatile markets. By identifying potential supply disruptions, price fluctuations, or regulatory changes driven by global events, it enhances resilience and optimizes procurement strategies. The focus is on robust data orchestration, intelligent analysis, and clear, actionable outputs.
What you are building
The core problem, expected build, and operating context for this challenge.
Develop an AI-driven platform using OpenAI GPT 5.2, BeeAgent, and Dagster to analyze geopolitical events and predict commodity market impacts.
How work is evaluated
The solution will be evaluated on the correctness and relevance of its geopolitical risk assessments for commodities, the robustness of its data pipelines, and the clarity of its generated insights.
Challenge datasets
Public datasets, plus the private datasets you have access to.
What you should walk away with
Develop an agentic system for autonomous data collection and analysis.
Utilize large language models for advanced textual analysis and insight generation.
Assess and mitigate risks in global commodity supply chains.
Design and implement an end-to-end data pipeline for geopolitical and market data.
Orchestrate complex AI workflows using MLOps tools.
Reference links and supporting material
Sample data for 3 tasks
Challenge setup
The solution will be evaluated on the correctness and relevance of its geopolitical risk assessments for commodities, the robustness of its data pipelines, and the clarity of its generated insights.
Challenge input
{'event_description': 'string', 'commodity': 'string', 'date': 'YYYY-MM-DD'}
Agent execution
No agent tool is listed for this challenge.
Evaluated output
{'summary': 'string', 'potential_impact': 'string', 'risk_score': 'float (0-10)'}
- Dagster pipeline runs end-to-end without errors.
- All generated insights adhere to the specified JSON output format.
- Evidence of BeeAgent autonomously retrieving and processing information.
- Relevance Score (Geopolitical) target: 0.8
- Python execution harness
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
No tool records are attached.
Evaluation contract
- Dagster pipeline runs end-to-end without errors.
- All generated insights adhere to the specified JSON output format.
- Evidence of BeeAgent autonomously retrieving and processing information.
Metrics
- Relevance Score (Geopolitical) · Target 0.8
- Insight Actionability · Target 0.75
- Risk Score Accuracy · Target 0.7
- Latency (seconds) · Target 15
Workflow tasks
- Task 1
Input: {'event_description': 'string', 'commodity': 'string', 'date': 'YYYY-MM-DD'}
Output: {'summary': 'string', 'potential_impact': 'string', 'risk_score': 'float (0-10)'}
Execution harness: Python
- Task 2
Input: {'commodity': 'string', 'period': 'string (e.g., '24h', '1w')'}
Output: {'sentiment': 'positive|neutral|negative', 'prediction_direction': 'up|down|stable', 'justification': 'string'}
Execution harness: Python
- Task 3
Input: {'pipeline_name': 'string', 'config': 'dict'}
Output: {'status': 'success|failure', 'error_log': 'string (if failure)'}
Execution harness: Docker
Recipe freeze marker
No recipe freeze time is recorded.