Environments

An environment is one isolated tenant of metrics and data. Every event carries its environment ID, which routes it to the right place and keeps one team's data separate from another's. A common split is one environment per stage (dev, staging, prod) or per team.

Environment ID vs API key

Attribute	API key	Environment ID
Purpose	Authentication	Data routing
Secret	Yes	No
Sharing	Never share	Safe in configs
Scope	Per-account	Per-team or per-stage

Both travel together in one header: X-10X-Auth: <API_KEY>/<ENV_ID>.

Managing environments

Create and manage environments from the MCP, with no console trip:

Task	Tool
List reachable environments	log10x_login_status, log10x_discover_env
Create one	log10x_create_env
Rename or set default	log10x_update_env
Edit routing config	log10x_configure_env
Delete one	log10x_delete_env

Each call maps to the Manage REST API; the MCP is a wrapper over the same /api/v1/user/env endpoints.