canonical: https://jentic.com/apis/alisqi.com/alisqi # AlisQI API Jentic publishes the only available OpenAPI specification for AlisQI API, keeping it validated and agent-ready. AlisQI is a quality management platform for manufacturers, and its API exposes analysis sets, lab results, specification versions, and capability statistics for tenant-specific deployments. Programs can pull descriptive statistics, push new lab results, define specification versions, and manage permissions on analysis sets. The API uses a tenant subdomain in the base URL and supports either bearer token or query-parameter access tokens. ## For AI agents Read and write quality management data in AlisQI - fetch lab results and statistics, push new measurements, and manage specification versions for a tenant. ## Scope Does not handle ERP transactions, document management, or production scheduling - use for quality measurement capture and SPC statistics only. ## Capabilities - Fetch results and master data from a named analysis set with filtering - Submit new or updated lab results into AlisQI in batch via storeResults - Retrieve descriptive and capability statistics for analysis set fields - Create new specification versions and read existing version history - Inspect the field structure of an analysis set or selection list - Provision new analysis sets and assign permissions to users or groups ## Use cases ### Automated lab result ingestion Push readings from inline sensors or LIMS exports straight into AlisQI by calling storeResults with the analysis set name and a batch of records. The API accepts master data alongside results, so production parameters and measurements land in the same payload. Typical integration takes hours rather than days because the spec is small and there is one write endpoint to learn. Example prompt: Call POST /storeResults with analysis set name 'Tablet_Hardness' and a batch of 200 records, then verify success by reading back via GET /getResults filtered to the same time window. ### Statistical process control reporting Pull descriptive and capability statistics for chosen analysis set fields to feed dashboards or daily reports. The getStatistics and getSpecificationEvaluation endpoints return summary values directly, so callers do not need to recompute Cp and Cpk locally. This is the fastest path to wire AlisQI quality data into an external BI tool. Example prompt: Call GET /getSpecificationEvaluation for analysis set 'Coating_Thickness' over the last 30 days and post the Cpk values into a Slack channel. ### Specification version management Create and retrieve specification versions when a product engineering change rolls out, so historical results are evaluated against the spec that applied at the time. The API exposes both read and write endpoints for versions, which avoids manual edits in the AlisQI UI when releases happen on a regular cadence. Example prompt: Call POST /storeSpecificationVersion to create a new version 'v2.3' for analysis set 'Bottle_Weight' with updated upper and lower limits. ### AI agent quality monitoring An AI agent can poll AlisQI on a schedule, pull fresh statistics for critical analysis sets, and raise an incident when capability indices drop below a threshold. Through Jentic the agent searches for the read operation by intent, loads the input schema, and executes - credentials never enter the prompt context. This converts a static dashboard into a proactive quality watch. Example prompt: Use Jentic to search for 'get capability statistics from AlisQI', load the input schema, and call GET /getSpecificationEvaluation for the configured analysis set; if Cpk is below 1.33, file an incident. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /getResults | Fetch results or master data for an analysis set | | POST | /storeResults | Create or update results in batch | | GET | /getStatistics | Descriptive statistics for analysis set fields | | GET | /getSpecificationEvaluation | Capability statistics for analysis set fields | | GET | /getAllSets | List all analysis sets and selection lists | | POST | /createSet | Create a new analysis set or selection list | | POST | /storeSpecificationVersion | Create a new specification version | ## Key resources - **Results** — Read and write lab results and master data tied to analysis sets - **Analysis sets** — List sets, inspect their field structure, create new sets, and manage permissions - **Statistics** — Descriptive and specification capability statistics for analysis set fields - **Specification versions** — Read existing specification versions and create new ones ## Why Jentic - **Setup:** Wiring AlisQI by hand means setting up its bearer API token, filling in the {subdomain}.alisqi.com tenant host, and encoding result capture and statistics reads yourself. Through Jentic you install once, import the AlisQI API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** AlisQI carries its result set and specification targets in query and body parameters rather than as path resources, so limit the agent to the operations it needs, such as getResults or getStatistics. You choose the operations it may call, so storeResults or createSet are not included unless you add them. - **Credential handling:** Your AlisQI API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'read quality measurement results' or 'get SPC statistics', and Jentic returns the matching AlisQI operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Clockify** — Time tracking on the shop floor often pairs with quality data capture - **Samsara** — Samsara provides industrial sensor and asset telemetry that can feed quality systems - **BambooHR** — Pair operator records with HR identity and team data ## FAQ ### Why is there no official OpenAPI spec for AlisQI API? AlisQI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AlisQI API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the AlisQI API use? AlisQI accepts a bearer API token via the standard Authorization header, or an access_token query parameter for environments where headers cannot be set. Through Jentic, the token is stored in the encrypted vault and injected at call time, so it never appears in agent prompts. ### Can I push batches of lab results to the AlisQI API? Yes. POST /storeResults accepts a batch of records bound to a named analysis set and creates or updates them in one call. Master data records can be sent alongside measurements in the same request body. ### How do I retrieve Cpk values via the AlisQI API through Jentic? Search Jentic for 'capability statistics from AlisQI', load the input schema for GET /getSpecificationEvaluation, and execute with the analysis set name. Jentic returns the capability indices directly so the agent does not have to recompute them. ### Does the AlisQI API require a tenant subdomain? Yes. The base URL is https://{subdomain}.alisqi.com/api where {subdomain} is the customer tenant. The subdomain must be configured in the request before calls can resolve. ### Can I create new analysis sets via the API? Yes. POST /createSet provisions a new analysis set or selection list, and POST /storeSetPermissions assigns access to users or groups. This is useful when onboarding a new product line programmatically. ### Can I limit what my agent is allowed to do with the AlisQI API? Yes. Because you run Jentic One yourself, your own rules decide which AlisQI operations and credentials the agent may use, so you can restrict it to read-only calls like getResults and getStatistics. AlisQI carries its analysis set and specification targets in query and body parameters rather than as path resources, so scoping is done per operation: write operations such as storeResults, createSet, and storeSpecificationVersion are not available to the agent unless you explicitly add them. The API token stays with your instance and is injected at call time, so the agent only exercises the operations you granted.