It is no use having a wonderful betting system if the users cannot find the bet that they want. Not only that, in order for the system to present sufficient liquidity (so bettors can find the bet that they want to make), and to provide optimal volume for consensus settlement, it is important that all software clients see the same selections as the same thing. As an example, it is equally valid to call a match winner market “match winner” or “winner” or even “moneyline 1X2”. The system needs to provide a mechanism to avoid duplication of markets and present a unified interface between disparate parties.A distributed directory of bets will be built in to the system making it simple for software clients to present a logically ordered menu of choices. The system will combine the many “standards” for event and market naming so that the same bet is treated equally. While the API will provide all functionality to all participants it is anticipated that there would be more specific apps built that focus on the intended end user. As an example, a sports bettor would in general use an interface similar to modern sports betting apps where bets can easily be found and taken with no concern for the underlying markets and events or laying prices.
Sportsbooks and wholesale bettors would utilise the lay side of bets and may or may not integrate the directory services. Some implementation of directory services and lay pricing may be purely API level integrations with existing sports books or exchanges.