Crypto data API where AI agents pay per request with USDC (x402)
x402 micropayments are clever, but the API is a thin wrapper around existing crypto data sources.
ElysiaJS plugin for the x402 Payment Protocol. Protect any route behind a crypto micropayment with a single .use() call.
One-liner x402 middleware for ElysiaJS; niche stack, nascent payment protocol adoption.
Bun/ElysiaJS developers building paid APIs or SaaS with crypto payments
Stripe Billing · Lemonsqueezy · Gumroad
What it does:
Lets you configure paid routes like "GET /api/weather" and enforce payment requirements (price, chain/network, recipient address).
If a client hits a protected route without a valid payment header, it returns 402 Payment Required describing what to pay; after payment, the request is allowed through and the handler runs.
Why I built it:
I wanted “pay-per-request” APIs in the Bun/Elysia ecosystem (same idea as existing x402 middleware in other frameworks, but native to Elysia).
I’m planning to use it to power paid endpoints in my own product (slaab.ai), but this repo is intended to be generally useful for any paid API.
How to try it:
Install: bun add @codingstark/x402-elysia
The README has a complete “Quick Start” showing .use(paymentMiddlewareFromConfig(...)).
Demo:
I also recorded a short video showing the flow (request → 402 → pay → retry → success): https://x.com/twitter/status/2027014126648672438
Feedback I’m looking for:
Does the configuration shape feel idiomatic for Elysia apps?
Any missing use-cases (multiple chains, paywall UX, internal bypass hooks) you’d want for production paid APIs?
x402 micropayments are clever, but the API is a thin wrapper around existing crypto data sources.
x402 middleware for REST APIs, but agent payments are still niche and early.
They revive HTTP 402 so agents can automatically buy API calls — the repo ships PayingClient/WalletManager primitives, an @x402-kit/core package, five agent templates (web-scraper, image-gen, search, translation, code-review), a live demo and 93 tests. Smart infrastructure play with a clear demoable surface; the hard part will be UX and economics (wallet funding, gas/settlement, and convincing API operators to adopt x402 instead of existing billing).
Biometric-gated payments let AI agents pay APIs without exposing private keys.
Agents finally have bank accounts: 402 interception + Lightning payments just works.
HTTP 402 Payment Required for autonomous agent micropayments in USDC.