Aperture (L402 proxy, Lightning Labs)
Lightning Labs reverse proxy that puts any HTTP or gRPC API behind L402: Lightning invoices plus macaroon credentials, answered with HTTP 402.
- Sato Score71
- ChainsBitcoin
Aperture (L402 proxy, Lightning Labs) is an open-source payment rail by Lightning Labs on Bitcoin, with last code activity on 2026-11-07 (Active). Latest release on 2026-11-05. Sato Score 71/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-09. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Nov 7, 2026 · Last release Nov 5, 2026 (v0.6.0) · ★ 272
Listed from l402.tech on 2026-09-24. Install: not attempted — no install path on record. Evidence →
Next step
Watch Aperture (L402 proxy, Lightning Labs)
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on lightninglabs/aperture before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Aperture is the reference L402 server from Lightning Labs. It sits in front of an HTTP or gRPC backend and answers unauthenticated requests with HTTP 402, a Lightning invoice and a macaroon; once the client pays, the macaroon plus the preimage is the credential for later requests. L402 predates x402 and is a separate protocol: an L402 token can be reused until it expires, while x402 exact on Lightning (merged 2026-09-23) settles one payment per request through a facilitator. Lightning Labs' agent toolkit (lightning-agent-tools) uses Aperture as its seller-side skill.
Sato Score
71/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 19/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 8/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from l402.tech on 2026-09-24. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Bitcoin | self-reported | github.com/lightninglabs/aperture | as of 2026-11-09 |
| Verification status | Unverified — not independently reviewed | self-reported | l402.tech | as of 2026-11-09 |
| Recent activity | last release 2026-11-05 · last commit 2026-11-07 | observed | github.com/lightninglabs/aperture | 2026-11-09 |
| Website answers | answered (HTTP 200) | observed | l402.tech | 2026-11-09 |
| Daily check record | 43 of 43 daily checks since 2026-09-27 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-11-08 |
| Creator profile | https://github.com/lightninglabsconfidence 0.85 | self-reported | github.com/lightninglabs/aperture | as of 2026-10-13 |
| Sato Score | 71/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-11-09 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Observed record — 44 daily checks since 2026-09-27
- Succeeded
- 44
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.
Last 30 days — to 2026-11-09, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Bitcoin
- Agent types
- Payments, Protocol
- Open source
- Yes
- Pricing
- Free / open source (MIT)
- Last checked
- 2026-11-09
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Aperture (L402 proxy, Lightning Labs) fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from Aperture (L402 proxy, Lightning Labs), pulled from its GitHub and X.
aperture v0.6.0
This is the first release since v0.5.0 (March). It adds metered pricing, so one Lightning payment can buy a bundle of tokens that each request then draws down by actual usage. It adds Wavelength-backed invoices, so a seller can run aperture without an lnd node. It also brings the MPP (Payment HTTP Authentication Scheme) implementation up to the spec and includes a large authorization hardening pas
aperture v0.4.3
Release v0.4.3
Listing History
Recorded changes to Aperture (L402 proxy, Lightning Labs)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Nov 5, 2026New release published
- Oct 13, 2026Auto-enriched: creator profile url
- Oct 2, 2026New release published
- Sep 27, 2026Edited: date added
- Sep 27, 2026Listed on Sato Hub
- Sep 27, 2026Sato Hub began tracking this listing
- Sep 24, 2026Edited: description long
- Sep 24, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Agent Payments Protocol (AP2)
ActiveOpen protocol from Google for secure agent-led payments across traditional and crypto rails, with a crypto-native x402 extension built with Coinbase, Ethereum Foundation, and MetaMask.
x402
EarlyOpen HTTP 402 payment protocol, now at the x402 Foundation: agents pay per request in stablecoins, and by a newly merged spec, in bitcoin over Lightning.
PayAI Network
ActiveSolana-first x402 payment facilitator enabling usage-based, machine-to-machine payments for AI agents.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Aperture (L402 proxy, Lightning Labs)
- Is Aperture (L402 proxy, Lightning Labs) open source?
- Yes. Aperture (L402 proxy, Lightning Labs) is open source; the repository is https://github.com/lightninglabs/aperture. Checked as of 2026-11-09.
- Which chains does Aperture (L402 proxy, Lightning Labs) support?
- Aperture (L402 proxy, Lightning Labs) lists support for Bitcoin as of 2026-11-09.
- Is Aperture (L402 proxy, Lightning Labs) still maintained?
- The most recent code activity Sato Hub observed was on 2026-11-07 (last commit 2026-11-07, last release 2026-11-05), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Aperture (L402 proxy, Lightning Labs)?
- Sato Hub has no deploy spec for Aperture (L402 proxy, Lightning Labs); follow the project's own documentation at https://github.com/lightninglabs/aperture#readme.
- Is Aperture (L402 proxy, Lightning Labs) verified on Sato Hub?
- No independent verification is on record for Aperture (L402 proxy, Lightning Labs); its verification status is "Unverified" and its Sato Score is 71 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Aperture (L402 proxy, Lightning Labs) — Sato Hub." Sato Hub, updated 2026-11-09, accessed 2026-11-09. https://satohub.ai/resources/apertureData last refreshed 2026-11-09; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.