402 200 Free analytics for x402
See what AI agents pay you.
Your API already charges agents with x402. Requestway shows you what they paid, per route and per day, and what they would pay on routes you haven't priced yet.
Free. No card, no plans. Works with Laravel and Node.
Market data API
Demo · simulated data- Earned today
- $18.42
- Would-be, observe mode
- $6.10
Two lines in .env.
If you charge with requestway/laravel-x402, you already have the package. Add your wallet and a project key and every settled, failed and observed payment is reported after the response is sent.
On Node, @requestway/reporter does the same next to @x402/express, @x402/next or @x402/hono, with zero dependencies.
.env
X402_PAY_TO=0xYourWalletAddress
X402_PLATFORM_KEY=rw_live_your_project_keyNode
npm install @requestway/reporterNew: endpoint tester
Pay your own API before an agent does.
Paste your paid route. Requestway calls it like an agent would: it reads the 402, signs a real payment with test USDC, retries, checks the settlement, then waits for your app to report it. Every step shows live.
-
A real testnet payment
Signed with EIP-3009 and settled by your own facilitator on Base Sepolia, so you know agents can actually pay you.
-
Never real money
Endpoints on mainnet get their 402 checked and nothing more. The tester can only sign on testnets.
-
Follows your config
Testnet payments land in a separate testnet view. Switch X402_NETWORK to mainnet and your dashboard flips with it.
GET https://api.example.com/premium-data
Testnet · Base Sepolia
How it works
Requestway sits beside your payments, never in them. It sees the outcome after your API has already answered.
-
01An agent calls your API
It gets a 402 with a price, signs a USDC payment and retries.
-
02Your API settles
Your x402 middleware verifies and settles through a facilitator. Money goes from their wallet to yours.
-
03The package reports
After the response, it posts the outcome in a batch. If we are down, your API doesn't notice.
-
04You see it here
Earnings per route, failures by reason, and demand on routes you're only observing.
What you get
-
Earnings per route
Daily revenue and which endpoints earn it, sortable, for 7, 30 or 90 days.
-
Demand you aren't charging for
Run a route in observe mode and see what agents would have paid before you set a price.
-
Failures, grouped
Every failed payment by stage and reason, most frequent first, so you fix the right thing.
-
A request log
Thirty days of raw events: route, price, network, transaction. Paginated and filterable.
-
Live and test keys
Staging traffic stays out of your real numbers. Keys are hashed and shown once.
-
An endpoint tester
Pay your own route with test USDC and watch each step of the 402 exchange, end to end.
-
Your data, any time
Export everything as JSON and CSV, or delete your account and all of it goes.
What we receive, and what we don't
Payment events come from your production app, so we keep them to the minimum an earnings dashboard needs.
We receive
- Event type (settled, failed, observed) and time
- Route label, HTTP method, host and path
- Price in USD, atomic amount, asset and network
- Your receiving address (
pay_to) - Request id and settlement transaction hash
- For failures: the stage and reason
We don't
- The payer, or any wallet other than yours. The packages never send it.
- Query strings. Discarded on arrival, before anything is stored.
- Request or response bodies, headers or cookies
- Your users' IP addresses
- Your funds. We never hold, move or touch money.
- Analytics or ad trackers on this site
Raw events are kept for 30 days; daily totals for as long as the project exists. Read the privacy policy.
Questions
Is it really free?
Yes. There is no billing in the product at all: no plans, no card, no usage tiers. We rate limit to keep it running for everyone.
Does it touch my money?
No. Payments go from the agent's wallet to yours through your facilitator. Requestway only receives a report of what happened, afterwards.
Will it slow down or break my API?
It is built not to. The Laravel package queues a batch after the response is sent; the Node reporter is fire-and-forget with a timeout and never throws. If Requestway is unreachable, events are dropped and your API carries on.
Are the numbers exact?
Treat them as analytics, not accounting. Reporting is best-effort: batches are capped at 100 events and dropped if delivery fails. Your wallet and facilitator are the record of what you were paid.
Who paid me?
We can't tell you, deliberately. The packages don't report payer or wallet identity, so neither do we. Your own app has that if you need it.
Which stacks are supported?
Laravel 12 and 13 through requestway/laravel-x402, and Node 20+ through @requestway/reporter alongside the official @x402 middleware. Anything else can post the same JSON to the ingest endpoint.
What is observe mode?
A setting in the Laravel package (X402_MODE=observe) that serves requests without charging and records what each would have cost. Requestway turns that into a would-be revenue figure per route.
What does the endpoint tester do?
It calls your paid route, reads the 402, signs a payment with test USDC from a Requestway wallet, retries, checks the settlement receipt and waits for your app to report it. It only ever pays on testnets such as Base Sepolia; for a mainnet endpoint it validates the 402 and stops.
How do I delete my data?
Delete a project, or your whole account, from the dashboard. Projects, keys, events and totals go with it, immediately. You can export everything first.