The case for pay-per-request hosting

Static sites and content delivery have run on the same business model for two decades: monthly subscriptions, opaque tiers, account creation, and recurring billing. For a landing page that needs to live online for a year, or an archive that gets read by a few hundred people, the friction-to-use ratio is upside-down.

objekt.sh treats hosting as a metered utility. Every served request settles in USDC over x402 — the HTTP-native payment protocol — so consumption pays for itself, and no account, card, or contract is required.

How it works

Files are stored on decentralised infrastructure and served from a global edge. When a request lands, the gateway responds with HTTP 402 if no payment is attached; the requester (or a delegated wallet) pays the listed amount in USDC and the response is returned. Settlement is recorded on-chain and legible to the publisher.

For static-site use, the model collapses to: upload, get a URL, ship. There's no dashboard to manage, no plan to outgrow.

What it enables

• Ephemeral sites that go quiet cleanly when no one's looking, instead of burning a paid subscription forever.
• Archive hosting where the publisher pre-funds expected reads at a known per-request rate.
• Agent-served content — autonomous systems that need to publish or consume web content can do so directly, without onboarding through a SaaS provider.

Status

Documentation is live. Lighthouse uses objekt.sh as a reference for what coordination primitives can look like when payment is a first-class part of the protocol stack, not a billing afterthought.