SadaIQBuild on governed analytics through API and SDK
Embed charts, query metrics and automate workflows through interfaces that enforce permissions on the server.
Documented, versioned, and safe by default
Reference documentation describes each endpoint together with the permissions it needs. Because enforcement happens server-side and per tenant, what you embed behaves the same way as what users see in the workspace.
- Product teams want analytics inside their application but cannot copy data access rules into every new screen.
- Embedded components, the SDK, the public API or MCP access call SadaIQ, and permissions are enforced on the server per tenant.
- Embedded charts and API results that obey the same policies as the workspace and include evidence fields.
- Open the documentation and make a first authenticated request.
A chart for this role
A synthetic example of a question someone in this role asks.
Evidence trail from source to decision
How did this figure travel from its source to the decision built on it?
The trail shows six ordered stops from source to decision, each with a named reference; inspecting a stop reveals its definition and reference, and the text sequence remains as a complete alternative. Show table
Evidence trail from source to decision # Stage Unit Source 1 Source source fixture:synthetic-orders-v1 2 Connection connection connector:public-fixture 3 Unified metric metric metric:net_revenue@1.0.0 4 Governed query query plan:monthly-revenue 5 Chart chart scene:revenue-seasonality 6 Decision decision action:review-campaign