Clockworks Analytics

Clockworks Analytics is a Boston-area building-analytics company whose cloud platform performs automated fault detection and diagnostics (FDD) on HVAC and building systems. It ingests interval data from Building Management Systems through the Clockworks Connect gateway, runs a curated library of root-cause diagnostics, and quantifies each performance issue by avoidable energy cost plus energy, comfort and maintenance priority on a 0-10 scale. Its public REST API is delivered through Azure API Management on rest.buildingsapi.net as four containers — core-base (clients, buildings, equipment, points, users), core-diag (diagnostic records), core-kpis (KQL-driven aggregated datasets) and workorders (Tasks / CMMS work-order sync) — and is documented publicly at cw.clockworksanalytics.com plus a public Confluence developer guide set for CMMS and KPI integration.

Clockworks Analytics publishes 4 APIs on the APIs.io network. Tagged areas include Company, Building Analytics, Fault Detection and Diagnostics, HVAC, and Energy Management.

Clockworks Analytics’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, changelog, authentication, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub

36.8/100 thin ▬ flat Agent 3/100 human only saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

4 APIs

CompanyBuilding AnalyticsFault Detection and DiagnosticsHVAC Energy Management Facilities Management Smart BuildingsCMMS IntegrationAnalytics Internet of Things

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 36.8/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 10.9 / 17

Access Clarity 6.0 / 17

Operational Transparency 3.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.3 / 9

Regulatory Posture 6.1 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/clockworks-analytics: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Clockworks Base API

The Base container of the Clockworks REST API. Serves static asset information — clients, buildings, building types and variables, equipment, equipment classes / types / variabl...

Clockworks Diagnostics API

The core-diag container. POST /diagnostics returns the diagnostic records produced by the Clockworks analysis engine for a set of client IDs, building IDs, a date range and an a...

Clockworks Key Performance Indicators API

The core-kpis container. POST /AggregatedData accepts a Kusto Query Language (KQL) expression plus a dataset list and returns server-side aggregated results across the Clockwork...

Clockworks Work Orders API

The workorders container. Carries the Task records Clockworks users create from diagnostic results and synchronizes them to work orders in a CMMS. Uses a bearer token obtained f...

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Clockworks Analytics Authentication

apiKey/http · 2 schemes

SECURITY

Clockworks Analytics Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Clockworks Analytics Trust Center

trust center published

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

Lifecycle

Conformance

DataModel

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Authentication

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: clockworks-analytics
name: Clockworks Analytics
description: Clockworks Analytics is a Boston-area building-analytics company whose cloud platform performs automated fault
  detection and diagnostics (FDD) on HVAC and building systems. It ingests interval data from Building Management Systems
  through the Clockworks Connect gateway, runs a curated library of root-cause diagnostics, and quantifies each performance
  issue by avoidable energy cost plus energy, comfort and maintenance priority on a 0-10 scale. Its public REST API is delivered
  through Azure API Management on rest.buildingsapi.net as four containers — core-base (clients, buildings, equipment, points,
  users), core-diag (diagnostic records), core-kpis (KQL-driven aggregated datasets) and workorders (Tasks / CMMS work-order
  sync) — and is documented publicly at cw.clockworksanalytics.com plus a public Confluence developer guide set for CMMS and
  KPI integration.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: covered
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://clockworksanalytics.com/wp-content/themes/Clockworks/images/clockworks-logo.svg
url: https://raw.githubusercontent.com/api-evangelist/clockworks-analytics/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-09'
modified: '2026-08-09'
tags:
- Company
- Building Analytics
- Fault Detection and Diagnostics
- HVAC
- Energy Management
- Facilities Management
- Smart Buildings
- CMMS Integration
- Analytics
- Internet of Things
apis:
- name: Clockworks Base API
  description: The Base container of the Clockworks REST API. Serves static asset information — clients, buildings, building
    types and variables, equipment, equipment classes / types / variables, points, point classes and types, engineering units,
    task records and users — as JSON:API-shaped documents. Authenticated with an Azure API Management subscription key in
    the Ocp-Apim-Subscription-Key header.
  humanURL: https://cw.clockworksanalytics.com/APIDocumentation.aspx
  baseURL: https://rest.buildingsapi.net/core-base
  tags:
  - Buildings
  - Equipment
  - Assets
  properties:
  - type: Documentation
    url: https://cw.clockworksanalytics.com/APIDocumentation.aspx
  - type: APIReference
    url: https://cw.clockworksanalytics.com/APIDocumentation.aspx
- name: Clockworks Diagnostics API
  description: The core-diag container. POST /diagnostics returns the diagnostic records produced by the Clockworks analysis
    engine for a set of client IDs, building IDs, a date range and an analysis interval, including avoidable cost, energy
    / comfort / maintenance priorities and the narrative fault notes.
  humanURL: https://cw.clockworksanalytics.com/APIDocumentation.aspx
  baseURL: https://rest.buildingsapi.net/core-diag
  tags:
  - Diagnostics
  - Faults
- name: Clockworks Key Performance Indicators API
  description: The core-kpis container. POST /AggregatedData accepts a Kusto Query Language (KQL) expression plus a dataset
    list and returns server-side aggregated results across the Clockworks datasets (Diagnostics, DiagnosticResults, RawData,
    AggregatedRawData, Equipment, Buildings, Points, Tasks, Users and more) instead of thousands of individual records.
  humanURL: https://clockworksanalytics.atlassian.net/wiki/spaces/ClockworksAnalyticsUM/pages/4577951781/Key+Performance+Indicators+API+Developer+Guide
  baseURL: https://rest.buildingsapi.net/core-kpis
  tags:
  - KPIs
  - Analytics
  - Aggregation
  properties:
  - type: Documentation
    url: https://clockworksanalytics.atlassian.net/wiki/spaces/ClockworksAnalyticsUM/pages/4577951781/Key+Performance+Indicators+API+Developer+Guide
- name: Clockworks Work Orders API
  description: The workorders container. Carries the Task records Clockworks users create from diagnostic results and synchronizes
    them to work orders in a CMMS. Uses a bearer token obtained from POST /workorders/auth/token with a clientId and clientSecret,
    valid for 3599 seconds, rather than the subscription key used by the other containers.
  humanURL: https://clockworksanalytics.atlassian.net/wiki/spaces/ClockworksAnalyticsUM/pages/5742297089/CMMS+Integration+Developer+Guide+version+2
  baseURL: https://rest.buildingsapi.net/workorders
  tags:
  - Work Orders
  - Task
  - CMMS
  tags_raw:
  - Work Orders
  - Tasks
  - CMMS
  properties:
  - type: Documentation
    url: https://clockworksanalytics.atlassian.net/wiki/spaces/ClockworksAnalyticsUM/pages/5742297089/CMMS+Integration+Developer+Guide+version+2
  - type: GettingStarted
    url: https://clockworksanalytics.atlassian.net/wiki/spaces/ClockworksAnalyticsUM/pages/5742297089/CMMS+Integration+Developer+Guide+version+2
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://clockworksanalytics.com/
- type: DeveloperPortal
  url: https://clockworks.developer.azure-api.net/
- type: Documentation
  url: https://cw.clockworksanalytics.com/APIDocumentation.aspx
- type: APIReference
  url: https://cw.clockworksanalytics.com/APIDocumentation.aspx
- type: GettingStarted
  url: https://clockworksanalytics.atlassian.net/wiki/spaces/ClockworksAnalyticsUM/pages/5742297089/CMMS+Integration+Developer+Guide+version+2
- type: Support
  url: https://kgsbuildings.atlassian.net/servicedesk/customer/portals
- type: Blog
  url: https://clockworksanalytics.com/blog/
- type: Login
  url: https://portal.clockworksanalytics.com/login
- type: TermsOfService
  url: https://clockworksanalytics.com/website-terms-of-use/
- type: PrivacyPolicy
  url: https://clockworksanalytics.com/website-terms-of-use/
- type: StatusPage
  url: https://status.clockworksanalytics.com/
- type: ChangeLog
  url: https://clockworksanalytics.com/product-updates/
- type: TrustCenter
  url: https://trust.clockworksanalytics.com/
- type: TrustCenter
  url: security/clockworks-analytics-trust-center.yml
- type: ChangeLog
  url: changelog/clockworks-analytics-changelog.yml
- type: Authentication
  url: authentication/clockworks-analytics-authentication.yml
- type: Conventions
  url: conventions/clockworks-analytics-conventions.yml
- type: Lifecycle
  url: lifecycle/clockworks-analytics-lifecycle.yml
- type: Conformance
  url: conformance/clockworks-analytics-conformance.yml
- type: DataModel
  url: data-model/clockworks-analytics-data-model.yml
- type: Sandbox
  url: sandbox/clockworks-analytics-sandbox.yml
- type: DomainSecurity
  url: security/clockworks-analytics-domain-security.yml
- type: LLMsTxt
  url: llms/clockworks-analytics-llms.txt
x-enrichment:
  date: '2026-08-09'
  status: enriched
  artifacts_added: 11
  pass: local-v1
x-coverage:
  state: covered
  reason: null
  detail: The public REST reference at cw.clockworksanalytics.com is fully readable and four Azure API Management containers
    on rest.buildingsapi.net were confirmed live, but Clockworks publishes no OpenAPI, AsyncAPI, GraphQL SDL or Postman collection
    anywhere — the APIM developer portal returns an empty API list to anonymous callers.
  evidence:
  - url: https://cw.clockworksanalytics.com/APIDocumentation.aspx
    status: 200
  - url: https://rest.buildingsapi.net/core-base/clients
    status: 401
  - url: https://clockworks.developer.azure-api.net/developer/apis?api-version=2022-04-01-preview
    status: 200
  checked: '2026-08-09'

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/clockworks-analytics"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/clockworks-analytics/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/clockworks-analytics/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.