local402
A one-command paywall for local servers that enables testing AI agents' payment flows by simulating HTTP 402 Payment Required responses. It proxies requests with valid payment headers to the actual server, making it easy to develop and test x402 client logic without real blockchain transactions.
README
<div align="center">
๐ local402
One-command local paywall for AI agents
Turn any local server into a payable resource in seconds. Perfect for testing agents that need to pay before they can access your API or MCP tool.
<br />
<!-- Upload your demo clip to assets/demo.gif in this repo, then this renders automatically. -->

<br />
npx local402 --target http://localhost:3000 --price 0.001
<br />
Website ยท npm ยท Report a bug
</div>
What is this?
local402 drops an x402-style HTTP 402 Payment Required paywall in front of any local HTTP server or MCP tool โ with a single command, zero config, and no blockchain.
Requests without payment get a clean 402. Requests that "pay" get proxied straight through to your real server. That's it.
It runs in fully simulated mode by default: no wallets, no gas, no external services, no waiting. Just instant, deterministic 402s you can build and test against locally.
agent โโโถ local402 (402 paywall) โโโถ your server
โ
โโโ no payment? โ 402 Payment Required
paid? โ proxied response โ
๐ธ Why local402?
Agents are learning to pay for things โ API calls, tool invocations, data, compute. The x402 protocol makes HTTP-native payments real. But there's a gap:
How do you test a paying agent without spending real money, standing up a wallet, or wiring a whole payment stack โ every single time?
You don't want to deploy a facilitator and fund a testnet wallet just to check that your agent notices a 402 and retries with payment. You want a paywall you can throw up in one command and tear down just as fast.
That's local402.
| Without local402 | With local402 |
|---|---|
| Stand up a facilitator + wallet + testnet funds | npx local402 --target ... |
| Real transactions on every test run | Instant, free, deterministic |
| Blockchain latency in your test loop | 0ms โ it's all local |
| Payment logic tangled into your app | One reverse proxy in front of it |
| Hard to reproduce the "unpaid" path | Guaranteed 402 on demand |
Use it to:
- โ
Test that your AI agent handles
402and retries with anx-paymentheader - โ Demo a "pay-per-call" API or MCP tool without touching a chain
- โ Develop x402 client logic offline, on a plane, in CI
- โ Prototype pricing before committing to real settlement
โก Quick Start
You don't even need to install it.
# 1. Have any local server running (your API, MCP tool, whatever)
# e.g. something on http://localhost:3000
# 2. Put a paywall in front of it
npx local402 --target http://localhost:3000 --price 0.001
local402 is now listening on http://localhost:4020 and guarding your server.
# โ No payment โ 402 Payment Required
curl -i http://localhost:4020/
# โ
"Pay" โ request is proxied to your real server
curl -i http://localhost:4020/ -H "x-payment: simulated"
Point your agent at http://localhost:4020 instead of your real server, and watch it learn to pay. ๐
๐ Usage
local402 --target <url> [options]
| Flag | Alias | Default | Description |
|---|---|---|---|
--target <url> |
-t |
(required) | The server to protect, e.g. http://localhost:3000 |
--port <number> |
-p |
4020 |
Port local402 listens on |
--price <string> |
0.001 |
Price advertised in the 402 response |
|
--asset <string> |
USD |
Currency / asset label for the price | |
--simulate |
true |
Simulated mode โ no blockchain, instant (default) | |
--no-simulate |
Reserved for real x402 settlement (coming soon) | ||
--no-color |
Disable colored console output |
The rule
- No
x-paymentheader โ402 Payment Required(with a helpful JSON body + headers). - Has
x-payment: simulated(orpaid) โ request is proxied to--target, and the real response comes back untouched.
In simulated mode, any non-empty x-payment value is accepted โ simulated and paid are just the canonical ones.
Examples
# Guard an MCP tool on a custom port, charge 0.01
local402 --target http://localhost:8787 --port 9000 --price 0.01
# Free status check โ always open, never paywalled
curl http://localhost:4020/__local402
๐ How it works
local402 is a tiny reverse proxy with one opinion: pay first, then pass through.
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ local402 โ
โ :4020 (paywall) โ
โโโโโโโโโโโ โ โ โโโโโโโโโโโโโโโโ
โ agent โ โโโโโโโโถ โ x-payment header present? โ โ your server โ
โ / curl โ โ โ โ :3000 โ
โโโโโโโโโโโ โ NO โโถ 402 Payment Required โ โโโโโโโโโโโโโโโโ
โฒ โ โ โฒ
โ โ YES โโถ proxy the request โโโผโโโโโโโโโโโโโโโโโโ
โ โ return real response โ โ
โโโโโโโโโโโโโโโโโคโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโโ
402 or proxied response โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The unpaid response (HTTP 402):
{
"x402Version": 1,
"error": "Payment Required",
"message": "This resource costs 0.001 USD. Retry with header 'x-payment: simulated'.",
"accepts": [
{
"scheme": "simulated",
"network": "local",
"maxAmountRequired": "0.001",
"asset": "USD",
"payTo": "local402-simulated",
"resource": "/",
"description": "local402 simulated paywall",
"mimeType": "application/json"
}
],
"hint": "x-payment: simulated"
}
Response headers on a 402:
HTTP/1.1 402 Payment Required
x-payment-required: true
x-payment-amount: 0.001
x-payment-asset: USD
x-payment-network: local
accept-payment: x-payment: simulated
On a paid request, local402 attaches a simulated settlement receipt so your client can verify the flow end-to-end:
x-payment-response: <base64 JSON receipt with a sim txHash>
๐บ Roadmap
local402 starts simple on purpose. The plan:
- [x] v0.1 โ Simulated mode. Instant, local, blockchain-free
402paywall. (you are here) - [ ] v0.2 โ Real x402 settlement. Verify actual
X-PAYMENTpayloads via a pluggable facilitator. - [ ] v0.3 โ MCP-native mode. First-class paywalling for MCP tools/resources, not just HTTP.
- [ ] v0.4 โ Per-route pricing. Different prices for different paths and methods.
- [ ] v0.5 โ Usage dashboard. Live TUI of requests, payments, and revenue.
Want to shape it? Open an issue.
๐ค Contributing
Contributions, ideas, and bug reports are all welcome โ this is meant to be a friendly little tool.
git clone https://github.com/wushu75/local402.git
cd local402
npm install
npm run dev -- --target http://localhost:3000 # run from source
npm run build # compile to dist/
- Fork it ๐ด
- Create a branch (
git checkout -b feat/amazing-thing) - Commit your changes (
git commit -m 'feat: amazing thing') - Push and open a PR
No contribution is too small โ even a typo fix helps.
๐ License
MIT ยฉ the local402 contributors. Do whatever you want with it.
<div align="center">
โญ Star the repo if this is useful
If local402 saved you from standing up a payment stack just to test an agent,
drop a star โ it genuinely helps other people find it.
<br />
Built for the agents that pay their way. ๐
</div>
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.