# Welcome to Stork Stork is an oracle protocol that enables ultra-low latency connections between data providers and both on-chain and off-chain applications. The most common use case for Stork is pulling and consuming market data in the form of real-time price feeds for DeFi. The core technical principles of Stork are: * Modularity * Low latency / high throughput * Cost efficiency * Arbitrary data support * Transparency, verifiability, and security Stork is implemented as a [pull oracle](https://docs.stork.network/core-concepts#docs-internal-guid-4b312e7b-7fff-1147-c04b-bbaadec1a82a) and supports automated on-chain delivery. Stork continuously aggregates, verifies, and audits data from trusted publishers, and makes that aggregated data available at sub-second latency and frequency. This data can then be pulled into any on or off-chain application as often as needed. Stork was created with the principle of trustlessness in mind. As such, all data inputs and outputs to Stork are cryptographically verifiable. This includes the underlying publisher data as well as Stork’s aggregated results. Stork currently supports 500+ assets on 70+ chains, including[ EVM](https://docs.stork.network/resources/contract-addresses/evm) chains, [Solana](https://docs.stork.network/resources/contract-addresses/solana), [Sui](https://docs.stork.network/resources/contract-addresses/sui), [Aptos](https://docs.stork.network/resources/contract-addresses/aptos), and [more](https://docs.stork.network/resources/contract-addresses), and is easily deployed on any other chain not yet supported. Chain deployments and asset additions are available upon request. For a complete list of supported chains, see the [Contract Addresses](https://docs.stork.network/resources/contract-addresses) page. For a complete list of supported assets, see the [Asset ID Registry](https://docs.stork.network/resources/asset-id-registry) page. To learn more about how Stork works, visit [Core Concepts](https://docs.stork.network/introduction/core-concepts) and [How It Works](https://docs.stork.network/introduction/how-it-works). {% hint style="info" %} Interested? Contact Stork Labs to determine appropriate feeds that meet your requirements. or [X (formerly Twitter) DMs](https://x.com/StorkOracle) open. {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.stork.network/introduction/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.