Fiix CMMS API
65
AI ReadinessAI-Aware (B)65/100
Official vendor OpenAPI document · agent-readyIOTDevice ManagementapiKey,oauth225 EndpointsREST
For Agents
Manage industrial assets, work orders, scheduled maintenance, parts inventory, and purchase orders in Fiix CMMS via 25 endpoints with API key or OAuth2 auth.
Use for: Create a work order for a faulty asset, List all open work orders at a specific site, Find scheduled maintenance due in the next 7 days, Get the asset hierarchy under a parent asset
Not supported: Does not handle ERP general ledgers, payroll, or production scheduling - use for CMMS assets, work orders, parts inventory, and preventive maintenance only.
Fiix (by Rockwell Automation) is a cloud-based Computerized Maintenance Management System (CMMS) used by manufacturers to track assets, work orders, parts, and scheduled maintenance. The API exposes 25 endpoints, with both a single /rpc operation-based JSON pattern and direct REST paths for assets, work orders, parts, purchase orders, and users. Authentication supports apiKey via the Authorization header and OAuth2 for delegated app access.
Install Jentic One Beta
Connect the Fiix CMMS API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fiix CMMS API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffiix.io%2Ffiix" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffiix.io%2Ffiix" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Fiix CMMS API.
Create, update, and close work orders against specific assets
Track asset hierarchies including parent-child relationships and locations
Schedule recurring preventive maintenance tied to assets
Manage spare parts inventory with reorder points
Issue purchase orders for parts replenishment
Execute generic CMMS operations via the unified /rpc endpoint
Use Cases
Patterns agents use Fiix CMMS API for, with concrete tasks.
★ Reactive Maintenance Workflow
Create work orders the moment a fault is detected by an upstream telemetry system. The Fiix API exposes POST /workorders linked to an asset_id so an agent can spawn the work order from sensor alerts without manual technician entry. Cuts mean-time-to-acknowledge from hours to seconds in industrial maintenance shops.
POST /workorders with asset_id and a description from the alert payload, then GET /workorders/{id} to confirm creation
Preventive Maintenance Scheduling
Surface upcoming preventive maintenance tasks across a fleet of assets so planners can stage parts and labour ahead of time. The Fiix API exposes scheduled-maintenance endpoints joined with asset records, supporting weekly look-aheads typical in plants with hundreds of assets.
List scheduled maintenance with due_date in the next 7 days, then resolve each asset_id to its location and group results by site
Parts Inventory Replenishment
Automate parts replenishment by joining current inventory with reorder thresholds and issuing purchase orders. The Fiix API exposes /parts and /purchaseorders endpoints, so an agent can detect low stock and create a PO in one workflow. Replaces manual stock-checks common in maintenance stockrooms.
GET /parts, filter by quantity_on_hand below reorder_point, and POST /purchaseorders for the affected parts
AI Agent Maintenance Assistant via Jentic
Through Jentic, an agent can answer plant-floor questions like which assets are overdue for service and which open work orders are blocked on parts. Jentic exposes Fiix's work order, asset, and parts operations as discoverable tools so a Claude or GPT agent can run grounded maintenance queries from natural language.
Search Jentic for 'list work orders', call GET /workorders, and return open ones grouped by asset and aged over 7 days
Key Endpoints
25 endpoints — fiix (by rockwell automation) is a cloud-based computerized maintenance management system (cmms) used by manufacturers to track assets, work orders, parts, and scheduled maintenance.
METHOD
PATH
DESCRIPTION
POST
/rpc
Execute an RPC operation
GET
/assets
List assets
POST
/assets
Create an asset
GET
/workorders
List work orders
POST
/workorders
Create a work order
GET
/parts
List parts inventory
POST
/rpc
Execute an RPC operation
GET
/assets
List assets
POST
/assets
Create an asset
GET
/workorders
List work orders
POST
/workorders
Create a work order
GET
/parts
List parts inventory
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Fiix CMMS API
- AI-Aware (B)65/100
87
Foundational Compliance57
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability68
Security54
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
35%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
34%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
69%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
68
Security
Trust, risk posture, and security compliance.
Grade: B+Signals: 1
68%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
54
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
54%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Fiix CMMS API by hand means resolving your {tenant} subdomain, choosing between API-key and OAuth2 auth, and driving the /rpc endpoint alongside the REST assets and work-order routes yourself. Through Jentic you install once, import the Fiix CMMS API from the API Directory, store the key and tenant once, and your agent calls it.
Permission scoping
Fiix work-order and asset targets travel in the request body and its /rpc payload rather than as owned-resource path ids, so limit the agent to the operations it needs, such as listing assets or creating a work order, and leave the rest out. Because you choose the allowed operations, a write runs only if you include it.
Credential isolation
Your Fiix API key or OAuth2 token and tenant value are stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw Authorization header value never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a work order' or 'list parts inventory', and Jentic returns the matching Fiix operation with its input schema, so the agent calls it without reading the API guide.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Fiix CMMS API through Jentic.
What authentication does the Fiix CMMS API use?
Fiix supports two methods: an API key sent in the Authorization header and OAuth2 for delegated apps. Through Jentic both are encrypted in your Jentic One instance and never enter agent context.
What is the /rpc endpoint in the Fiix API?
POST /rpc accepts an operation-based JSON request that maps to internal Fiix actions. It complements the direct REST paths and is used for actions that do not have a dedicated path in the OpenAPI spec.
What are the rate limits for the Fiix CMMS API?
Fiix does not publish per-second limits in the OpenAPI spec; consult fiixlabs.github.io/api-documentation/guide.html for plan-specific quotas applied per tenant.
How do I create a work order through Jentic?
Search Jentic for 'create work order', load the POST /workorders schema, and execute with asset_id and description. Run pip install jentic to start.
Does the Fiix API support multi-tenant deployments?
Yes. The base URL https://{tenant}.machinemetrics.io/api/v2 contains a tenant variable so each customer addresses their own subdomain. Jentic stores the tenant value alongside the credential.
Can I track parts inventory with the Fiix API?
Yes. The Parts endpoints expose quantity_on_hand and reorder_point fields and the Purchase Orders endpoints let you replenish low-stock parts in a single workflow.
Can I limit what my agent is allowed to do with the Fiix CMMS API?
Yes. Because Jentic One is self-hosted, you decide which Fiix operations your agent can reach, so you can allow read-only calls like listing assets or work orders while withholding writes such as creating a work order or issuing a purchase order. Fiix passes its work-order and asset targets in the request body and the /rpc payload rather than as owned-resource path ids, so the operation allowlist you set is what governs access. A write runs only if you have included that operation, and the API key and tenant value stay under your control.
GET STARTED