> For the complete documentation index, see [llms.txt](https://docs.nulth.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nulth.xyz/guides/prove-to-an-auditor.md).

# Prove compliance to an auditor

A Nulth account can prove its spending policy stays within a limit — without revealing the policy. This is the auditor / correspondent-bank flow.

## The scenario

An auditor (or a correspondent bank, or a compliance desk) needs assurance that this treasury's per-payment cap stays within a regulatory limit — say, an AML transaction ceiling. They must **not** see the cap itself.

## Steps

1. Open **Auditor & Verify** in the app.
2. Set the **regulatory limit** the auditor requires.
3. **Prove** — your browser generates a disclosure proof that `cap ≤ regulatory_max`, bound to your account's on-chain `policy_commitment`.
4. The proof is verified **on-chain** against the shared BN254 verifier. The auditor sees a single verified bit: *within the limit* — and nothing about the cap.

## What the auditor learns (and doesn't)

* **Learns:** the account's real, committed cap is ≤ the stated limit — verifiably, because the proof opens the same `policy_commitment` that's stored on-chain.
* **Does not learn:** the cap value, the salt, or anything about the allowlist.

If the cap exceeds the limit, **no proof exists** — the account cannot falsely claim compliance.

## Trust note

The `regulatory_max` is supplied by the auditing side (e.g. published by an anchor or KYC provider) — an oracle-trust assumption, stated openly. See [Auditor disclosure](/how-nulth-works/auditor-disclosure.md) for the circuit and cost, and the [roadmap](/trust-and-security/roadmap.md) for set-containment disclosures (proving your allowlist ⊆ an authority's screened set).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.nulth.xyz/guides/prove-to-an-auditor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.