LLM Provider
Precision Bridge can route requests to a Large Language Model (LLM) of your choice to power AI-assisted features. The LLM Provider preferences screen lets you select a provider, pick a model, store an API key, and verify the configuration with a single test call.
When to Configure an LLM Provider
An LLM provider is optional. Configure one if you want Precision Bridge to use AI-assisted functionality. If no provider is configured, AI features remain disabled and the rest of the application is unaffected.
How to Configure a Provider
- Open Precision Bridge in your browser
- Navigate to Preferences from the main navigation menu
- Select LLM Provider under the AI section in the sidebar
- Choose a provider from the Provider dropdown
- Enter the Model identifier as expected by the provider (for example,
gpt-4o-minifor OpenAI,claude-sonnet-4-6for Anthropic) - Paste the API Key issued by the provider
- If you need to override the default endpoint (for example, to target Moonshot's China region), enter the API Base URL
- Click Test Connection to verify that the provider, model, and credentials work
- Click Save to persist the configuration
Supported Providers
The Provider dropdown surfaces OpenAI, Anthropic, Google Gemini, and Moonshot. If you need a provider that is not listed, contact help@precisionbridge.net.
| Provider | Notes |
|---|---|
| OpenAI | GPT-4, GPT-4o, GPT-5, and o-series models |
| Anthropic | Claude 4 family (Opus, Sonnet, Haiku) |
| Google Gemini | Gemini via Google AI Studio |
| Moonshot | Kimi K2 and Moonshot models. Defaults to the international endpoint (https://api.moonshot.ai/v1); set the API Base URL to https://api.moonshot.cn/v1 to target the China region. Kimi K2.5 and kimi-k2-thinking* models enable reasoning by default, which is incompatible with the structured outputs that AI-driven features rely on; Precision Bridge disables thinking on calls to these models so they still work. The model still uses its full weights but skips the chain-of-thought step |
Model Identifiers
After selecting a provider, the Model field offers a curated list of common models for that provider. Pick one to populate the field. If the model you want is not in the list — a fine-tuned model, or a release Precision Bridge has not yet surfaced — select Custom... and type the identifier directly.
Enter the model name as the provider expects it (for example, gpt-4o-mini for OpenAI, claude-sonnet-4-6 for Anthropic). If you paste an identifier that includes a leading provider prefix (such as anthropic/claude-sonnet-4-6) the prefix is stripped when it matches the selected provider.
API Base URL
The API Base URL field is optional for every supported provider. Each one has a global default endpoint that Precision Bridge uses when the field is left blank. Override only when targeting an alternate region (such as https://api.moonshot.cn/v1 for Moonshot's China region), routing through a corporate proxy or self-hosted gateway, or pointing at a private deployment.
API Key Storage
API keys entered in this screen are encrypted at rest using the same AES key store as other Precision Bridge credentials (such as connection passwords). They are written to the Precision Bridge preferences file in encrypted form and decrypted in memory only when an LLM request is made.
Note: Anyone with read access to the Precision Bridge data volume could still observe the encrypted key. Treat the data volume as sensitive and limit access accordingly.
Testing the Configuration
The Test Connection button sends a short prompt to the configured provider and reports the response. The values you have entered are used directly for the test, even before you click Save, so you can validate a configuration without persisting it first.
A successful test displays the model's response. A failed test displays the error reported by the provider — common causes include an invalid API key or a model name the provider does not recognise.
Troubleshooting
Authentication errors
Verify that the API key is correct and has not expired.
Model not found
Confirm the model identifier matches the provider's naming convention.
Connection works in another tool but not in Precision Bridge
If the provider is reachable only via a corporate proxy that performs SSL inspection, upload the proxy's CA certificate under Preferences > SSL Certificates.
Comments
0 comments
Please sign in to leave a comment.