Aquant · Arazzo Workflow
Diagnose an asset and source the right replacement part
Version 1.0.0
Confirm a symptom, predict the next symptom, then look up, detail and source the part.
View Spec
View on GitHub
CompanyArtificial IntelligenceAgentsField ServiceService ManagementManufacturingMedical DevicesIndustrial EquipmentKnowledge-ManagementVoice AIMCPPredictive MaintenanceArazzoWorkflows
Provider
Workflows
diagnose-and-source-part
Guard on observation_existence, rank likely next symptoms, then walk the parts chain from catalog lookup through detail to sourcing.
1
confirm-observation
observation_existence
Guard — verify Aquant knows this symptom before acting on it.
2
predict-next-symptom
next_symptom
Rank the most likely next symptoms for this asset, with how to check each.
3
lookup-part-catalog
part_catalog_lookup
Find candidate parts from the tenant catalog.
4
get-part-info
part_info
Pull detail for the selected catalog entry — pass the catalog data through, do not re-derive it.
5
get-part-sources
part_sources
Find where the part can be sourced.
Source API Descriptions
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for arazzo workflows
4 MCP tools reach this
find_arazzoBrowse and filter every workflow in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/aquant-diagnose-and-source-part"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.