Settings

Update user-account metadata: analyzer cost ($/GB used for cost-driver math), AI provider settings, display name. PATCH-like semantics — existing fields not in the payload are preserved.

Example

You

set my Datadog cost to $2.50/GB

Log10x

Updated. analyzer_cost is now 2.5. Every cost-driver call without an explicit analyzerCost= arg uses this from now on.

More to ask

• "switch AI provider to anthropic, key in ANTHROPIC_API_KEY"
• "disable AI"
• "rename my account to acme-platform"

Prerequisites

Signed in — see Sign in.

Schema and samples

Input example

Real call against the demo env (captured by scripts/capture-tool-envelopes.mjs).

{
  "metadata": {
    "analyzer_cost": 3
  }
}

Input schema

Agent-facing JSON Schema (the canonical shape the MCP server publishes via tools/list):

{
  "type": "object",
  "properties": {
    "metadata": {
      "type": "object",
      "additionalProperties": {},
      "description": "Object of metadata key/value pairs to update on the user account. Common fields: `analyzer_cost` (number, $/GB SIEM cost used for cost-driver math); `ai_provider` (`openai` | `anthropic` | `xai` | `custom` | empty for Log10x-managed); `ai_api_key` (string, BYOK); `ai_endpoint` (string); `ai_model` (string); `ai_temperature` (number 0-1); `ai_disabled` (boolean, true to disable AI entirely); `company` (string display name). The backend persists arbitrary keys, so additional documented fields can be passed through. Existing fields not in the payload are preserved (PATCH-like semantics on the backend)."
    }
  },
  "required": [
    "metadata"
  ],
  "additionalProperties": false
}

Source: src/tools/update-settings.ts.

Output example

Real envelope from the demo env. view: "summary" returns the full StructuredOutput with typed data. Long arrays + base64 PNG bodies trimmed for readability; the real call returns them in full.

Headline (the 1-line agent-facing answer):

Updated 1 setting for alice@acme.example.

{
  "schema_version": "1.0",
  "schema_epoch": "2026-05-25",
  "tool": "log10x_update_settings",
  "view": "summary",
  "summary": {
    "headline": "Updated 1 setting for alice@acme.example."
  },
  "data": {
    "ok": true,
    "username": "alice@acme.example",
    "fields_updated": 1,
    "redacted_keys": []
  },
  "generated_at": "2026-05-26T00:00:00.000Z"
}

Output schema

The data block inside the StructuredOutput envelope:

interface ToolData {
  ok: boolean;
  username: string;
  fields_updated: number;
  redacted_keys: unknown[];
}

Envelope-level fields the agent should also read: summary.headline (1-line answer), actions[] (next-call chain hints as {tool, args, reason}), truncated: boolean, images[] (PNG attachments where applicable), schema_epoch (engine-ID stability boundary).

Next: Rotate key