# Burnt Verified

**Burnt Verified** is Verona's enterprise surface for **income, employment, and credential verification**—cryptographic proofs from the source, with **no documents stored** and no custodial liability for the verifier.

Where Ero proves the consumer story, Burnt Verified proves the **real-company** story: paying customers, enterprise workflows, and verification revenue on the same Truth Engine that powers agents and apps.

## What it enables

* **Income and employment verification** — Users authenticate to payroll or HR sources; verifiers receive a cryptographic proof in seconds, not a document upload
* **Real-estate, lending, and insurance workflows** — Decisions on records verified at the source; the data underneath never transits through your systems
* **Non-custodial assurance** — Gate features, payouts, compliance, or agent tools on attestations instead of PII archives
* **Composable with agents** — Authorized agents query scoped proofs (for example income above a threshold) without holding bank statements

Burnt (the company) sells verification to landlords, lenders, insurers, and other buyers who today pay traditional data brokers. Burnt's wins are **revenue**; Verona's wins are **category and network effects**—the surfaces reinforce each other.

## For developers

Start with the verification stack, then layer product logic:

| Source          | Module           | Developer entry                                                                        |
| --------------- | ---------------- | -------------------------------------------------------------------------------------- |
| Websites / APIs | zkTLS            | [Internet Verification](/verona/build-on-verona/verification/internet-verification.md) |
| Email           | zkEmail          | [Email Verification](/verona/build-on-verona/verification/email-verification.md)       |
| Identity        | zkPassport       | Truth Engine surface; contact the team for integration paths                           |
| Mobile apps     | App Attestations | [Mobile Verification](/verona/build-on-verona/verification/app-attestations.md)        |

Publishing custom verification keys: [Publishing ZK Verification Keys](/verona/build-on-verona/verification/publishing-zk-verification-keys.md).

Burnt Verified product APIs and issuer flows will be documented here as they ship; the modules above are the current integration path.

{% hint style="info" %}
Do not name unannounced data-broker or operator partnerships in public docs until cleared by marketing and legal.
{% endhint %}

## Related docs

* [Truth Engine](/verona/about-verona/verification-infrastructure.md)
* [Use Cases](/verona/about-verona/overview/use-cases.md)
* [Ero (EarnOS)](/verona/about-verona/surfaces/earnos.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
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.burnt.com/verona/about-verona/surfaces/burnt-verified.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.