webln.guide valid

Welcome

Welcome to the Lightning Web Standard (WebLN). This guide covers how to build a Bitcoin Lightning-driven web application using the WebLN standard.

For agents: WebLN Guide: documentation for building Bitcoin Lightning web apps with the WebLN standard, including window.webln API reference and getting-started guides.

weblnbitcoin lightninglightning web appswindow.weblnweb paymentsjavascript api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T02:40:06.387Z. Cached copy · Source on webln.guide

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

# Welcome

Welcome to the Lightning Web Standard (**WebLN**). This guide covers how to build a Bitcoin Lightning-driven web application using the WebLN standard.

Bitcoin is a global payment protocol that anyone with Internet access can participate in and contribute to. Hence, Bitcoin Lightning’s use cases are as vast as its user base. However, building them does not need to be complicated. We designed this guide to help anyone get started quickly. We can’t imagine every possible use case, but we can help you to build for them.

You may be interested in reading this guide if you want to build or operate a web application

* that accepts or makes Bitcoin Lightning payments
* that have decentralized identity and authentication

All you need is to interact with a client application such as a browser extension that understands WebLN. It does so by providing a JavaScript API called `window.webln` on every web page you visit. To have a look at what this object looks like, have a look at the [WebLN Reference](/building-lightning-apps/webln-reference.md) or just type `window.webln` in the Chrome or Firefox DevTools console.

WebLN is a JavaScript interface to the Bitcoin Lightning Network. There are functions to:

* Get information about a user's Bitcoin Lightning node ([`webln.getInfo`](/building-lightning-apps/webln-reference.md))
* Send a payment ([`webln.sendPayment`](/building-lightning-apps/webln-reference.md))
* Request an invoice to receive a payment ([`webln.makeInvoice`](/building-lightning-apps/webln-reference.md))
* Request a signature of an arbitrary message ([`webln.signMessage`](/building-lightning-apps/webln-reference.md))
* …and [some more](/building-lightning-apps/webln-reference.md)

When a WebLN provider is installed, any front-end code can get access to all these functions, and interact with the Bitcoin Lightning network. These web applications are called *LApps* (Lightning Apps).


---

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

Related sites

Find similar publishers by meaning →

Other listed sites in Documentation and reference. See the whole category →

Machine-readable: GET /v1/resolve?q=webln.guide · GET /v1/domain/webln.guide · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for webln.guide:
1. POST https://agentwebmap.com/v1/sites/webln.guide/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://webln.guide/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/webln.guide/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/webln.guide).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.