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

BrightAI

BrightAI builds Physical AI for essential services — continuous, AI-driven awareness of the real-time state of physical infrastructure for operators of water, power, energy, transportation and industrial systems. Founded in 2019 by SmartThings founder Alex Hawkinson, the company ships a four-layer Stateful platform (Data Acquisition, AI Hub, Stateful OS, Foundation Models) combining peel-and-stick sensors (Stateful Sticker), autonomous drone and quadruped inspection, a voice-interactive field Stateful Wearable, and infrastructure foundation models trained on operational outcomes across millions of industrial assets. BrightAI publishes no conventional developer portal or OpenAPI, but it does operate a public, no-authentication Model Context Protocol server at public.stateful.world/mcp exposing six read-only tools over its Global Observability Database, alongside an llms.txt index, agent-addressed markdown briefs, and two unauthenticated public JSON endpoints.

agent aware

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles BrightAI the way a machine reads it — 7 machine-readable artifacts across 2 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 — BrightAI scores 24.0/100 (emerging), with a separate agent-readiness read of 23/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 — 24.0/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 5.1 / 20
Commercial Clarity 7.9 / 20
Operational Transparency 0.0 / 13
Governance 1.5 / 12
Discoverability 7.6 / 10
Regulatory · Energy & Utilities 5.3 / 15
Agent readiness — 23/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 10 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills derived 1.3 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
BrightAI Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from BrightAI'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/brightai/"
   title="BrightAI on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/brightai.svg"
       alt="BrightAI 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 BrightAI

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

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.

BrightAI Public MCP Server

A public, read-only Model Context Protocol server (protocol 2025-06-18, serverInfo brightai-public 0.1.0) requiring no authentication. Exposes six tools over BrightAI's Global O...

BrightAI Public Observatory Data API

Two unauthenticated JSON endpoints published in BrightAI's llms.txt: /api/public/industries returns live worldwide aggregates and per-vertical addressable annual impact from the...

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

brightai-mcp.yml

MCP SERVER

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.

Brightai Authentication

none · 1 scheme

SECURITY

Brightai Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Brightai Trust Center

SOC 2

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.

Brightai Agentic Access

6 operations

6 operations · 0 acting

AGENTIC

Resources

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

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

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/brightai · machine-readable index on apis.io

Where this information came from

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