STACK
STACK Construction Technologies makes cloud-based preconstruction software for on-screen takeoff and estimating used by contractors across most trades. STACK does expose a real, documented REST API (v2), but access is gated - you must be a STACK customer on an API-Enabled Subscription (or an approved partner) to obtain credentials. Authentication is OAuth 2.0, offered as two-legged (client-credentials, server-to-server) and three-legged (authorization-code, on behalf of a user) flows. Tokens are issued by a per-tenant authorization server (base pattern https://{server}/api/v2). The full endpoint reference sits behind an access request; the API surface catalogued here is modeled from STACK's public developer overview, authentication guide, and tutorials - it is not sourced from an official machine-readable OpenAPI document.
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 STACK the way a machine reads it — 10 machine-readable artifacts across 6 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 — STACK scores 26.4/100 (emerging), with a separate agent-readiness read of 12/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
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from STACK'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/stack-takeoff/"
title="STACK on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/stack-takeoff.svg"
alt="STACK Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/stack-takeoff/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/stack-takeoff/"
title="STACK on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/stack-takeoff/card.svg"
alt="STACK 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 STACK
Each block below is one kind of artifact we hold for STACK. 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 6
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.
STACK Projects API
Create and update projects and organize their contents in folders - the top-level container that takeoffs, plans, and estimates hang off of. Modeled from STACK's developer tutor...
STACK Plans & Files API
Upload plan sets and supporting documents into project folders, read file metadata, update file properties, and download plans. Modeled from STACK's developer tutorials (Folders...
STACK Takeoffs API
Create takeoffs on a project, list a takeoff's pages, set page scale, and retrieve measured quantities. On-screen takeoff is STACK's core workflow. Modeled from STACK's develope...
STACK Estimates API
Create, update, and retrieve estimate proposals - turning takeoff quantities into priced line items and a bid. Modeled from STACK's developer tutorials (EstimateProposals endpoi...
STACK Items & Assemblies API
Manage items and assemblies attached to takeoffs and retrieve their quantities and costs, so partner tools can pull takeoff/estimating data into invoices, purchase orders, or a ...
STACK Reference Data API
Read-only lookup endpoints for cost types, states, and countries used when constructing projects and estimates. Modeled from STACK's developer tutorials (CostTypes, States, Coun...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Stack Takeoff Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Stack Takeoff Finops
FINOPSSecurity 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 STACK — 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
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 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/stack-takeoff · machine-readable index on apis.io
This is an independent, third-party profile of STACK, 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.