> For the complete documentation index, see [llms.txt](https://resource-network.gitbook.io/resource-technical/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resource-network.gitbook.io/resource-technical/07-technology/7.4-distributed-underwriting-and-data-aggregation.md).

# 7.4 Distributed Underwriting and Data Aggregation

The role of risk assumption within the Resource protocol falls on network participants that assume the underwriter role. The Underwriting Application is a simple dApp that aggregates on/off chain data to derive a protocol-native credit score. In partnership with Teller Finance, we developed an underwriting algorithm responsible for deriving a network specific credit score.

The Underwriting dApp acts as a viewing window into the protocol where the underwriter can stake SOURCE, view financial data of businesses associated with each marketplace/network, create liquidity pools for specific aspects of a marketplace, track their Underwriter portfolio, delegate SOURCE to other underwriters, assume delegated SOURCE, and harvest rewards.


---

# 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://resource-network.gitbook.io/resource-technical/07-technology/7.4-distributed-underwriting-and-data-aggregation.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.