Management UI
Copyable LLM curl examples from current profile data
Render copyable LLM curl examples from live profile data while keeping the one-time raw client key out of page markup and copied commands.
Users onboarding themselves to LLM Proxy through the management UI.
The problem
Docs and examples drift when they hardcode hosts, provider choices, or secret placeholders that do not match the signed-in user's state.
How LLM Proxy helps
LLM Proxy Settings renders copyable examples from profile data while keeping raw client keys out of example markup and clipboard actions.
How it works
- Open Settings after signing in.
- Expand Usage / Request examples.
- Copy default text, default /v2, or default dictation examples.
- Select a provider to copy provider-specific text, /v2, and dictation examples when supported.
Feature-to-benefit table
| Feature | Why it matters here | Example |
|---|---|---|
| Generated-secret placeholder | Examples always use <generated-secret>, including after automatic client-key creation. | Raw client keys never enter example markup. |
| Separate one-time key | The newly created key appears masked in a read-only field with Show and Copy actions. | Users substitute it for the placeholder outside the page. |
| Provider-specific variants | Selected-provider examples include provider and model context. | Dictation examples appear only for dictation-capable providers. |
Use-case examples
First run
A new user copies the automatically created client key, saves a provider key, and then copies the default /v2 example.
After creation
The example still contains <generated-secret> so the raw client key is not copied implicitly.
Provider switch
Selecting DeepSeek updates provider-specific examples and hides dictation when unsupported.
Objections and limitations
- Examples are for proxy calls, not direct provider API calls.
- The generated secret is shown once; copy it when created.
- Examples depend on the API-served profile and config payloads.
Repository evidence
get exampleSecret() {
return EMPTY_SECRET_PLACEHOLDER;
}Verified 2026-07-22 by Tyemirov on GitHub against site/assets/llm-proxy/js/ui/requestExamples.js.
FAQ
What do copied curl examples use for the client key?
Every example uses the <generated-secret> placeholder. The user supplies the separately copied one-time client key when preparing the real request.
Where do example hosts and provider choices come from?
The Settings UI builds examples from the API-served runtime configuration and the current authenticated management profile instead of hardcoding deployment-specific values.
Can copying an example expose the raw generated key?
No. The generated value stays in its dedicated read-only field, while example markup and clipboard actions use only the placeholder.
When does a provider-specific dictation example appear?
It appears only when the selected provider supports dictation; text and /v2 examples remain available for configured text providers.
What should I read next?
A closely related resource is Authenticate an LLM Proxy client with a tenant secret, which covers LLM Proxy client authentication.
Related resources
Use this pattern in LLM Proxy
Start from the canonical API reference, then use the management surface when the workflow needs tenant or provider configuration.
Open API reference