Platform · 07
You integrate once. We change what sits behind it.
Every market needs a different set of sources, and sources go down, get bought, change their terms or stop being the best option. Absorbing that is the layer's whole reason to exist.
- 1contract
- nsources behind it
- 0operator changes on a swap
What an operator is actually buying here
Not a discount on a data provider. A single contract, one API surface and one evidence format across five regimes, with the routing — which source is authoritative in which market, which is the fallback, what happens when the first one times out — handled on this side of the boundary.
The test of that promise is boring and specific: when a source is replaced, does anything change in your code? The answer has to be no, or the layer is decoration.
How routing decides
Inputs to the routing decision
- Market
- Which regime the player is registering under
- Document
- Issuing authority and series
- Health
- Live source availability
- Policy
- Your own source preferences
Set per check, not per account, because an operator may run several licences.
Some authorities are read better by one provider than another; the routing knows which.
A source that is timing out is routed around before it becomes your incident.
Where you have a commercial or contractual reason to prefer a source, that preference is honoured.