Resolve the intended instrument
Maintain canonical definitions rather than relying on display symbols alone.
WHY IT MATTERS
Correct decisions start with correct identity.
Keep mappings consistent
Connect market-data symbols with the relevant venue and contract.
Respect coverage boundaries
Validate reference-data imports and make phased scope explicit.
THE OPERATING MODEL
What happens, and in what order.
Import
Bring reference data through validated import workflows.
Identify
Maintain the canonical instrument and contract.
Map
Associate venue and market-data symbol definitions.
Use
Carry the identity into testing and eligible operation.
MAKE THE EVALUATION CONCRETE
Ask to see it.
Use these demonstrations to test the fit with your institution. Capability descriptions are a starting point, not independent assurance.
- Resolve a contract that has multiple display symbols.
- Inspect validation of a reference-data import.
- Confirm the actual catalogue scope for the proposed deployment.
QUESTIONS, ANSWERED
The questions that matter.
Bring the next question to a focused product and architecture conversation.
Does a symbol uniquely identify a derivative?
The documented model preserves contract context such as expiry, strike and option right, not just a display symbol.
Does the catalogue establish live availability?
No. Coverage, data, account and connector eligibility must be checked separately.
Does currency coverage mean spot FX?
No. Configured currency products must be identified explicitly. No universal spot-FX claim is made.
CONNECTED CAPABILITIES
Continue the evaluation.
START WITH YOUR REQUIREMENTS
Bring your operating model.
Let’s map the fit.
Discuss the client journey, enabled scope and institutional controls that matter to your team.