Cove.Tool
cove.tool (rebranded to "cove" in 2025) is an Atlanta, Georgia building-performance analysis platform for architects, engineers and contractors, founded in 2017 by Sandeep Ahuja, Patrick Chopson and Daniel Chopson. Its analysis.tool engine runs energy, daylight, glare, embodied carbon, water, radiation, shadow and cost-versus-performance optimization on early-stage building designs. The company publishes a public REST API — marketed as api.tool — that lets software vendors and design firms create projects, upload building geometry, select an energy code, kick off daylight and energy simulation, poll job status and retrieve EUI, sDA and ASE results without using the web application. Two OpenAPI 3.0 definitions are served from the developer portal: a three-operation v1 and a thirteen-operation v2.
Cove.Tool publishes 2 APIs on the APIs.io network: REST API v2 and API v1. Tagged areas include Company, Building Performance, Energy Modeling, Daylight Analysis, and Sustainability.
Cove.Tool’s developer surface includes authentication, API reference, documentation, getting-started guide, support, signup flow, and 15 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
cove.tool REST API v2
The current cove.tool REST API. Thirteen operations across six tags — User, Profiles, Energy Codes, Projects, Project Geometry and Daylight Analysis — covering account creation,...
cove.tool API v1
The original cove.tool API, still served from the developer portal alongside v2. Three operations: obtain an API token, list projects and their associated information, and updat...
Open Collections 2
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
cove.tool API
OPEN COLLECTIONcove.tool REST API v2
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Cove.Tool Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
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 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API