> ## 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. MCP clients sign in with OAuth and need no API key; application code reads CONTEXT_DEV_API_KEY.

# Usage and request logs

> Label requests and investigate their metadata, input, and results.

Use `tags` to group requests by environment, workflow, or customer account identifier. Keep secrets and personal data out of labels.

## Tag requests

For JSON endpoints, add:

```json theme={null}
{"tags":["production","site-import"]}
```

GET endpoints accept comma-separated `tags`, such as `production,site-import`. A request accepts up to 20 tags, each 1–50 characters. ZDR requests omit tags from retained logs.

## Inspect usage

The dashboard usage page filters charts and request logs together by key and tags. Monitors have persistent tags that label their runs and changes; request tags label a single API call.

## Read request logs

Use [List request logs](/api-reference/logs/list) with `logs:read`, then [Retrieve a request log](/api-reference/logs/retrieve) for retained input and response content. Available filters include key, route, status, time, and tags; the reference lists query syntax and pagination.

Entries include HTTP requests and synthetic `MONITOR` and `BATCH` rows for runs and settlements. Their `method` is not always an HTTP verb, and their `key_id` can be null.

Logs are kept for up to one year. Retained input and response fields redact recognized credentials; redaction does not remove every kind of sensitive content. [ZDR](/optimization/zero-data-retention) retains operational metadata only.

Save `request_id` with application errors so you can match them to the API logs and support reports.