# Shadow

## Shadow

- [Overview](https://docs.shadow.xyz/overview.md)
- [Quickstart](https://docs.shadow.xyz/quickstart.md): This 5 minute tutorial will walk you through steps to create a shadow fork of Ethereum Mainnet, add a shadow event to a contract, and retrieve its data.
- [Use cases](https://docs.shadow.xyz/use-cases.md)
- [Supported chains](https://docs.shadow.xyz/supported-chains.md)
- [Versioning](https://docs.shadow.xyz/modify-contracts/versioning.md): Your shadow fork has immutable versioning so you can safely deploy changes without disrupting previously running jobs.
- [How to's](https://docs.shadow.xyz/modify-contracts/how-tos.md)
- [Proxy contracts](https://docs.shadow.xyz/modify-contracts/how-tos/proxy-contracts.md)
- [Using oracles](https://docs.shadow.xyz/modify-contracts/how-tos/using-oracles.md)
- [Factory contracts](https://docs.shadow.xyz/modify-contracts/how-tos/factory-contracts.md)
- [Interdependent shadow contracts](https://docs.shadow.xyz/modify-contracts/how-tos/interdependent-shadow-contracts.md)
- [Shadow RPC](https://docs.shadow.xyz/getting-data/shadow-rpc.md)
- [Database syncs](https://docs.shadow.xyz/getting-data/database-syncs.md)
- [Recurring exports](https://docs.shadow.xyz/getting-data/recurring-exports.md)
- [One-off exports](https://docs.shadow.xyz/getting-data/one-off-exports.md)
- [API Keys](https://docs.shadow.xyz/getting-data/api-keys.md): Learn how to authenticate your requests to Shadow.
- [Postgres](https://docs.shadow.xyz/integrations/postgres.md): Set up a fully managed data pipeline to stream data into your Postgres database in real-time.
- [GCS / S3](https://docs.shadow.xyz/integrations/gcs-s3.md): Set up a fully managed data pipeline to export data to a GCS / S3 bucket in a one-off or recurring fashion.
- [Dune](https://docs.shadow.xyz/integrations/dune.md): Set up a fully managed data pipeline to upload data to Dune in a one-off or recurring fashion.
- [Catalog](https://docs.shadow.xyz/product-guide/catalog.md)
- [Test runs](https://docs.shadow.xyz/product-guide/test-runs.md)
- [Subgraphs](https://docs.shadow.xyz/product-guide/subgraphs.md)
- [Proxy contracts](https://docs.shadow.xyz/tips/proxy-contracts.md)
- [Solidity beginners](https://docs.shadow.xyz/tips/solidity-beginners.md): Don't know Solidity? Don't worry.
- [Recommended tools](https://docs.shadow.xyz/tips/solidity-beginners/recommended-tools.md): Don't know Solidity? Don't worry.
- [Concepts](https://docs.shadow.xyz/resources/concepts.md)
- [FAQs](https://docs.shadow.xyz/resources/faqs.md)


---

# 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
This site has an agentic ask interface you may use to query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shadow.xyz/index.md?ask=<question>&goal=<user_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.
