Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Limble CMMS website screenshot

Limble CMMS

Limble CMMS is a cloud-based computerized maintenance management system (CMMS) for manufacturing, facilities, and fleet maintenance teams. The Limble REST API V2 provides programmatic access to assets, locations, work orders, preventive maintenance schedules, parts inventory, purchase orders, vendors, users, and webhooks across regionally distributed endpoints covering North America, Canada, Australia, and Europe.

agent aware

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Limble CMMS the way a machine reads it — 75 machine-readable artifacts across 43 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 — Limble CMMS scores 44.6/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 44.6/100 · thin
Contract Quality 16.0 / 25
Developer Ergonomics 6.1 / 20
Commercial Clarity 3.7 / 20
Operational Transparency 0.0 / 13
Governance 8.8 / 12
Discoverability 10.0 / 10
Agent readiness — 41/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Limble CMMS

Each block below is one kind of artifact we hold for Limble CMMS. 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 43

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.

Limble API V2

The Limble CMMS REST API V2 provides HTTPS access to maintenance management data including assets, locations, work orders, preventive maintenance tasks, parts, purchase orders, ...

Limble CMMS Assets API

The Assets API from Limble CMMS — 15 operation(s) for assets.

Limble CMMS Batch API

The Batch API from Limble CMMS — 1 operation(s) for batch.

Limble CMMS Bills API

The Bills API from Limble CMMS — 9 operation(s) for bills.

Limble CMMS Budgets API

The Budgets API from Limble CMMS — 5 operation(s) for budgets.

Limble CMMS Capacity API

The Capacity API from Limble CMMS — 5 operation(s) for capacity.

Limble CMMS Categories API

The Categories API from Limble CMMS — 2 operation(s) for categories.

Limble CMMS Comments API

The Comments API from Limble CMMS — 7 operation(s) for comments.

Limble CMMS Exceptions API

The Exceptions API from Limble CMMS — 3 operation(s) for exceptions.

Limble CMMS Fields API

The Fields API from Limble CMMS — 13 operation(s) for fields.

Limble CMMS Files API

The Files API from Limble CMMS — 5 operation(s) for files.

Limble CMMS General Ledgers API

The General Ledgers API from Limble CMMS — 2 operation(s) for general ledgers.

Limble CMMS Image API

The Image API from Limble CMMS — 1 operation(s) for image.

Limble CMMS Images API

The Images API from Limble CMMS — 4 operation(s) for images.

Limble CMMS Instructions API

The Instructions API from Limble CMMS — 5 operation(s) for instructions.

Limble CMMS Invoices API

The Invoices API from Limble CMMS — 4 operation(s) for invoices.

Limble CMMS Items API

The Items API from Limble CMMS — 3 operation(s) for items.

Limble CMMS Labor API

The Labor API from Limble CMMS — 2 operation(s) for labor.

Limble CMMS Locations API

The Locations API from Limble CMMS — 2 operation(s) for locations.

Limble CMMS Logs API

The Logs API from Limble CMMS — 11 operation(s) for logs.

Limble CMMS Me API

The Me API from Limble CMMS — 1 operation(s) for me.

Limble CMMS Options API

The Options API from Limble CMMS — 2 operation(s) for options.

Limble CMMS Parts API

The Parts API from Limble CMMS — 20 operation(s) for parts.

Limble CMMS Priorities API

The Priorities API from Limble CMMS — 2 operation(s) for priorities.

Limble CMMS Purchasables API

The Purchasables API from Limble CMMS — 1 operation(s) for purchasables.

Limble CMMS Purchase Orders API

The Purchase Orders API from Limble CMMS — 10 operation(s) for purchase orders.

Limble CMMS Regions API

The Regions API from Limble CMMS — 2 operation(s) for regions.

Limble CMMS Roles API

The Roles API from Limble CMMS — 3 operation(s) for roles.

Limble CMMS Routes API

The Routes API from Limble CMMS — 120 operation(s) for routes.

Limble CMMS Schedules API

The Schedules API from Limble CMMS — 2 operation(s) for schedules.

Limble CMMS State API

The State API from Limble CMMS — 2 operation(s) for state.

Limble CMMS Statuses API

The Statuses API from Limble CMMS — 2 operation(s) for statuses.

Limble CMMS Steps API

The Steps API from Limble CMMS — 3 operation(s) for steps.

Limble CMMS Tags API

The Tags API from Limble CMMS — 4 operation(s) for tags.

Limble CMMS Tasks API

The Tasks API from Limble CMMS — 24 operation(s) for tasks.

Limble CMMS Teams API

The Teams API from Limble CMMS — 3 operation(s) for teams.

Limble CMMS Transactions API

The Transactions API from Limble CMMS — 4 operation(s) for transactions.

Limble CMMS Units of Measure API

The Units of Measure API from Limble CMMS — 2 operation(s) for units of measure.

Limble CMMS Users API

The Users API from Limble CMMS — 9 operation(s) for users.

Limble CMMS Vendor Associations API

The Vendor Associations API from Limble CMMS — 2 operation(s) for vendor associations.

Limble CMMS Vendors API

The Vendors API from Limble CMMS — 11 operation(s) for vendors.

Limble CMMS Webhooks API

The Webhooks API from Limble CMMS — 2 operation(s) for webhooks.

Limble CMMS Work Request Submissions API

The Work Request Submissions API from Limble CMMS — 3 operation(s) for work request submissions.

Scroll within the panel for all 43 ·

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Limble Cmms Context

17 classes · 50 properties

JSON-LD

Spectral Rules 2

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Limble CMMS API Rules

5 rules · 3 warnings

SPECTRAL

Limble CMMS API Rules

7 rules · 1 errors · 4 warnings

SPECTRAL

JSON Schema 8

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.

Asset

10 properties

JSON SCHEMA

Location

14 properties

JSON SCHEMA

Part

21 properties

JSON SCHEMA

PurchaseOrder

27 properties

JSON SCHEMA

Task

40 properties

JSON SCHEMA

User

14 properties

JSON SCHEMA

Vendor

11 properties

JSON SCHEMA

WorkRequestSubmission

21 properties

JSON SCHEMA

Scroll within the panel for all 8 ·

JSON Structure 8

JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.

JSON Structure definitions describing this provider's data shapes.

Limble Cmms Asset Structure

0 properties

JSON STRUCTURE

Limble Cmms Location Structure

0 properties

JSON STRUCTURE

Limble Cmms Part Structure

0 properties

JSON STRUCTURE

Limble Cmms Purchase Order Structure

0 properties

JSON STRUCTURE

Limble Cmms Task Structure

0 properties

JSON STRUCTURE

Limble Cmms User Structure

0 properties

JSON STRUCTURE

Limble Cmms Vendor Structure

0 properties

JSON STRUCTURE

Scroll within the panel for all 8 ·

Examples 9

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Scroll within the panel for all 9 ·

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

Limble Cmms Authentication

http · 1 scheme

SECURITY

Limble Cmms Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Limble Cmms Trust Center

SOC 2, GDPR

SECURITY

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.

Limble Cmms Agentic Access

200 operations · 142 acting

200 operations · 142 acting

AGENTIC

Resources

Every other property we hold for Limble CMMS — 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 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 3

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Commercial 1

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/limble-cmms · machine-readable index on apis.io