# Recuut developer documentation (/)

Recuut checks payment before your application returns an API response or other digital resource. Choose the job you need to do.

- [Understand Recuut](/guides/concepts/how-recuut-works/) — Learn the payment model, prices, revisions, x402, and the request lifecycle before choosing an integration.
- [Build with HTTP](/guides/http/) — Follow a full direct-HTTP guide from a new test resource to a paid x402 retry.
- [Use an SDK](/sdks/) — Read Python client, generated contract, FastAPI, and Django documentation.
- [Inspect the Merchant API](/api-reference/) — Look up generated endpoints, fields, responses, and canonical cURL examples.

## Start with the right question

Concepts explain the product without choosing a programming language. Guides are complete vertical slices: create test data, start an endpoint, see an unpaid `402`, make a paid retry with an x402-compatible test wallet, and inspect the completed transaction. SDK documentation explains maintained libraries and framework integrations. The separate API Reference is the exact backend-owned contract.

Start with [how Recuut works](/guides/concepts/how-recuut-works/), follow the [direct HTTP guide](/guides/http/), explore the [Python SDK](/sdks/python/), or browse the [Merchant API Reference](/api-reference/).