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
Crux OCM website screenshot

Crux OCM

CruxOCM builds AI-powered automation software for industrial control-room operations in the energy-infrastructure sector. Its Industrial Automation Hub (IAH) delivers closed-loop automation on top of existing SCADA and DCS systems to increase pipeline throughput, cut operating and energy costs, and improve safety without replacing installed control infrastructure. The product family includes pipeBOT, gatherBOT, draBOT, maxOPT, leanOPT, and powerOPT, supported by a Deployment Manager, Log Analyser, and real-time Status Dashboard. Founded by control-room engineers and operators (CEO Vicki Knott, co-founder Roger Shirt) and headquartered in Calgary, Alberta, the company raised a $17M Series A led by Microsoft's M12 and serves midstream operators including ONEOK, Delek US, Enbridge, HF Sinclair, and Alliance Pipeline. It was surfaced as a Techstars portfolio company and added to the API Evangelist network.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Crux OCM the way a machine reads it — 2 machine-readable artifacts, 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 — Crux OCM scores 12.7/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 — 12.7/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.9 / 20
Commercial Clarity 3.7 / 20
Operational Transparency 1.4 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 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 Crux OCM

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

Security Posture 2

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.

Crux Ocm Domain Security

TLSv1.3 · DMARC

SECURITY

Crux Ocm Vulnerability Disclosure

contact published

SECURITY

Resources

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

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

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