Omen
Omen (omen.ai) delivers real-time asset intelligence through continuous fluid analysis, monitoring the health of mission-critical machinery in data centers and heavy industry. Its two offerings are a non-invasive permanent sensor that attaches to equipment for continuous, automated fluid (oil, coolant, water) analysis and real-time health tracking, and a portable canister lab that performs on-site, off-site, and field spectroscopic testing. The platform detects wear, contamination, and degradation before failures occur, targeting the machines the world depends on. Backed by CRV. As of this enrichment pass Omen publishes no public API, developer portal, documentation, or SDKs; this profile captures company identity 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.
Omen is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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 — Omen scores 6.8/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
How this is scored →scored 2026-07-27 · rubric v0.5
Resources
Every other property we hold for Omen — 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.
Company 2
The organization behind the API
Omen is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/omen · machine-readable index on apis.io