> 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/what-is-webln.md).

# What is WebLN

### Introduction

WebLN is a set of specifications for Lightning apps and client providers to facilitate communication between web apps and users' Lightning nodes in a secure way. It provides a programmatic, permissioned interface for letting applications ask users to send payments, generate invoices to receive payments, and much more.

![WebLN  Provider functionality](https://121660472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSHMrYyqxEldRs701vokD%2Fuploads%2FeDFFV3BfQBVYe1mfboJT%2FFrame%201\(2\).png?alt=media\&token=dd65fb76-9e61-4b3b-83c2-f4423560d6da)

### State of WebLN

WebLN builds on the idea of [web3.js](https://www.npmjs.com/package/web3), a collection of libraries that allow you to interact with a local or remote ethereum node using HTTP, IPC or WebSocket. The WebLN specifications were published in 2018 and since then have continuously improved. In the meantime several Lightning applications and client providers have been built using this standard.


---

# 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/what-is-webln.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.