Start with a question.
Give people a way to explore tables using the words they use at work, with results returned from the database.
Ask AI
Turn a question about your tables into database results. Keep the selected data and executed query plan visible, so your team can understand the answer.
Help your team get closer to the records behind a decision.
Give people a way to explore tables using the words they use at work, with results returned from the database.
Choose relevant tables so the question is interpreted in the context your application intends.
Request the executed query plan alongside the rows to inspect the tables, filters and operations behind the answer.
A question with context
A clear question names the data, the condition and the result you want. Ask AI uses that context to compile a query against your registered tables.
Explore table scopingA scoped question with the query plan included in the response.
{
"nl": "Count records in activity.events",
"schemas": [
"activity.events"
],
"show_plan": true
}Illustrative request · use your own registered table Pass the table scope with your question. This gives the compiler a focused set of fields and relationships to consider.
Name the quantity, filter or grouping that matters. Split unrelated requests into separate questions.
Confirm the intended tables and conditions were used. Compare the result with familiar data before using it in an application workflow.
From a question to a feature
Send a question through the API, receive database rows and include the executed plan when you need to explain the result.
Recognized questions compile directly. Other questions can use the language model configured on your instance.
The response reports whether a plan was reused. Reuse depends on the schema and authorization context.
No. Matching cached plans can be reused, and built-in rules handle recognized questions. Questions that need model assistance are sent to the provider configured on your instance. Consider the question and selected data context when choosing that provider.
Yes. Set show_plan to request the executed plan with the result. It helps you
check the selected tables, filters and operations. The plan is returned after execution.
The compiler considers the catalog allowed by the active database identity. Giving it a relevant table scope reduces ambiguity, especially in a larger catalog.
Build with OriginChainDB