--- url: "https://predictiontoolkit.com/tools/azuro/" publisher: "PredictionToolkit" dateModified: "2026-11-02" --- [← SDKs & libraries]() ![Azuro logo]() Infrastructure # Azuro: infrastructure for sports prediction applications Azuro provides the protocol layer for applications that need betting functions, sports data and shared liquidity. Developers integrate its SDK, contracts and indexed data; liquidity providers use a different set of pool mechanics and economic responsibilities. [**3.5**/ 5Editorial rating]() [Editorial assessment]() [Open Azuro]() azuro.org **Available on:** API **Pricing:** [See plans and costs ↓]() [Screenshots]() [Explore alternatives]() **Availability: public** [SDKs & libraries]() [Data APIs]() +3 more [Liquidity & market making]() [Position yield]() [Sports research]() ## Screenshots and interface Product preview1 / 2 The overview introduces Azuro’s infrastructure ecosystem. ## What is Azuro? An Azuro integration starts with the role you want to perform. An application builder connects an interface to protocol operations and event data, while a blockchain integration needs the relevant deployments. A liquidity provider instead studies how capital is organized, allocated and rewarded. These responsibilities are distinct even when they meet in the same ecosystem. The documentation connects odds, virtual funds, providers and settlement with SDK and frontend resources. It also supplies subgraphs and deployment references. This is an independent infrastructure ecosystem: supported sports and liquidity functions should be assessed on their own terms, rather than treated as a Polymarket adapter or proof that every broad market concept on the landing page is implemented. ### Who it is for - Developers creating sports prediction or betting interfaces. - Blockchain teams evaluating a prediction-market integration. - Liquidity providers researching pool utilization, capital allocation and rewards. ## Features and coverage - **Shared pools and LiquidityTree** Connect an application to shared liquidity and study how LiquidityTree organizes and allocates pool capital. - **Event and odds infrastructure** Use the supported sports-event and odds-provider infrastructure for the application’s data requirements. - **SDK and frontend toolkit** Integrate protocol operations with the maintained SDK and construct the interface with the linked frontend tools. - **Indexed activity** Read protocol activity through the documented subgraphs rather than relying only on interface displays. - **Bet and payment operations** Follow contract-integration guides for betting and payment actions. - **Resolution policies** Consult provider and oracle-resolution rules together with settlement-policy resources. - **Deployment references** Check network addresses, audits and versioned releases for the deployment you intend to use. ## Workflows with Azuro ### Build an application Select a supported chain and inspect its current deployment. Connect the SDK and toolkit to the required event data, then check the resulting betting and payment flows. ### Evaluate pool participation Before supplying capital, examine pool utilization, virtual funds and reward distribution. Returns depend on actual betting and fee flows. ### Trace an event lifecycle Follow odds, accepted bets and settlement across the protocol’s defined actors, and test rejected as well as accepted and settled states. ## Pricing and total cost The public entry pages do not provide a single flat app-launch price. Protocol economics, frontend rewards, data access and chain costs depend on the integration and the role being taken. ## Getting started **Before you start:** Frontend, data-provider and liquidity-provider responsibilities differ. 1. Choose the Applications or Blockchains development path. 2. Check the applicable deployment addresses and versions. 3. Read the betting model and settlement rules. 4. Build a small integration using the SDK and indexed data. 5. Test accepted, rejected and settled event states. 6. Review the economic arrangement for your frontend or pool role. Define the responsibilities of the frontend builder, data provider and liquidity provider before joining their flows. [Read the developer and protocol documentation]() ## Useful links ### What to check - Frontend, data-provider and liquidity-provider responsibilities differ. - Documented sports and liquidity functions do not establish support for every broader market concept in promotional material. - Pool returns depend on actual protocol betting and fee flows. - A newer toolkit release may not be compatible with every older deployment. A closer look ## Ratings & reviews Editorial rating **3.5**/ 5 0 user reviews PredictionToolkit editorial ### Our take on Azuro Editorial rating: 3.5/5. Shared liquidity, subgraphs and developer tools give Azuro a clear infrastructure role. Integrating it requires understanding its protocol actors and settlement design; it is not a direct Polymarket data adapter. Based on documented features, setup and access terms. [How we rate]() ### User reviews 0 The main score switches to user ratings after 5 published reviews. **Be the first to share your experience** A specific example helps the next person choose the right tool. ## Related tools [Browse category]() ![SEDA documentation on Oracle Programs and Data Proxies]() [SEDA]() Infrastructure**3.5**Editorial Developer infrastructure for fetching external data, applying verifiable logic and delivering structured oracle results. - Access API Compare programmable infrastructure for event data. ![SX Bet product overview]() ![SX Bet logo]()[SX Bet]() Platform**3.5**Editorial A crypto-funded peer-to-peer sports exchange with live and upcoming events, bet slips and supported multi-selection parlays. - Access Web · API Compare a sports exchange interface. ![OrderbookTrade explanation of its execution and platform workflow]() ![OrderbookTrade logo]()[OrderbookTrade]() restricted Infrastructure**3.0**Editorial Integrate order actions, matching and market-making tools through shared API and WebSocket infrastructure. - Access API Also in SDKs and Developer Libraries. ## Frequently asked questions about Azuro ### Is Azuro a Polymarket frontend? No. It is an independent infrastructure ecosystem for applications built on its protocol and liquidity architecture. ### What developer resources are available? The documentation links an SDK and frontend toolkit, contract-integration guidance and deployment references. ### Can I query indexed protocol activity? Yes. The documentation describes subgraphs for reading indexed protocol data. ### Where should I check settlement rules? Use the knowledge hub and settlement-policy resources, including the responsibilities of providers and oracle-resolution participants. In this profile