Whatever message this page gives is out now! Go check it out!
Anthropic- LLM configuration field reference
Last update:
May 18, 2026
This document describes settings for the Anthropic provider in the LLM configuration UI: basic connection, model parameters, proxy, and advanced options.
Behavior notes
- Leaving numeric or optional text fields blank uses the provider or integration default for that parameter.
- API key and logging fields include inline security guidance in the descriptions below (suitable for UI help text).
For official Anthropic concepts (models, Messages API, parameters), see Anthropic API documentation.
---
Basic configuration
Field | Description |
|---|---|
Config alias | Required. Unique name for this configuration. Use only letters, numbers, hyphens, and underscores (for example claude-sonnet-prod). |
Provider | Anthropic. The provider for this saved configuration. |
Model name | Required. The model id your client sends to the Anthropic API (for example claude-sonnet-4-20250514 or another documented model). Use the exact string your API version and account support. |
API key | Optional. Leave blank to supply the key at runtime. If you enter a key, it is stored with this configuration—treat it as a secret and follow your organization’s access and rotation rules. Create and rotate keys in the Anthropic Console or your team’s secret store. |
Base URL | Optional. Use Anthropic’s default API base unless you use a proxy, VPC endpoint, or compatible gateway. When set, use the root URL your HTTP client expects for Messages (or other) requests. |
---
Model parameters
These map to generation options supported by the Anthropic API for your selected model.
Field | Description |
|---|---|
Temperature | Leave blank to use the default. When set, use 0 or greater. Higher values increase randomness; allowed ranges depend on model and API version. |
Max tokens | Leave blank to use the default. When set, enter a positive integer for the maximum number of tokens in the assistant response (subject to model output limits). |
Top P | Leave blank to use the default. When set, use 0 or greater (often 0–1). Nucleus sampling; adjusts how the model samples from the token distribution. |
Top K | Leave blank to use the default. When set, use a non-negative integer to limit how many of the highest-probability candidate tokens are considered at each step. |
Response format | Default or structured output when your integration requests JSON or another supported response mode. Leave Default unless your workflow requires structured parsing. |
Stop sequences | Optional. Comma-separated sequences that stop generation when they appear in the output (for example END or newline tokens your API accepts). |
---
Proxy settings
Field | Description |
|---|---|
Proxy host | Optional. HTTP proxy hostname or IP. If you set a host, you must set Proxy port. |
Proxy port | Optional. Integer from 1 through 65535. Required when proxy host is set. |
Proxy username | Optional. User name for proxy authentication. Leave blank if the proxy does not require credentials. |
Proxy password | Optional. Proxy password. Stored credentials are sensitive—follow your organization’s secret-handling rules. Leave blank if not required. |
---
Advanced settings
Field | Description |
|---|---|
Max retries | Leave blank to use the default. When set, enter a positive integer for how many times to retry a failed request (rate limits, transient network errors). |
Timeout (seconds) | Leave blank to use the default. When set, enter a positive integer for the maximum wait time per request. |
Log API requests | When enabled, request details are written to logs. Requests can include prompts, headers, and metadata—use only while troubleshooting and disable afterward. Follow your organization’s logging and privacy requirements. |
Log API responses | When enabled, response details are written to logs. Responses can contain generated text and personal data—use only while troubleshooting and disable afterward. Follow your organization’s logging and privacy requirements. |
---
Parameters not shown on the default Anthropic screen
Your full parameter matrix may include Anthropic-only options (for example beta flags, prompt caching, or extended thinking controls). Document those in the same style when your UI exposes them: defaults when blank, valid ranges, and any compliance or cost implications. See
LLM_PROVIDER_PARAMETERS.md for the Anthropic column (Y / --).---
Related reference
- Parameter inventory and validation rules:
LLM_PROVIDER_PARAMETERS.md(Anthropic column: Y = supported, -- = not shown for that provider).
We're glad. Tell us how this page helped.
We're sorry. Can you tell us what didn't work for you?
Share additional feedback to help us improve.
0/255
|
