AlisQI API

Name: AlisQI API API
Brand: AlisQI API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligencebearer, apiKey10 EndpointsREST

For Agents

Read and write quality management data in AlisQI — fetch lab results and statistics, push new measurements, and manage specification versions for a tenant.

Quickstart

Get started with AlisQI API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"push lab results to AlisQI"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AlisQI API API.

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

GET STARTED

Start building with AlisQI API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AlisQI API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use AlisQI API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

10 endpoints — jentic publishes the only available openapi specification for alisqi api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AlisQI bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution tokens — the raw bearer or access_token query value never enters the prompt or LLM context.

Intent-based discovery

Agents search by intent (e.g. 'push lab results to AlisQI') and Jentic returns the matching operation with its input schema, so the agent calls the right endpoint without parsing the docs.

Time to first call

Direct AlisQI integration: 1-2 days to handle tenant subdomain config, auth wiring, and batch result formatting. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Clockify

Time tracking on the shop floor often pairs with quality data capture

Use Clockify when you need to attach who recorded a measurement and how long the operation took, alongside the AlisQI quality reading

Complementary

Samsara

Samsara provides industrial sensor and asset telemetry that can feed quality systems

Use Samsara when the quality measurement originates from connected industrial equipment and AlisQI is the quality system of record

Complementary

BambooHR

Pair operator records with HR identity and team data

Use BambooHR when an AlisQI quality report needs to attribute readings to a specific operator's HR record

FAQs

Specific to using AlisQI API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.