# Argentic bets AI scrapers will pay 10 sats for a proxy hop > Source: > Published: 2026-08-21 12:21:04+00:00 # Argentic bets AI scrapers will pay 10 sats for a proxy hop **The pseudonymous builder said the zero-cost prototype had no paying agents after seven weeks, a candid test of whether bots will pay instead of route around.** By [RuntimeWire Staff](/author/runtimewire-staff) ยท Published Primary source: [Argentic](https://argentic.network/) ## Why it matters Argentic exposes the central problem in agent payments: the transaction can work before the market does. Its builder must prove a paid proxy offers value when bots can route around it and publishers increasingly have their own HTTP 402 tools. An anonymous builder working under the name RevolutionaryTrash56 is testing a narrow idea with [Argentic](https://argentic.network/?ref=runtimewire): make an AI agent pay 10 satoshis over Bitcoin's Lightning Network, then give it an hour-long token for requests forwarded through Argentic's proxy. The builder's wager is that autonomous software will eventually find a tiny payment easier than opening an account, managing an API key or hunting for another route. ([argentic.network](https://argentic.network/?ref=runtimewire)) The candor behind the project matters as much as the payment flow. In [an earlier public discussion](https://www.reddit.com/r/defi/comments/1ul662v/built_a_machinenative_http_402_toll_booth_for_ai/?ref=runtimewire), the builder described Argentic as a zero-cost working prototype and wrote: "Mostly bots route around it for now. No paying agents yet, been live 7 weeks." The project had reached the web before it had found a market, giving its pseudonymous creator a clean test of whether agent payments are an approaching business model or another protocol waiting for demand. ([reddit.com](https://www.reddit.com/r/defi/comments/1ul662v/built_a_machinenative_http_402_toll_booth_for_ai/?ref=runtimewire)) ### A payment gate with a one-hour token Argentic's published flow begins when an agent sends the gateway a target URL. Argentic responds with the HTTP 402 "Payment Required" status, a Lightning invoice and a payment hash. The agent pays through its own Lightning node or wallet, polls Argentic using the hash and receives a session token. Requests carrying that token in an `X-Lightning-Token` header are forwarded for the next hour. ([argentic.network](https://argentic.network/?ref=runtimewire)) Argentic advertises settlement in under 40 milliseconds and values the 10-satoshi charge at roughly $0.001. Those are Argentic's figures, rather than results from an independent performance test. The homepage also contradicts itself on the unit being sold: its opening metrics say 10 sats "per request," while the protocol and pricing sections say one 10-satoshi payment buys a one-hour session. The code example supports the session interpretation because subsequent requests reuse the same token. ([argentic.network](https://argentic.network/?ref=runtimewire)) That distinction determines what Argentic has built. Its public implementation looks like a paid proxy hop. The agent pays Argentic for a gateway token, and Argentic forwards the request to the target URL. The payment does not itself buy a license or permission from the target publisher. A target site can still impose its own technical restrictions and usage terms. The builder's initial pitch is therefore aimed at agents that value convenience, rather than publishers looking to charge bots directly. Argentic says the token removes accounts and API keys from the transaction. Whether that convenience is worth even a fraction of a cent depends on what the proxy can reliably reach and how it handles failures. ### Argentic simplifies L402 Argentic describes the gateway as L402 infrastructure, but its documented exchange differs from the [Lightning Labs L402 specification](https://github.com/lightninglabs/L402/blob/master/protocol-specification.md?ref=runtimewire). The specification pairs a Lightning invoice with a macaroon, a credential that commits to the invoice's payment hash. After paying, the client presents the macaroon and payment preimage in an HTTP `Authorization` header. The server verifies that the preimage matches the hash before granting access. ([github.com](https://github.com/lightninglabs/L402/blob/master/protocol-specification.md?ref=runtimewire)) Argentic's example instead returns invoice and payment-hash fields in JSON, asks the client to poll with an `X-Payment-Hash` header and then issues its own session token. That can produce a simpler demonstration, but it means Argentic's public flow should be read as a customized implementation inspired by L402, rather than proof of compliance with the full specification. Argentic has not published an independent security assessment in the materials reviewed for this story. The thorniest product question appears after payment. A user in the earlier discussion raised the case of an agent that pays and is then blocked or fails to receive access. The builder's current answer is deliberately economical: at 10 sats, retrying costs less than building a full recovery system. The builder said a receipt and recovery path was on the roadmap and that the payment preimage could prove payment. ([reddit.com](https://www.reddit.com/r/defi/comments/1ul662v/built_a_machinenative_http_402_toll_booth_for_ai/?ref=runtimewire)) That tradeoff is reasonable for a prototype and becomes less comfortable as usage grows. Automated buyers need a predictable link between payment, the resource purchased, token issuance and expiration. Otherwise a cheap failure repeated across a fleet of agents turns into an accounting and reliability problem. Argentic's builder has reduced the first version to the smallest transaction that can test demand; recovery is the engineering work demand would force next. ### The payment rails are arriving before the customers Argentic is entering a busier field than its small footprint suggests. On February 11th, 2026, [Lightning Labs released agent tools](https://lightning.engineering/posts/2026-02-11-ln-agent-tools/?ref=runtimewire) for operating Lightning nodes, paying L402-gated endpoints and hosting paid services behind its Aperture reverse proxy. Its `lnget` client automates the invoice, payment and authentication sequence for agents, including reuse of cached credentials. ([lightning.engineering](https://lightning.engineering/posts/2026-02-11-ln-agent-tools/?ref=runtimewire)) Other payment companies are pursuing a broader set of rails. On March 18th, [Stripe introduced the Machine Payments Protocol](https://stripe.com/blog/machine-payments-protocol?ref=runtimewire), which supports agent payments through stablecoins as well as fiat methods. On June 15th, [Stripe and AWS announced an HTTP 402 capability](https://stripe.com/newsroom/news/aws-waf-and-stripe?ref=runtimewire) for publishers and content owners using AWS Web Application Firewall. In that model, the 402 response can carry pricing, payment options and license terms for the protected resource. ([stripe.com](https://stripe.com/blog/machine-payments-protocol?ref=runtimewire)) Those releases validate the problem Argentic's builder chose: software agents remain awkward customers for systems designed around human identities, cards and recurring subscriptions. They also raise the bar. Argentic must give an agent a reason to pay its intermediary when tools increasingly let the agent pay the resource owner directly. For now, Argentic is an unusually honest prototype. It has a functioning payment sequence, a price low enough to make experimentation painless and a builder willing to acknowledge that bots currently route around the booth. The next test is distribution. A toll booth becomes infrastructure only when it stands on a road agents already need to use.