Does iDBQuery have an API or SDK?

iDBQuery is not only an end-user app — it exposes an Embedded SDK so developers can put its capabilities inside their own software.

• Embed the querying engine. Add plain-language data chat, generated SQL, charts, dashboards and cited answers to your own product.
• Keep data local. The SDK is designed so data can stay within your environment rather than being shipped to a third party.
• Programmatic access. Drive questions and retrieve results from your application, so iDBQuery becomes a component of your stack rather than a separate destination users have to visit.

This is how product teams add self-serve analytics to their apps without building a text-to-SQL system, a semantic layer and a citation engine from scratch. For example, a vertical SaaS company could let its customers ask questions about their own account data, in-app, with every figure traceable to source rows — powered by the SDK rather than months of in-house engineering. Because iDBQuery is model-agnostic and deployable in your environment, embedding it does not force you to expose customer data to an external service. If your question is 'can I build this into my platform?', the answer is yes, and the SDK is the route.