> For the complete documentation index, see [llms.txt](https://docs.doot.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doot.foundation/readme.md).

# Introduction

This is the canonical, production‑grade documentation for the Doot Oracle. It explains how the system works end‑to‑end, how to run it, and how to integrate it safely in production.

Doot provides signed, verified price feeds for 10 core crypto assets with multiple levels of trust and availability:

* API (fastest): served from the Doot backend cache
* L2 (Zeko): on‑chain reads with fast finality
* L1 (Mina): on‑chain reads with maximum security

The SDK automatically falls back API → L2 → L1, returning a consistent response shape regardless of source.

What’s inside these docs:

* Architecture: Components and data flow
* SDK: Usage, methods, response formats, fallbacks, and errors
* Backend: Cron jobs, caching, aggregation, IPFS pinning, and on‑chain updates
* Contracts: L1/L2 design, off‑chain state, methods, and deployment notes
* Operations: Config, runbooks, monitoring, and troubleshooting
* Examples: Practical usage and reference snippets

New to Doot? Start with Architecture, then pick the section for your role (SDK consumer vs. protocol operator).


---

# 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:

```
GET https://docs.doot.foundation/readme.md?ask=<question>
```

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.