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

# Developer Sandbox

### **Build and test bitcoin payments in minutes.** 

**Alby Sandbox offers:**

* zero-setup test wallets
* different payment scenarios
* ready-to-use code examples
* one-shot prompts for agents

**Here's the developer workflow we've enabled:**

1. Create test wallets programmatically with the faucet API
2. Build your payment logic (Alby Agent Skill is all you need)
3. Run full end-to-end tests with real payment flows
4. When ready, swap in your production NWC connection available in your [Alby Hub](https://getalby.com/alby-hub) wallet.

**Get started:**  <https://sandbox.albylabs.com/>

{% embed url="<https://www.youtube.com/watch?v=FAxCr3Fj0vo>" %}

### The New Bitcoin Payment Developer Stack

We've built three tools that work together to eliminate friction from implementing bitcoin payment flows:

[**NWC Faucet**](https://faucet.nwc.dev/) — Create a test wallet with a single HTTP request. No signup. No infrastructure. Just a working wallet with 10,000 sats.

[**Alby Agent Skill**](https://github.com/getAlby/alby-agent-skill) — An AI assistant that knows how to build bitcoin apps. It understands Nostr Wallet Connect, lightning addresses, invoices, subscriptions, hold invoices, and more.

[**Alby Sandbox**](https://sandbox.albylabs.com/) — A visual playground to see bitcoin lightning payments in action across multiple wallets.

All tools are combined in  <https://sandbox.albylabs.com/>. Give it a try.&#x20;

Once you are ready to go live, swap in your production NWC connection available in your [Alby Hub](https://getalby.com/alby-hub) wallet. 🚀


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.getalby.com/developer-guide/developer-guide/developer-sandbox/developer-sandbox.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.