> 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/ai-agent-frameworks.md).

# AI Agent Frameworks

Reveel Pay(ID) API for AI Agent Frameworks

#### Summary

Enable AI Agents to transact across chains with a single identity using Pay(ID) — simplifying Agent-to-Agent and Human-to-Agent payments.

#### Who It's For

* Agent framework developers (e.g. ElizaOS, Virtuals, Olas, Fetch.ai, Aethir)
* AI agents interacting with users or other agents
* Cross-chain payment systems embedded in AI protocols

#### Problem

AI agents often operate across domains and applications — but managing multiple wallets, bridging assets, and sending payments across chains creates unnecessary friction in the agent stack, preventing agent to transact with other agents or humans on different networks.

#### How Pay(ID) Solves It

Pay(ID) allows each Agent to have its own omnichain payment identity, removing the need to manage multiple wallets or networks. Funds sent to an Agent's Pay(ID) are routed automatically to its preferred token and chain, allowing agents to transact with any other party while holding only 1 type of stablecoin.

#### Implementation Outline

* Integrate Reveel Pay(ID) API as a plug in/skill for the agent framework
* Let users empower each agents with a Pay(ID)
* Define Route rules for token/network preferences
* Agents can then use the Reveel API to resolve Pay(ID)s and trigger cross-chain payments

#### Outcome / Benefits

* Abstracted Agent-to-Agent payments
* Simplified multi-agent financial coordination
* Cleaner architecture for AI payment logic


---

# 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/ai-agent-frameworks.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.