Official SDK · Python
x402 Django SDKDjango (Python ≥3.10)
Thin x402 payment-gate middleware for Django. Implements the frozen X402v1 wire contract. No payment logic in your app; relays to the platform's signed challenge/verify and fails closed (502, never serves paid content if the platform is unreachable).
Source is public on GitHub — official registry packages (npm · PyPI · Packagist · Go · Maven Central · NuGet · RubyGems) are coming. Each SDK implements the same frozen X402v1 wire contract.
Pay-per-call for Django views with one middleware.
- 01Create an account & register a route
In the dashboard, add the route + price and issue a test or live API key.
- 02Install the SDK
One package; the per-SDK command is below.
- 03Add one middleware
Wrap the route — it now returns a signed x402 challenge and only serves paid content after the agent pays in USDC.
pip install x402-djangoPackage id: x402-django
# settings.py
MIDDLEWARE = [
# ...
"x402_django.X402Middleware",
]
X402_ROUTE = "/premium"
X402_PRICE = "0.10"| X402_API_KEY | your key id | Identifies the key (from the API Keys page). |
| X402_SECRET | shown once | HMAC signing secret — shown once on key creation, stored encrypted. |
| X402_ENV | sandbox | live | sandbox = test key (synthetic settlement); live = real on-chain USDC. |
| X402_BASE_URL | https://api.payrelayer.com | Platform base URL the SDK calls. |
Use a test key with X402_ENV=sandbox: payments settle synthetically so you can build and CI-assert the full challenge → pay → verify → allow loop with zero real USDC, then flip to a live key — no code change.
- Thin client — no settlement, custody, or crypto code runs in your process. Keys, fees, the on-chain 95/5 split and payouts all live on the platform; you add one middleware.
- Fails closed — if the platform is unreachable the gated route returns 502 and never serves paid content. It cannot accidentally give away a paid response.
- One frozen wire contract — X402v1 is byte-identical across all 9 SDKs, enforced by a shared known-answer signature test, so behaviour can't drift between languages.
- Signed, retried webhooks (payment.settled, payout.sent, payout.failed) + a live dashboard of requests, balances and payouts — reconciliation is done for you.
- Django middleware class via settings.
- Python ≥ 3.10.
No. The SDK is a thin HTTP client. Settlement, the 95/5 split and payouts happen on-chain on the platform side; you add one middleware and read the result.
No. It fails closed — if the platform is unreachable the gated route returns 502 and never serves the paid response.
Use a test/sandbox key (X402_ENV=sandbox). Payments settle synthetically end-to-end; flip to a live key when you're ready, with no code change.
Yes. X402v1 is a frozen wire contract, byte-identical across all 9 SDKs and enforced by a shared known-answer signature test.
No — separate package (x402-django); same frozen X402v1 contract, byte-identical signing.