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

# Transparency

Transparency is central to Nara’s design. Because Nara connects on-chain assets with real-world payment financing, users need clear information about reserves, portfolio allocation, performance, risks, audits, and incidents.

Nara’s transparency framework should help users answer four questions: what backs NaraUSD, how capital is allocated, how the PayFi portfolio is performing, and what risks or incidents have occurred.

#### Transparency reports and evidence

| Evidence                  | What it should show                                                                        | Update cadence       |
| ------------------------- | ------------------------------------------------------------------------------------------ | -------------------- |
| **Reserve dashboard**     | Current reserve assets, supported chains, contract addresses, and relevant balances.       | Real time update     |
| **Portfolio report**      | Liquid reserves, PayFi exposure, allocation ranges, tenor, concentration, and performance. | Every 7 days         |
| **Insurance fund report** | Current balance, funding source, coverage rules, and loss waterfall role.                  | Every 7 days         |
| **Incident log**          | Material incidents, impact, response, remediation, and current status.                     | Updated as required. |


---

# 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.nara.io/nara-protocol/transparency.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.