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
Tenant API access provides a text request example from the saved default route. The example contains a key placeholder.
How it works
- Select a tenant and save its text default.
- Open API access in the tenant details.
- Create a tenant API key and copy its one-time value.
- Copy the text request example and replace its key placeholder outside the dashboard.
Feature-to-benefit table
| Feature | Why it matters here | Example |
|---|---|---|
| Generated-secret placeholder | Examples use <generated-secret>, including after explicit API key creation. | Raw client keys never enter example markup. |
| Separate one-time key | The newly created key appears in a read-only field with a copy action. | Users substitute it for the placeholder outside the page. |
| Saved route context | The text example includes the saved provider and model. | The API reference documents other request forms. |
Use-case examples
First run
A user connects a provider, saves a text default, creates a tenant API key, and copies the request example.
After creation
The example still contains <generated-secret> so the raw client key is not copied implicitly.
Default change
Saving a DeepSeek text default changes the provider and model in the next request example.
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
Examples use the <generated-secret> placeholder.Verified 2026-09-10 by Tyemirov on GitHub against docs/tenant-connections.md.
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 dashboard uses the runtime configuration for the proxy origin and the tenant profile for the saved default route.
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.
Where are dictation request examples documented?
The API reference documents dictation requests. Tenant API access shows the saved text route example.
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