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

# YO Risk Graph

Risk Graph is YO's risk intelligence layer for DeFi. It scores pools, assets, protocols, and chains with a letter grade (A–F) based on their full dependency stack — not just the entity in isolation. This is the same system YO uses to inform vault allocations and due diligence.

Two ways to access it:

1. **Vault Exposure API** — free, public, no auth. Returns a vault's collateral exposure breakdown.
2. **Agent API** — paid via x402, for full risk grading and dependency mapping.

### Which one should I use?

<table><thead><tr><th width="158.546875"></th><th>Vault Exposure API</th><th>Agent API</th></tr></thead><tbody><tr><td>Cost</td><td>Free</td><td>Pay-per-query (x402/USDC)</td></tr><tr><td>Auth</td><td>None</td><td>Wallet signature</td></tr><tr><td>Returns</td><td>Collateral exposure for one vault</td><td>Risk grades, dependency graphs, entity search</td></tr><tr><td>Best for</td><td>Quick exposure checks, UX display</td><td>Full risk assessment, contagion analysis, agentic decision-making</td></tr></tbody></table>

Use the Vault Exposure API to see what a vault holds. Use the Agent API to grade what it holds and trace how risk propagates through it.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.yo.xyz/yo-risk-graph.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.