> For the complete documentation index, see [llms.txt](https://docs.stork.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stork.network/introduction/products.md). # Products Stork for Real Time, Options, StarkEx, and the Composite Oracle Service. ### Stork for Real Time Stork for Real Time is an ultra low-latency, decentralized off and on-chain price feed designed for any chain. Stork for Real Time is powered by a decentralized network of data publishers, and signed with a cross-chain compatible signature. Stork for Real Time prioritizes performance, using ultra-fast websockets to ensure data is available at the millisecond level, similar to the data used for trading in TradFi. Using an off-chain, decentralized feed gives protocols the ability to perform initial processing off-chain, and elect to only push on-chain the price updates that are relevant to their product. Since prices are signed in a chain-compatible way, protocols can use Stork’s Contract, or their own smart contract, to verify the feed on-chain, proving that the data is legitimate. ### Stork for StarkEx Stork maintains a first class partnership with StarkEx. This enables Stork to provide oracle services that are accepted natively by StarkEx. The key difference between Stork for Real Time and Stork for StarkEx is that the signatures used are compatible with StarkEx, and present only in the publisher messages. Also, publishers use StarkEX's native signatures when providing data for StarkEX users. ### Composite Oracle Service A Composite Oracle Service (COS) allows for modular and configurable custom [Aggregators](/introduction/how-it-works.md#aggregators) enabled by Storks core architecture. A COS is a tuned oracle that provides aggregated data leveraging Stork's decentralized publisher network, while creating a composite of the specific assets and aggregation methods required by a [Subscriber](/introduction/how-it-works.md#subscribers). For more information about how Stork’s core architecture enables COS, see [How It Works](/introduction/how-it-works.md). ### Auto Pushed Feeds Stork provides a service to automatically push data to any supported chain based on a configurable schedule and delta tolerance threshold. Protocols that only require on-chain data and want the simplest plug-and-play experience can request new feeds by reaching out to . {% hint style="info" %} Interested? Contact Stork Labs to determine appropriate feeds that meet your requirements. or [Twitter DMs](https://twitter.com/StorkOracle) open. {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stork.network/introduction/products.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.