CoConstruct
CoConstruct is a residential construction management software platform originally founded in 2005 in Charlottesville, Virginia by Donny Wyatt to help custom home builders and remodelers manage projects, budgets, selections, client communications, scheduling, and financial workflows in a single web and mobile application. The product served thousands of custom builders across the United States and was paired with CBUSA, a homebuilder group purchasing organization CoConstruct previously acquired. On February 24, 2021, CoConstruct was acquired by Buildertrend of Omaha, Nebraska, with growth funding from Bain Capital Tech Opportunities, HGGC, and Serent Capital, creating a combined company serving 23,000+ clients, 1.1M+ users, and $200B+ in annual construction project value. By 2022 Buildertrend had merged the two products into a single unified Buildertrend platform and migrated CoConstruct customers off the legacy product. CoConstruct historically operated a developer portal at developer.coconstruct.com exposing APIs for project, financial, and scheduling data, but as of the merger CoConstruct has paused new API development — "we are not establishing new API endpoints or connecting additional users to existing endpoints" — and the developer portal now redirects to a static notice page. Existing API connections are reportedly maintained but no public OpenAPI specification, SDK, or open-source release is published. Net-new integration work is directed to Buildertrend's own platform and partner program.
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 CoConstruct 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 — CoConstruct scores 14.1/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 CoConstruct
Each block below is one kind of artifact we hold for CoConstruct. 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 CoConstruct — 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 2
Portal, sign-up, and the first successful call
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/coconstruct · machine-readable index on apis.io