> 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/dids-decentralized-identifiers.md).

# DIDs (Decentralized Identifiers)

Reveel Pay(ID) API for DIDs

#### Summary

Turn any DID into a payment-ready identity with Pay(ID) — making it a universal, chain-agnostic stablecoin receiver.

#### Who It's For

* DID providers (e.g. ENS, Lens, MocaID)
* Custom application-level identity frameworks
* Any protocol that uses DIDs as user identities

#### Problem

DIDs lack built-in payment logic. While they resolve to addresses, they don’t support cross-chain routing, stablecoin settlement, or programmable preferences.

#### How Pay(ID) Solves It

Reveel enables DIDs to link to a Pay(ID), turning them into omnichain payment endpoints. Developers can recognize a DID, resolve the underlying Pay(ID), and trigger stablecoin payments that follow the user’s routing preferences.

#### Implementation Outline

* Link existing DID (e.g. ENS name) to a Pay(ID)
* Define Routes behind the Pay(ID)
* Integrate DID recognition + Reveel API in the app

#### Outcome / Benefits

* DIDs become payment-enabled identities
* Cross-app, cross-chain usability for user IDs
* Reduced cognitive load for users


---

# 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/dids-decentralized-identifiers.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.