> For the complete documentation index, see [llms.txt](https://www.webln.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.webln.guide/introduction/benefits-of-webln.md). # Benefits of WebLN WebLN comes with a couple of benefits: * **Better UX**\ WebLN allows for programmatic interactions and reduces friction between a Lapp and the user’s wallet. Users don't have to switch context for scanning a QR code to make a payment anymore. Additionally, they can sign a message with one click to prove ownership of a wallet. If a WebLN client supports auto-payments, no prompt is needed and the user is just one click away from sending a payment. * **Ready and secure**\ WebLN is a specification that only describes how to interact with a Bitcoin Lightning wallet. There is no need to trust and integrate a third-party library. Over the years WebLN has developed and has been recognized as a standard within the community. * **Simple implementation**\ Initialization and execution of WebLN requires not more than some lines of code of JavaScript - a language that is commonly used for creating web apps. * **Complementary to LNURL**\ WebLN works well together with [LNURL](https://github.com/fiatjaf/lnurl-rfc), another, more manual standard to make interactions with Lighting easier. If [implemented correctly](/building-lightning-apps/best-practices.md) WebLN provides a great enhancement of the UX. For users without a WebLN provider installed, LNURL can serve as a fall-back option. --- # 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://www.webln.guide/introduction/benefits-of-webln.md?ask=&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.