> For the complete documentation index, see [llms.txt](https://doc.highkey.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.highkey.ai/7.-darp-usage-scenarios.md).

# 7. DARP Usage Scenarios

## Developers

**Build and deploy custom Web3 solutions**

* Create custom Agents using DARP servers for data access
* Deploy Schedulers for complex task orchestration
* Integrate with official and third-party DARP servers
* Access open-source model services for AI capabilities

## End Users

**Access Web3 data and services seamlessly**

* Use pre-built Agents for common Web3 tasks
* Access chain data through user-friendly interfaces
* Monitor Meme coins and market intelligence
* Interact with multiple chains in one platform

## Data Providers

**Share and monetize Web3 data resources**

* Deploy custom DARP servers
* Connect existing data sources to the platform
* Set up data access policies and pricing
* Monitor usage and manage permissions

## Enterprise Users

**Build comprehensive Web3 solutions**

* Create custom Agent workflows for specific needs
* Integrate with existing enterprise systems
* Manage large-scale data access and processing
* Deploy private DARP servers and Schedulers


---

# 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://doc.highkey.ai/7.-darp-usage-scenarios.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.