# Getting Proofs

When your application retrieves data from the indexer, each blob and account change comes with a built-in ZK proof that can be verified directly on-chain.

These proofs tie every piece of fetched information back to exactly what happened in the ledger history, so no data will ever be taken on faith.

<table><thead><tr><th width="224.228515625">RPC Call</th><th>Description</th></tr></thead><tbody><tr><td><a href="/pages/09tVdH32a4E5BRHluHYB">checkpoint_proof</a></td><td>Initiate a ZK proof committing to a series of data blobs.</td></tr><tr><td><a href="/pages/gQNdMUhyYgCJRwtsmFL1">get_proof_request_status</a></td><td>Returns the current status of the ZK proof generation: created, completed, failed, etc.</td></tr></tbody></table>


---

# 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.termina.technology/documentation/open-source-contributions/modules/data-anchor/indexing-data/getting-proofs.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.