Model choice
Update the saved configuration as your application's requirements change, while keeping the same ASK request interface.
Open provider settings All products Your model.
Model provider keys
Your model.
Your provider key.
Choose the provider and model that help turn natural-language questions into database queries.
Connect a model to ASK.
Save model settings for your instance, then use the same ASK endpoint from your application.
Your OriginChainDB instanceSaved configuration
Provider key
•••• •••• ••••
Encrypted in storage
Used on the server Your application’s question
/askQuery compiler
Rules and cached plans can avoid a model call.
The dashboard displays a masked key.
Only when a model is neededQuestion + model request
Selected provider
Your chosen model
Helps translate the question into a query plan.
Plan returned to the engineChoose your provider
Select an available provider and model, add your key and save the settings for your instance. Connection options depend on the selected provider.
Use it when needed
ASK uses the enabled provider when a question needs model assistance. Built-in query rules and cached plans can avoid a model call.
Model availability depends on the provider and instance configuration. Disabling BYOK returns ASK to the engine's default configuration.
See how ASK worksWhy connect your provider?
Managed credentials
Your key is encrypted before it is saved. The dashboard shows only a masked value.
Manage your keyInspectable queries
Review the resulting plan alongside database rows to understand how the question was executed.
Inspect a query planA deliberate setup
Choose. Connect. Verify.
Decide which model should handle questions that need assistance, then verify it with a small query you can check.
Choose an available model
Review the provider’s supported models, account access and data-processing terms. Use a model available in your instance’s provider catalogue.
Save the configuration
Add the provider key in instance settings. Supply any endpoint options the selected provider requires. Keep credentials out of application source code.
Review a first result
Send a focused ASK request with plan inspection enabled. Check its tables, filters and returned rows before relying on it in a workflow.
Keep control as requirements change
Manage the key.
Understand the next request.
Provider credentials and database credentials serve different purposes. Changing your model key changes the model connection; your application still uses ASK.
Review the ASK contract- Replace the saved key
- Subsequent requests use the updated provider configuration.
- Disable BYOK
- Keep the saved configuration, while ASK uses the engine’s default model settings.
- Remove the configuration
- Delete the saved connection and return to engine defaults. This does not revoke the key at the provider.
Check model charges and limits with your provider. Database pricing is separate.
Put it to work.
Build with ASK
Scope questions to registered tables and request a plan when reviewing query behaviour.
Read the ASK guidePlan your costs
Provider terms apply when using your credentials. Review database pricing separately from model usage.
Review database pricing