Aquant
Aquant is an agentic AI platform built for organizations that manufacture, sell, and service complex equipment. It turns a company's own service content — manuals, service histories, parts and warranty data, case notes — and the tacit expertise in its technicians' heads into role-specific AI agents for field technicians, call centers, customer self-service, and service leaders. The platform ships a library of prebuilt agents (Troubleshooting, Knowledge, Parts, IoT, Voice AI, Vision AI, Preventive Maintenance) plus an Agent Studio for building custom agents, and delivers them across web, mobile, voice, offline, and API channels into CRM, FSM, and support-portal workflows. Aquant exposes two public machine-readable surfaces: an MCP server at mcp.aquant.ai that publishes eleven service-intelligence tools over both JSON-RPC Streamable HTTP and REST, and the Aquant Conversation Platform (ACP) voice/chat API at voiceai-api.aquant.ai fronted by a first-party browser SDK.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Aquant the way a machine reads it — 14 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Aquant scores 48.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Aquant's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aquant/"
title="Aquant on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aquant.svg"
alt="Aquant Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/aquant/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aquant/"
title="Aquant on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aquant/card.svg"
alt="Aquant Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Aquant
Each block below is one kind of artifact we hold for Aquant. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Aquant MCP Server
The Aquant MCP Server exposes Aquant's service-intelligence capabilities as eleven agent-callable tools — part catalog lookup, part info and sourcing, agent (technician) data, t...
Aquant Conversation Platform (VoiceAI) API
The Aquant Conversation Platform (ACP) API powers Voice AI and web chat with Aquant's service agents. Clients exchange an API key and secret for a one-hour access token at POST ...
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Aquant MCP Server
OPEN COLLECTIONFastAPI
OPEN COLLECTIONArazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Diagnose an asset and source the right replacement part
Confirm a symptom, predict the next symptom, then look up, detail and source the part.
ARAZZOLocate an asset and rank the nearest qualified technician
Resolve an asset location, pull technician proficiency, then rank technicians by proximity.
ARAZZORun a preventive-maintenance visit and file the summary
Health-check the service, generate the PM checklist for an asset, then produce the summary report.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
aquant-mcp.yml
MCP SERVERJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Aquant Mcp Server Schemas
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Aquant — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aquant · machine-readable index on apis.io
This is an independent, third-party profile of Aquant, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.