# Set up your product (/guides/setup)

Every integration starts from a published revision with a Price and a merchant test key. Create them for your own product; each step also names the text-generation example that the guides use.

[Sign in to the recuut app](https://app.recuut.com/). If your account has no workspace, create one when prompted; if access is unavailable, ask your recuut contact for an invitation before continuing.

In the recuut app:

1. Open **Resources**, choose **Create resource**, and name the API endpoint or digital item you sell. The guides use a Resource named **Text generation API**.
2. Open the Resource and choose **Create revision**. Add one variable for each quantity you price or record, with its unit and source: **Input** for values your server derives before the work runs, **Output** for values measured after it. Publish the revision. The guides use **Text generation v1**, with `input_tokens` read from the request and `output_tokens` returned by the handler, both in `token`.
3. Copy the published revision key beginning with `rvk_`.
4. Under **Revision pricing**, create and publish a Price in **USD**, then turn on **Require payment** for the revision. The guides use a fixed Price with a flat fee of **0.01**. [Pricing](/guides/concepts/pricing/) explains free, flat, and variable Prices.
5. Open **Organization → Environments**. Expand **Test credentials** if needed, choose **Reveal Test key**, then **Copy Test key**. Keep the key on the server only.

The revision key is generated by recuut. Yours will differ from examples in the API Reference. The guide examples use the text-generation names; with your own revision, use the names and variables you published.

To see a working paid endpoint first, [try an example](/guides/example/). For a Python application, [pull contracts](/guides/pull-contracts/) next, then protect a route with [FastAPI](/guides/fastapi/) or [Django](/guides/django/). For any other server stack, continue with the [Direct HTTP integration](/guides/http/).