Existing x402 tools
Already using x402 middleware or the official SDKs? Point them at Penni's facilitator URL with your API key.
Penni speaks standard x402 v2. Any server-side x402 middleware that lets you set a facilitator URL and request headers can use Penni:
| Setting | Value |
|---|---|
| Facilitator URL | https://api.pennipay.eu/v1/x402 |
| Authorization header | Bearer x402_sk_... (your site's API key) on verify and settle |
payTo | The wallet set for the site in the dashboard |
| Tokens | A token selected for the site: see networks and tokens |
The middleware adds /verify, /settle and /supported to the facilitator URL itself.
What Penni checks
Penni only verifies and settles payments for your own site. A request is refused with 403 when payTo isn't the site's wallet or the token isn't selected for the site, and with 401 without a valid key. This keeps a leaked key from being used to settle payments to someone else.
Prices from the dashboard
With your own middleware, prices usually live in your code. To manage them in the dashboard instead, fetch the ready-made accepts list for a path from the config API and pass it to your middleware.
Paying clients
Payers need nothing from Penni. Any x402 v2 client, such as @x402/fetch, the Python or Go SDKs, or an agent framework with x402 support, reads the 402 and pays.