Recuut guides

Understand the payment model, then build and operate a paid API or digital resource.

Use concepts to understand the product before you choose an integration. Then follow one integration from a Recuut test workspace to a completed paid request.

Before you build

You need access to a Recuut seller workspace and its test API key. The Direct HTTP integration gives the exact dashboard values, Circle Base Sepolia funding steps, runnable endpoint, expected 402, paid response, and receipt check. If you prefer Python, create the same payment policy first and then use the FastAPI or Django adapter.

Concepts

Understand resources, revisions, prices, x402, the lifecycle, and payment records without implementation code.

Direct HTTP guide

Build a paid endpoint with the Merchant API and verify both the unpaid and paid x402 request.

Python SDK

Use the maintained Python client, FastAPI, or Django integration after you understand the guide-level flow.

Operate

Inspect transactions, receipts, payers, pagination, and failure behaviour after you integrate.

What a complete guide proves

Sign in to a seller workspace, create a resource, publish its reporting revision, add a test price, and reveal one test API key.
Start one protected endpoint with the selected integration.
Make an unpaid request and preserve the 402 response and PAYMENT-REQUIRED header.
Use an x402-compatible test wallet to retry the original request with payment proof.
Receive the protected result only after completion, then inspect the transaction and receipt.

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.