Redaptive
Redaptive is an energy infrastructure modernization company that funds, installs, and measures energy-saving and energy-generating equipment across large multi-site commercial, industrial, healthcare and real-estate portfolios under an Efficiency-as-a-Service and Energy-as-a-Service model, so customers modernize lighting, HVAC, refrigeration, solar and EV infrastructure without capital expenditure. Its Redaptive ONE platform meters electricity, gas and water at the asset level and turns that telemetry into portfolio consumption, sustainability benchmarking and ESG reporting. Redaptive contracts an API and an SDK to Data Solutions customers under published terms, but the reference and specification are not public.
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.
API Evangelist profiles Redaptive the way a machine reads it — 5 machine-readable artifacts across 3 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 — Redaptive scores 22.6/100 (emerging), 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.
Why this profile is thin
Redaptive's own Data Solutions Terms and Conditions define an API, an SDK and developer documentation that Redaptive "may make available from time to time" to contracted customers, and all three production backends behind the Redaptive ONE app (core, denali, data-browser) answer anonymous requests with a bare 401 or 404 — the only document reachable without a Redaptive-issued API key is the OAuth authorization-server metadata at the core gateway.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Redaptive's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://core.api.prod.redaptivegroup.com/api/core/v1→ HTTP 401https://denali-api.redaptive.com/api/denali→ HTTP 401https://core.api.prod.redaptivegroup.com/.well-known/oauth-authorization-server→ HTTP 200https://redaptive.com/data-solutions-terms-and-conditions/→ HTTP 200
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.
Put this on your own site. The badge is drawn live from Redaptive'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/redaptive/"
title="Redaptive on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/redaptive.svg"
alt="Redaptive Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/redaptive/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/redaptive/"
title="Redaptive on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/redaptive/card.svg"
alt="Redaptive Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Redaptive
Each block below is one kind of artifact we hold for Redaptive. 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 3
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.
Redaptive ONE Core API
The core API gateway behind the Redaptive ONE platform, serving the account, portfolio and building-insights surfaces of the ONE web application. Access is OAuth 2.0 protected: ...
Redaptive ONE Denali API
The Denali service behind the Redaptive ONE platform, serving the metering, consumption and sustainability-reporting surfaces of the ONE web application. OAuth 2.0 protected; an...
Redaptive Data Solutions API
The API Redaptive licenses to Data Solutions customers, alongside an optional SDK, for programmatic access to metered energy, gas and water usage data. Its existence, its API-ke...
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.
Resources
Every other property we hold for Redaptive — 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 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
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/redaptive · machine-readable index on apis.io
This is an independent, third-party profile of Redaptive, 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.