> For the complete documentation index, see [llms.txt](https://docs.cros.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cros.world/decentralized-ad-infrastructure/our-approach.md). # Our approach Cros provides advertisers, publishers and creators with infrastructure in the form of **APIs and tools**, as well as connectors with popular supply-side and demand-side platforms. Through the use of these APIs, SDKs and tools built for different game platform and familiar SSPs and DSPs, the ad-campaigns and ad-inventory can be matched together with off-chain auction and programmatic bidding. * The platform models ad-assets, ad-bids, auction formats and ad-impression as first-class blockchain-based primitives providing for a transparent allocation and pricing of advertisements. These **protocol primitives** form the substrate for creating innovative ad-serve and ad-bidding APIs for ease of integration with existing ad-platforms and ad managers. * The protocol is defined by the smart contract representations and rules. It defines the message and control flow between two or more participating entities to design campaigns, create ad-inventory, submit bids, run auctions and serve ads - everything secured and available for audit on-chain. The housekeeping services specified by the protocol include impression prediction, fraud detection & prevention, and event triggers. * The protocol token creates incentives for the network of participants to operate rationally and coordinate their actions toward the allocation and pricing of the advertisements. With the right mechanism design, the ad-revenue model is aligned with the token incentives for creators, consumers, advertisers and publishers. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cros.world/decentralized-ad-infrastructure/our-approach.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.