Brokers and intermediaries
Explore a future connectivity model only after licensing, flow and operational requirements are reviewed.
A proposed discovery and integration path for eligible professional counterparties. Product scope, liquidity sources, technology and service terms require provider verification and a signed agreement.
Suitability and availability depend on the counterparty, jurisdiction, permissions, volume profile and approved service scope.
Explore a future connectivity model only after licensing, flow and operational requirements are reviewed.
Discuss permitted market access and reporting requirements within an eligibility-led process.
Assess bespoke requirements through legal, compliance and technical discovery before any commitment.
Nothing in this section represents an active liquidity, price or execution guarantee.
Potential instrument scope and venue connectivity will depend on approved providers and jurisdiction.
Account hierarchy, permissions and controls will be designed around agreed operational requirements.
Permitted reports, data fields, delivery methods and retention must be confirmed during discovery.
Support ownership, escalation, maintenance and service expectations belong in the final contract.
Outline entity, mandate, jurisdictions and desired service.
Complete legal, regulatory, AML and counterparty due diligence.
Define connectivity, account, data, security and support requirements.
Proceed only after terms, providers, controls and acceptance criteria are approved.
No liquidity depth, spreads, latency, fill ratio, uptime, supported protocol or execution statistic is published at this stage. All future specifications must be evidence-backed and contract-specific.
Official institutional contact and approved provider scope are still required.