Recipes are short, goal-shaped walkthroughs that combine [Bot protection](/docs/bot-protection) and [Lidar](/docs/concepts/lidar) to stop a specific kind of abuse. Each recipe names the threat, the pieces you use, the setup, and how to verify it before relying on it.

## Recipes

- [Prevent signup and free-trial abuse](/docs/recipes/prevent-signup-abuse): stop automated account creation and trial farming.
- [Stop credential stuffing](/docs/recipes/stop-credential-stuffing): blunt list-testing against your sign-in.
- [Stop MFA fatigue](/docs/recipes/stop-mfa-fatigue): cap MFA push bombing against a single user.
- [Detect impossible travel](/docs/recipes/detect-impossible-travel): flag sign-ins that cannot be physically real.

## Prerequisites

Every recipe assumes you have:

- A [project and environment](/docs/concepts/multi-tenancy) you can configure without affecting production.
- [Lidar access](/docs/console/lidar) approved for the environment, where a recipe tunes a monitor.
- A reCAPTCHA site (v3 or v2) registered with the domains that serve your auth pages, where a recipe uses [Bot protection](/docs/bot-protection).

Recipes fail closed on the bot-protection side and only raise Signals on the Lidar side; neither blocks legitimate users on its own when configured in a non-production environment first.

## Related

- [Bot protection](/docs/bot-protection): reCAPTCHA add-on reference.
- [Lidar concepts](/docs/concepts/lidar): monitors, detectors, and Signals.
- [Lidar in the console](/docs/console/lidar): enable access and triage Signals.
- [Security](/docs/security): platform defaults behind these controls.