Rust edition: this page follows the live DeepWiki structure but treats the current Rust crates as implementation authority. Non-Rust surfaces are identified at their boundary and are not presented as Rust APIs.
Cryptocurrency Exchange Adapters
Scope decision
This Rust reference deliberately limits venue integration coverage to two adapters:
nautilus-databentoundercrates/adapters/databentofor historical and live market data.nautilus-interactive-brokersundercrates/adapters/interactive_brokersfor brokerage market data and execution.
The adapter family described by the original DeepWiki page is not part of this edition. Its venue-specific clients, authentication rules, schemas, and execution behavior are therefore not presented as dependencies or supported Anthera integration paths.
Reusable Rust boundary
The excluded adapters use the same underlying Nautilus contracts documented in Adapter Framework: provider-specific clients translate external messages into nautilus-model values, register through data or execution client factories, and are composed by a live node. The selected Databento and Interactive Brokers pages demonstrate those contracts without expanding the dependency surface.
Where to continue
- Use Traditional Broker Adapters for the Interactive Brokers implementation.
- Use Data Provider Adapters for the Databento implementation.
- Use Creating Custom Adapters only when a new provider has an accepted requirement.