aperture

Protect backend services with a Lightning-powered L402 reverse proxy requiring payment.

57|18|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lightninglabs/lightning-agent-tools --skill aperture-lightninglabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aperture
Source: https://github.com/lightninglabs/lightning-agent-tools/tree/main/skills/aperture
Command: npx skills add https://github.com/lightninglabs/lightning-agent-tools --skill aperture-lightninglabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go, aperture, and includes scripts (resource) components.

What problem does it solve?

Aperture removes the friction of protecting web services with payments by turning an ordinary backend into a Lightning-native paywall that can issue L402 challenges and verify paid access.

Core Features & Use Cases

  • Paid API Gatekeeping: Place Aperture in front of an HTTP or HTTPS service and require Lightning payment before requests are proxied through.
  • Agent-to-Agent Monetization: Host content or endpoints that other agents can discover, pay for, and consume without manual billing workflows.
  • Operator-Friendly Setup: Generate a ready-to-edit config, connect to a local or remote lnd instance, and run the proxy in foreground or background mode.
  • Testing and Deployment Flexibility: Support mainnet, testnet, and regtest-style workflows, with options for TLS, no-auth development mode, and Docker-based integration testing.

Quick Start

Ask the agent to install Aperture, generate a configuration for your lnd node, start the proxy, and attach it to the backend service you want to protect.

Frequently Asked Questions about aperture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a Bitcoin Lightning paywall to my API?

Aperture creates a Lightning paywall for APIs by acting as a reverse proxy that issues L402 challenges and verifies micropayments via lnd before routing requests to your backend service.

How does an L402 reverse proxy handle paid API access?

An L402 reverse proxy intercepts HTTP requests, requires a Lightning invoice payment, and only proxies traffic to the configured backend service after verifying the paid access token.

What do I need to set up a Lightning micropayments proxy for local development?

Setting up a Lightning micropayments proxy requires a running lnd instance, the invoice.macaroon credential for invoice creation, a generated YAML configuration, and a backend service listening on the configured port.

Can I use a reverse proxy to monetize agent-to-agent API content?

Yes, you can monetize agent-to-agent content by hosting endpoints behind a proxy that requires other agents to discover endpoints, pay Lightning invoices, and consume content without manual billing workflows.

Does the Lightning paywall proxy support regtest testing and TLS?

Yes, the Lightning paywall proxy supports regtest workflows for testing, alongside mainnet and testnet, and includes options for enabling TLS or using a no-auth development mode.