recuut guides
Set up your product, protect an endpoint, test a paid request, and go live.
Set up your product, protect an endpoint, test a paid request, then prepare your live configuration. Python integrations also pull typed contracts; direct HTTP uses the revision key.
Get started
- Set up your product to publish a revision with a Price and copy a merchant test key.
- Pull contracts into a Python application. Direct HTTP uses the revision key instead.
- Protect an endpoint with FastAPI, Django, or direct HTTP, and confirm its unpaid
402. - Test a paid request with a Base Sepolia test wallet and verify its receipt.
- Go live: request business verification and prepare the Live revision. Live payments are not available yet.
After step 1, you can try an example: a generated FastAPI app for your revision that returns its first 402 without changing your own application. The recuut integration skill gives an AI coding agent the same path.
Concepts and operations
How recuut works explains the payment boundary, the paid request, and each server branch. Resources and revisions, Pricing, x402 payment instructions, and Test and live environments cover the rest of the model.
After you integrate, CI/CD, Transactions and receipts, Errors and retries, Payers, and Pagination cover day-to-day operation.
The API Reference is separate from these guides. Use it to look up exact fields and generated cURL examples, not to learn the product for the first time.