lnget primary sources — 2026-05-03

Project status in this pass

• No canonical standalone lnget whitepaper or litepaper surfaced.
• The clearest current source of truth is the canonical repository README plus the first-party architecture guide in docs/agents.md.
• The materials consistently frame lnget as a client-side operating layer for consuming paid HTTP resources over Lightning, not as a generic download utility.

Primary-source snapshots

1) Canonical repository / project positioning

• URL: https://github.com/lightninglabs/lnget
• Key excerpt:
  • The repository positions lnget as a Lightning-aware command-line HTTP client maintained by Lightning Labs.
  • Even before the deeper docs, the project framing is clearly about making paid HTTP access operational rather than manual.

2) Canonical repository README

• URL: https://raw.githubusercontent.com/lightninglabs/lnget/master/README.md
• Key excerpt:
  • The README says lnget is a command-line HTTP client that handles L402 Lightning payments transparently.
  • It describes the core flow: when a server returns 402 Payment Required, lnget parses the WWW-Authenticate challenge, pays the invoice through a configured backend, retries the request, and caches the resulting token per domain.
  • It also documents max-cost / max-fee controls, JSON output, quiet mode, and examples aimed at automated pipelines and AI agents.

3) Dashboard and local API surface

• URL: https://raw.githubusercontent.com/lightninglabs/lnget/master/README.md
• Key excerpt:
  • The README documents a built-in spending dashboard, SQLite-backed event logging, and a local REST API for events, token management, status, and configuration.
  • This is strong evidence that lnget is more than a thin request wrapper: it packages observability and operations around paid HTTP usage.

4) First-party architecture guide

• URL: https://raw.githubusercontent.com/lightninglabs/lnget/master/docs/agents.md
• Key excerpt:
  • The guide describes lnget’s architecture in terms of an L402-aware transport layer, dedicated protocol handler, persistent token store, pluggable Lightning backends, configuration, and event logging.
  • It also makes explicit that the client is designed to pay invoices through lnd, LNC, or Neutrino and to retry requests with Authorization: L402 <macaroon>:<preimage>.

5) Agent-oriented positioning

• URL: https://raw.githubusercontent.com/lightninglabs/lnget/master/README.md
• Key excerpt:
  • The README explicitly says AI agents need a seamless way to consume paid APIs without human intervention and presents lnget’s automatic payment flow, token caching, cost controls, and JSON output as the answer.
  • That agent-facing framing is a strong clue that lnget should be cataloged as machine-commerce client infrastructure rather than as a niche Lightning wallet helper.

Working conclusion

lnget is best cataloged as a client-side paid-API and payment-authorization tool for the Lightning ecosystem. The decisive evidence in this pass was the recurring combination of automatic L402 challenge handling, pluggable Lightning backends, per-domain token caching, programmatic output modes, explicit cost guardrails, and the bundled dashboard/API surface for spending visibility. The key distinction is that lnget packages the buyer-side operating layer for repeated machine access to monetized HTTP endpoints instead of merely demonstrating one payment flow.