Plan the crypto pricing boundary between a broker's upstream venues, quotation policy and trading server.
A reference quote is not evidence that an order can execute at that price. Document whether the broker consumes indicative prices, a venue order book or an executable liquidity connection; each requires different risk and availability checks.
Review decimal precision, contract size, weekend trading permissions and the relationship between feed symbols and platform instruments. A feed update should not overwrite a server's contract settings without a separately approved configuration change.
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
| Instrument scope | Identify the exact underlying, source identifier, quote currency and intended use. |
|---|---|
| Consumer workflow | List trading platforms, charts, risk tools and applications that need the output. |
| Delivery contract | Agree protocol, quote fields, timestamps, source status and recovery behaviour. |
| Production review | Confirm source rights, integration ownership, test evidence and commercial scope. |
For digital assets, define who consumes the prices and what each system needs to reconstruct a usable quote. An application dashboard, broker platform and historical process can require different delivery rules even when they share one normalized instrument model.