Manage
Manage your 10x deployment lifecycle: API keys, environments, authentication, licensing, and the metrics the engine publishes. Drive it through the MCP env and auth tools or the REST API. API keys are minted by MCP sign-in.
-
API Key
Generate and rotate the per-environment key the MCP and REST API use.
-
Environments
Isolate metrics and data by team, project, or deployment stage.
-
Identity
Per-environment key for the engine; Auth0 device flow for the MCP.
-
License
The signed token the engine verifies offline, and the built-in evaluation license when there is none.
-
Status
What status.log10x.com monitors, and how to read it from your own monitoring.
-
Logging
Where the engine writes its own logs, and how to change path, appender, and rotation.
-
MCP Server
Cost attribution and pattern analysis for AI agents (Claude, Cursor, etc.).
Metric output
The engine publishes per-pattern cost and volume metrics to a time-series backend you own. That store is also the audit trail for what the engine did, held on your own infrastructure. Pick the output that matches your setup:
| Output | Use case | Configuration |
|---|---|---|
| Prometheus remote write | your own Prometheus, Grafana Cloud, Mimir, Thanos, VictoriaMetrics | Remote Write |
| Prometheus scrape | pull-based collection | Scrape |
| Push Gateway | batch or job workloads | Push Gateway |
| Datadog | an existing Datadog account | Datadog |
| Elastic | Elasticsearch or OpenSearch | Elastic |
| AWS CloudWatch | AWS-native monitoring | CloudWatch |
| Log4j2 | local files, no time-series database | Log |
No output is active until you pick one. Full reference: Metric Output.