How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.

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 Clockworks Analytics the way a machine reads it — 7 machine-readable artifacts across 4 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 — Clockworks Analytics scores 35.8/100 (thin), with a separate agent-readiness read of 9/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-08-17 · rubric v0.11.0
Composite quality — 35.8/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 8.4 / 20
Operational Transparency 4.1 / 13
Governance 1.5 / 12
Discoverability 9.3 / 10
Regulatory · Energy & Utilities 6.1 / 15
Agent readiness — 9/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
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
Clockworks Analytics Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Clockworks Analytics'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/clockworks-analytics/"
   title="Clockworks Analytics on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/clockworks-analytics.svg"
       alt="Clockworks Analytics Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Clockworks Analytics

Each block below is one kind of artifact we hold for Clockworks Analytics. 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 4

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.

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

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

Every other property we hold for Clockworks Analytics — 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.

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

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

Where this information came from

This is an independent, third-party profile of Clockworks Analytics, 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.