> For the complete documentation index, see [llms.txt](https://guides.getalby.com/developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/developer-guide/developer-guide/alby-browser-extension-apis/overview.md).

# Overview

The Alby Browser Extension acts as a provider of for open standards by injecting common window objects such as:

* `window.webln` ([WebLN](https://webln.guide/)) 
* `window.nostr` ([NIP-07](https://github.com/nostr-protocol/nips/blob/master/07.md))
* `window.liquid`
* `window.webbtc` ([WebBTC](https://webbtc.dev/))

The browser extension also injects a special `window.alby` object for alby-specific functionality such as programmatically requesting the creation of new Alby accounts.

{% hint style="info" %}
If you want to support multiple wallets implementing the same window APIs you can offer users a wallet selection UI and then use the vendor-specific APIs via *window\.alby*. (e.g. *window\.alby.webln.sendPayment*). 
{% endhint %}

### Alby Browser Extension GitHub repo

<https://github.com/getAlby/lightning-browser-extension>


---

# 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://guides.getalby.com/developer-guide/developer-guide/alby-browser-extension-apis/overview.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.