> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/blink-payment-methods/lightning-address/what-is-a-lightning-address-and-what-does-it-look-like.md).

# What is a Lightning Address, and what does it look like?

Lightning Addresses are a type of Lightning Network payment request based on the LNURL protocol that allows users to receive bitcoin payments directly to their Lightning wallet. They look just like an email address, but instead of emails, you can receive Lightning payments with it.

Lightning Addresses can look different depending on the service that the payment recipient uses.

For example, a Blink user's Lightning Address will look like <username@blink.sv>, while a Wallet of Satoshi user's Lightning Address might look like <username@walletofsatoshi.com>.

Regardless of the format, all Lightning Addresses are unique to the recipient, allowing them to receive Lightning payments securely and easily.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faq.blink.sv/blink-payment-methods/lightning-address/what-is-a-lightning-address-and-what-does-it-look-like.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.