> 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/introduction/readme.md).

# Key Concepts-old

## Pay(ID)

A unique, human-readable identifier that can receive *any stablecoin from any chain*, and automatically route it to the recipient’s desired destination.

## Routes

Rules defined by the user to control how funds are settled. Routes follow an "if this, then that" model. Examples:

* USDC from Optimism → USDC on Base, into Wallet A
* Any funds from alice(id) → USDT on Polygon, into Wallet B

Routes can be based on 3 types of triggers:

* Source Token (e.g. if I receive USDC, then...)
* Source Network (e.g. if I receive funds on BNB Chain, then...)
* Sender (e.g. if I receive funds from Bob, then...)

## Pay(ID) Data Layer

Reveel’s database layer storing:

* Pay(ID) registrations
* Routes
* Linked wallets
* Metadata (linked ENS, MocaID, email, social handles, app namespaces…)

## Liquidity Orchestration Layer

Reveel’s routing engine that determines the optimal transaction path using partner liquidity networks. It finds the best route to deliver funds to the destination wallet, considering:

* Gas fees
* Available bridges
* Partner fees
* Settlement time
* Token liquidity


---

# 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/introduction/readme.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.