> ## Documentation Index
> Fetch the complete documentation index at: https://docs.context.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Setting up Context.dev for a user? Follow https://docs.context.dev/agent-quickstart.md. Start by signing the user up and getting an API key through https://www.context.dev/auth.md; application code reads CONTEXT_DEV_API_KEY.

# Production checklist

> Prepare authentication, output handling, deadlines, and observability for production.

Start with a representative success case, a target that cannot be read, and an empty or partial result. Verify the behavior your product depends on before increasing traffic.

## Keep credentials on the server

Store keys in a secret manager and give each integration the [permissions](/account/api-keys) it needs. Keep source-site credentials out of application logs.

## Choose outputs and validate results

Combine the Scrape formats you need in one request. Check each output’s `success`; handle empty lists, missing Brand fields, and low-confidence People matches explicitly. Preserve user corrections outside refreshed API data.

## Set cache freshness

Choose freshness by workload. Use `maxAgeMs: 0` when a Scrape result must reflect a new visit; accept older data for infrequently changing pages. See [Scrape caching](/scrape/freshness-and-caching) and [Brand options](/brand/overview#options).

## Bound work and retries

Set [API and client timeouts](/optimization/timeouts), restrict crawl scope, and cap concurrent work. Honor `Retry-After` after 429. Retry transient failures with bounded exponential backoff and jitter; fix invalid inputs before retrying.

Use an idempotency key for [batch submission](/batches/submit#idempotency). Monitor [webhook deliveries](/webhooks#delivery-history-and-replay) and deduplicate events before applying changes.

## Reduce transfer size

Request only needed outputs and apply [content filters](/scrape/content-filtering). Avoid preserving base64 images in Markdown unless needed. Use `Accept-Encoding: gzip` or your client’s compression support; SDKs generally decompress responses automatically.

## Observe the integration

Record `request_id`, latency, response status, and stable error codes. Use [tags and logs](/optimization/usage-and-logs) to locate regressions without retaining unnecessary page content. Test [ZDR confirmation](/optimization/zero-data-retention#confirm-zdr-was-honored) when using retention controls.

Pin SDK versions, review the [changelog](/changelog), and follow the [API stability policy](/optimization/trust#api-versioning) when upgrading.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.