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

# Use Cases

- [AI Agent Frameworks](https://docs.reveel.id/use-cases/ai-agent-frameworks.md): Reveel Pay(ID) API for AI Agent Frameworks
- [ElizaOS POC](https://docs.reveel.id/use-cases/ai-agent-frameworks/elizaos-poc.md): A proof-of-concept plugin that integrates Reveel Pay(ID) directly into the ElizaOS agent framework, enabling agents to search, authenticate, manage routes, and view transaction history using Pay(ID).
- [Openclaw Skill](https://docs.reveel.id/use-cases/ai-agent-frameworks/openclaw-skill.md): The Reva Openclaw Skill gives any OpenClaw agent a wallet and a Pay(ID), enabling it to earn, pay, hire, and settle. Built on Privy wallet infrastructure and Reveel's routing layer.
- [DIDs (Decentralized Identifiers)](https://docs.reveel.id/use-cases/dids-decentralized-identifiers.md): Reveel Pay(ID) API for DIDs
- [Embedded Wallets](https://docs.reveel.id/use-cases/embedded-wallets.md): Reveel Pay(ID) API for Embedded Wallets
- [Portal POC](https://docs.reveel.id/use-cases/embedded-wallets/portal-poc.md): A proof-of-concept integration combining Portal's embedded wallet infrastructure with Reveel Pay(ID), enabling applications to give their users a single omnichain payment identity.


---

# 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.reveel.id/use-cases.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.