Apex Protocol – An open MCP-based standard for AI agent trading
Apex Protocol is a new open standard that defines how AI agents interact with brokers and exchanges, aiming to become the 'FIX Protocol' for the era of agentic trading.
The Open Standard for Agentic Trading
APEX defines how AI agents communicate with brokers, exchanges, dealers, and other execution venues. One protocol. Realtime state. Autonomous safety. Multi-asset by design.
FIX Protocol connected electronic trading. APEX connects agentic trading.
Protocol Specification
19 mandatory tools across five domains – session, account, orders, market data, and risk – plus a realtime resource model with live state, notifications, and production capability profiles.
Instrument Taxonomy
A universal instrument identifier system. APEX:FX:EURUSD means the same thing at every broker. No more per-broker symbol mapping. One ID scheme for every tradeable instrument.
Conformance Tests
167 executable conformance checks across 4 reference implementations validating protocol conformance – from basic tool smoke tests to transport resilience, schema validation, and production readiness.
Implement once. Every agent connects.
Build an APEX alpha-compatible MCP server and become accessible to agent integrations through a shared protocol surface – without bespoke integrations for each one.
- Reference implementations in TypeScript, Rust, Go, and Java
- HTTP/SSE transport with session replay and notification delivery
- 167-check conformance harness across stdio and transport
- Canonical instrument IDs across all asset classes
- Production profiles: Realtime and Autonomous capability claims
Write once. Trade on any broker.
Use canonical instrument IDs and a unified tool vocabulary. Your agent code targets a shared protocol surface rather than per-provider APIs. Switch providers with far less custom integration work.
- Canonical instrument IDs:
APEX:FX:EURUSD - Realtime state: subscribe to quotes, candles, positions, risk
- Event-driven notifications: fills, rejections, candle closes, kill switch
- Deterministic safety: halt on stale data, broken sequences, risk limits
- Open spec, free to implement: CC-BY 4.0
Layer 1 – Mandatory Baseline
Session, account, orders, market data, risk
Realtime & Autonomous Profiles
Transport, resources, notifications, safety controls
Asset Classes Supported
- FX: Spot FX, CFD FX, rollovers, currency exposure
- CFD: Equities, indices, commodities, corporate actions
- Crypto: Spot, perpetuals, funding rates, margin modes
- Derivatives: Listed options, futures, greeks
- Fixed Income: Bonds, yield, duration
Autonomous Safety
Kill switch, position limits, daily loss caps, stale-data rejection, and sequence-gap detection. The runtime halts autonomy before the model is asked to decide – not after.
Open standard. Vendor-neutral. Community-governed.
The APEX Protocol specification is licensed CC-BY 4.0. Reference implementations are Apache 2.0. Governance is through the Technical Advisory Committee with an open RFC process. Agent developers never pay to use the protocol.
Source: Hacker News
