# Requestway

> Requestway is a free analytics dashboard for the x402 payment protocol. APIs that charge AI agents and other HTTP clients with x402 report each payment outcome (settled, failed or observed) to Requestway, and their developers see earnings, per-route activity, failures and observe-mode demand. Requestway is not a payment service: it never holds, moves or settles funds, and it does not receive payer or wallet identity.

Key facts:

- Free. No plans, no billing, no paid tiers.
- Install for Laravel: `composer require requestway/laravel-x402`, then set `X402_PLATFORM_KEY=rw_live_…` in `.env` and run a queue worker.
- Install for Node 20+: `npm install @requestway/reporter`, set `REQUESTWAY_KEY`, and call `settled`, `failed` and `observed` from the hooks of `@x402/express`, `@x402/next` or `@x402/hono`. On serverless, pass `waitUntil` or `await rw.flush()`.
- Ingest endpoint: `POST https://api.requestway.com/x402/events` with `Authorization: Bearer <project key>` and a JSON body `{"source": "...", "events": [{"type", "at", "payment": {...}}]}`. Event types: `payment.settled`, `payment.failed`, `payment.observed`. Amounts are strings. Up to 500 events and 1 MB per request; returns 202.
- Each project has a live key (`rw_live_`) and a test key (`rw_test_`).
- Endpoint tester: Requestway can call a developer's paid route, read the 402, pay it with test USDC on Base Sepolia (EIP-3009), check settlement and confirm the app's report. It never pays on mainnet; mainnet endpoints get their 402 validated only.
- Analytics are split into Mainnet and Testnet by each event's network; the dashboard follows whichever the app reports from.
- Query strings are discarded on arrival. Raw events are kept 30 days; daily totals until deletion.
- Figures are analytics, not accounting records. Reporting is best-effort.

## Pages

- [Home](https://requestway.com): what Requestway is, what it collects and what it doesn't, FAQ
- [What is x402?](https://requestway.com/x402): the HTTP 402 payment flow, headers, USDC and EIP-3009, facilitators and testnets, explained for developers
- [Install guide](https://requestway.com/docs): Laravel and Node setup, the endpoint tester, mainnet and testnet views, live and test keys, troubleshooting, the ingest API and limits
- [Articles](https://requestway.com/articles): practical guides to x402 and AI agent payments ([RSS](https://requestway.com/articles/feed.xml))
- [Sign up](https://requestway.com/register): create a free account (GitHub or email)

## Articles

- [A checklist for moving an x402 API from testnet to mainnet](https://requestway.com/articles/x402-testnet-to-mainnet): A step-by-step checklist for moving an x402 API from testnet to mainnet, covering wallet, network, facilitator, replay cache, alerts and the first real payment.
- [How AI agents pay for APIs: wallets, signatures and facilitators](https://requestway.com/articles/how-ai-agents-pay-for-apis): How AI agents pay for APIs with x402: the wallet, the EIP-3009 signature and the facilitator explained step by step, with client code and the safety limits.
- [How to add x402 payments to a Laravel API, step by step](https://requestway.com/articles/add-x402-payments-to-laravel): Add x402 payments to a Laravel API with requestway/laravel-x402: install, price routes, test without a wallet and prepare for mainnet, step by step.
- [Observe mode: measuring what agents would pay before you charge](https://requestway.com/articles/x402-observe-mode): Use x402 observe mode to measure what AI agents would pay per route before you charge: setup in Laravel and Node, the queries, and how to read them.
- [Pricing an API for AI agents: per-request pricing explained](https://requestway.com/articles/pricing-an-api-for-ai-agents): Pricing an API for AI agents per request: how x402 prices work in atomic units, how to set fixed, tiered and dynamic prices, and how to test demand first.
- [Testing x402 payments on Base Sepolia without spending real money](https://requestway.com/articles/test-x402-payments-base-sepolia): Test x402 payments on Base Sepolia for free: fake facilitators in unit tests, test USDC from the Circle faucet, a real paid call and receipt checks.
- [What HTTP 402 Payment Required means and how x402 uses it](https://requestway.com/articles/http-402-payment-required): What the HTTP 402 Payment Required status code means, why it sat unused for decades, what a 402 looks like with x402 today, and how clients should handle one.
- [What to charge AI agents for and which endpoints to put behind x402](https://requestway.com/articles/what-to-charge-ai-agents-for): How to decide what to charge AI agents for, which API endpoints belong behind x402, which to keep free, and how to test your choices before charging anyone.
- [What x402 facilitators do and how to choose one](https://requestway.com/articles/x402-facilitators-explained): What an x402 facilitator does at each step of a payment, what it can never do with your money, and how to choose one for testnet, mainnet or self-hosting.
- [Why x402 payments fail: the common errors and how to fix them](https://requestway.com/articles/why-x402-payments-fail): Why x402 payments fail, stage by stage: the real error codes, what causes each one, and the concrete fix on both the client side and the server side.
- [x402 vs API keys and subscriptions: when pay-per-request makes sense](https://requestway.com/articles/x402-vs-api-keys-and-subscriptions): x402 vs API keys and subscriptions, compared fairly: where pay-per-request wins, where keys and plans are better, and how to run both on one Laravel API.
- [x402 with Express, Next.js and Hono: a practical guide](https://requestway.com/articles/x402-express-nextjs-hono): Add x402 to Express, Next.js and Hono with the official v2 packages: one shared resource server, route config, a paying client and outcome hooks.

## Packages

- [requestway/laravel-x402](https://github.com/requestway/laravel-x402): x402 payments for Laravel 12 and 13, with optional reporting to Requestway
- [@requestway/reporter](https://github.com/requestway/reporter): zero-dependency Node reporter for x402 payment events; a reporter, not a payment library

## Legal

- [Terms of Service](https://requestway.com/terms)
- [Privacy Policy](https://requestway.com/privacy): exactly which fields are received, what is discarded, retention and sub-processors
- [Cookie Policy](https://requestway.com/cookies): essential session and CSRF cookies only

## Optional

- [Dashboard](https://requestway.com/projects): requires sign-in