Bidgely
Bidgely is a Mountain View, California energy analytics company that builds AI software for electric and gas utilities. Its flagship platform, UtilityAI, applies patented non-intrusive load monitoring (NILM) and disaggregation techniques to smart meter interval data to infer appliance-level energy usage — air conditioning, heat pumps, electric vehicles, pool pumps, water heaters and more — from the whole-home meter signal alone, without surveys, sub-meters, or smart plugs. The platform layers GenAI natural-language interfaces and Agentic AI workflows on top of disaggregation to support utility programs across demand-side management, customer engagement and high-bill alerts, load flexibility and time-of-use, electrification (EV and heat pump targeting), grid resiliency and DER planning, affordability and income-qualified outreach, gas efficiency, small and mid-sized business programs, and energy theft detection. Bidgely is sold to utilities as SaaS or deployable into customer AWS, Snowflake, Databricks, Azure, and Oracle environments, and exposes embeddable customer-facing widgets to utility digital channels. Bidgely has been deployed by more than 50 utilities across four continents — including FortisBC, Arizona Public Service, PacifiCorp, Avista, NV Energy, Nova Scotia Power, and SoCalGas — covering tens of millions of meters. Bidgely operates an internal REST API surface across regional endpoints (naapi.bidgely.com, api.eu.bidgely.com) for its own pilot deployments and embeddable widgets, but does not currently publish a public developer portal, OpenAPI specification, or self-service API key program; integration is conducted under utility contracts.
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.
API Evangelist profiles Bidgely the way a machine reads it — 1 machine-readable artifact, 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 — Bidgely scores 7.4/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
How we profile Bidgely
Each block below is one kind of artifact we hold for Bidgely. 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 1
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.
Resources
Every other property we hold for Bidgely — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Company 6
The organization behind the API
Other 17
Properties that don't map to a standard resource type
Scroll within the panel for all 17 ·
← All providers · Data indexed from github.com/api-evangelist/bidgely · machine-readable index on apis.io