> For the complete documentation index, see [llms.txt](https://docs.herodotus.dev/herodotus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.herodotus.dev/herodotus-docs/developers/storage-proof-api.md).

# Storage Proof API

Request storage proofs quickly and easily

The Storage Proof API enables developers to request storage proofs quickly and easily. There is no need to understand cryptography, zero-knowledge proofs, or how to write circuits. The API handles scheduling, mutualizes many costs associated with generating storage proofs and saves developers significant time so they can focus on building their on-chain data-powered applications.

Requests to this API initiate actions or processes, like running the Storage Proof Workflow. The product name remains **Storage Proof API**; HTTP traffic is served by **Mission Control**.

{% hint style="info" %}
Note: Using these endpoints incurs charges based on resource usage.
{% endhint %}

### **API Endpoint**

**URL:** `https://mission-control.api.herodotus.cloud`

**Alias:** `https://api.herodotus.cloud` (same Mission Control service)

**Auth:** `api-key` header (required on all endpoints except `/is-alive`)

Primary routes:

* `POST /submit-request`
* `GET /get_queries/{request_id}`
* `GET /get_actions/{query_id}`
* Grow orders: `GET/POST /grow-orders`, `GET /grow-orders/{id}`, `POST /grow-orders/{id}/cancel`
* `GET /is-alive`

Do not use the retired paths `/submit-batch-query` or `/batch-query-status`.

Canonical docs: <https://docs.herodotus.cloud/storage-proofs-api/introduction>

## Interactive Documentation

**URL:** [`https://mission-control.api.herodotus.cloud/swagger/`](https://mission-control.api.herodotus.cloud/swagger/)

## Examples

* **Step by step example:** [`https://github.com/HerodotusDev/yab-herodotus`](https://github.com/HerodotusDev/yab-herodotus)
