BuildOps

BuildOps is an AI-native, all-in-one commercial contractor management platform for multi-trade service and construction companies. It unifies project management, service operations, dispatch and scheduling, financials and invoicing, and sales/CRM into a single system used by 1,500+ contractors across HVAC, electrical, plumbing, fire safety, and refrigeration trades. Backed by Founders Fund, the company offers pre-built integrations with ERP and accounting systems (QuickBooks, Sage, Vista, Spectrum, NetSuite) plus field-intelligence, payroll, and procurement tools. BuildOps operates a public Dev Center that names a BuildOps Public API offering REST endpoints and webhook callbacks, but that API documentation is marked "Invite Required" and is reachable only through an implementation or customer-success manager. No OpenAPI, AsyncAPI, GraphQL SDL or Postman collection is published anywhere, and no first-party SDK exists in any public registry. The only public Dev Center project is a Data Dictionary describing BuildOps datasets on the Dashboard module and a Snowflake private share. BuildOps does publish a security policy and a Vanta-hosted Trust Center carrying SOC 2 Type I.

BuildOps is listed with 1 API on the APIs.io network. Tagged areas include Company, Construction Software, Field Service, Contractor Management, and Commercial Services.

The BuildOps catalog on APIs.io includes 1 event-driven AsyncAPI specification.

BuildOps’ developer surface includes pricing, signup flow, support, documentation, engineering blog, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

34.9/100 thin ▬ flat Agent 32/100 agent ready Front door AI 3/6 light saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

1 API 1 MCP Servers

CompanyConstruction SoftwareField Service Contractor ManagementCommercial ServicesHVAC ERP Integration CRM

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 34.9/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 2.0 / 17

Access Clarity 10.3 / 17

Operational Transparency 1.5 / 11

Contract Governance 0.0 / 10

Discoverability 6.4 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 32/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/buildops: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Building Automation (HVAC, BACnet, KNX, smart buildings)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

BuildOps Public API

The BuildOps Public API, named by the BuildOps Dev Center as the REST + webhook-callback integration surface for customers, software partners and vendors. The Dev Center gates i...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

BuildOps MCP Server

Remote MCP server at docs.buildops.com over HTTP.

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Buildops Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Buildops Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Buildops Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Buildops Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Buildops Vulnerability Disclosure

Hackerone · contact published

SECURITY

Buildops Trust Center

SOC 2 Type I

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 6

Authentication, authorization, and security posture

TrustCenter

TrustCenter

DomainSecurity

DomainSecurity

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

TrustCenter

TrustCenter

Compliance

Compliance

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: buildops
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/buildops.png
name: BuildOps
description: BuildOps is an AI-native, all-in-one commercial contractor management platform for multi-trade service and construction
  companies. It unifies project management, service operations, dispatch and scheduling, financials and invoicing, and sales/CRM
  into a single system used by 1,500+ contractors across HVAC, electrical, plumbing, fire safety, and refrigeration trades.
  Backed by Founders Fund, the company offers pre-built integrations with ERP and accounting systems (QuickBooks, Sage, Vista,
  Spectrum, NetSuite) plus field-intelligence, payroll, and procurement tools. BuildOps operates a public Dev Center that
  names a BuildOps Public API offering REST endpoints and webhook callbacks, but that API documentation is marked "Invite
  Required" and is reachable only through an implementation or customer-success manager. No OpenAPI, AsyncAPI, GraphQL SDL
  or Postman collection is published anywhere, and no first-party SDK exists in any public registry. The only public Dev Center
  project is a Data Dictionary describing BuildOps datasets on the Dashboard module and a Snowflake private share. BuildOps
  does publish a security policy and a Vanta-hosted Trust Center carrying SOC 2 Type I.
url: https://raw.githubusercontent.com/api-evangelist/buildops/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- founders-fund
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-10'
x-docs-platform: stoplight
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-21
tags:
- Company
- Construction Software
- Field Service
- Contractor Management
- Commercial Services
- HVAC
- ERP Integration
- CRM
tags_raw:
- Company
- Construction Software
- Field Service Management
- Contractor Management
- Commercial Services
- HVAC
- ERP Integration
- CRM
apis:
- aid: buildops:public-api
  name: BuildOps Public API
  description: The BuildOps Public API, named by the BuildOps Dev Center as the REST + webhook-callback integration surface
    for customers, software partners and vendors. The Dev Center gates its reference behind "Invite Required"; the production
    host is live and answers unauthenticated health checks but publishes no OpenAPI. Recorded here as a real but undocumented
    API surface.
  humanURL: https://developer.buildops.com/docs/buildops-public-api
  baseURL: https://public-api.live.buildops.com
  tags:
  - Field Service
  - Contractor Management
  - Construction Software
  tags_raw:
  - Field Service Management
  - Contractor Management
  - Construction Software
  properties:
  - type: Documentation
    url: https://developer.buildops.com/docs/buildops-public-api
  x-access: gated
  x-evidence:
    fetched: '2026-08-10'
    humanurl_status: 404
    humanurl_note: '"Invite Required - Reach out to your IM or CSM to get access to the documentation above." The doc node
      is not published to the public Stoplight project, so the link on the Dev Center landing page 404s.'
    baseurl_discovery: Host read from the production host map in BuildOps' own public web-client bundle at https://live.buildops.com/static/js/main.7f23205c.js,
      which names public-api.live.buildops.com as the PROD entry alongside rest-api.live.buildops.com and graphql.live.buildops.com.
      Not stated in any BuildOps documentation; recorded from a live probe, not from the docs.
    baseurl_probes:
    - url: https://public-api.live.buildops.com/
      status: 200
      body: OK!
    - url: https://public-api.live.buildops.com/health
      status: 200
      body: OK!
    - url: https://public-api.live.buildops.com/openapi.json
      status: 404
    - url: https://public-api.live.buildops.com/swagger.json
      status: 404
    - url: https://public-api.live.buildops.com/api-json
      status: 404
    server_note: 404 bodies are NestJS-shaped ({"statusCode":404,"message":"Cannot GET /openapi.json"}), confirming a live
      application rather than a CDN catch-all. No specification is served on any conventional path.
x-contract-discovery:
  checked: '2026-08-10'
  method: probed
  finding: 'Machine-readable contracts for BuildOps DO exist and are generated by the running services - they are auth-gated,
    not absent. Two probes prove it: api.core.live.buildops.com serves the springdoc path /v3/api-docs and answers 401 "Authorization
    token isn`t provided" (a missing spec would 404), and graphql.live.buildops.com/graphql answers a GraphQL introspection
    POST with a 403 "Your authorization token is invalid" rather than a transport error. This is why the coverage state is
    `gated` and not `unreadable` or `none`.'
  probes:
  - url: https://api.core.live.buildops.com/v3/api-docs
    status: 401
    note: springdoc OpenAPI endpoint present
    token required: null
  - url: https://api.core.live.buildops.com/swagger-ui/index.html
    status: 403
  - url: https://graphql.live.buildops.com/graphql
    status: 403
    note: GraphQL introspection rejected - "Your authorization token is invalid"
  - url: https://rest-api.live.buildops.com/openapi.json
    status: 401
    note: unauthorized request
  - url: https://public-api.live.buildops.com/openapi.json
    status: 404
  production_hosts_named_in_web_client:
  - account-management-svc.live.buildops.com
  - api.core.live.buildops.com
  - batch-operation.live.buildops.com
  - bim-svc.live.buildops.com
  - core.live.buildops.com
  - crmplus-api.live.buildops.com
  - equipment-svc.live.buildops.com
  - graphql.live.buildops.com
  - project-management-api.live.buildops.com
  - public-api.live.buildops.com
  - rest-api.live.buildops.com
  - search-query.live.buildops.com
  source: https://live.buildops.com/static/js/main.7f23205c.js
  note: These are the application's own service hosts, discovered from a public JavaScript bundle. They are recorded as evidence
    that the API estate is real and reachable, NOT as documented public endpoints. Only public-api is promoted to an apis[]
    entry, because it is the one the provider itself names as public.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://buildops.com
- type: DeveloperPortal
  url: https://developer.buildops.com/
- type: Integrations
  url: https://www.buildops.com/platform/integrations
- type: Pricing
  url: https://www.buildops.com/pricing
- type: SignUp
  url: https://www.buildops.com/book-demo
- type: Login
  url: https://live.buildops.com/
- type: Support
  url: https://academy.buildops.com/
- type: TrustCenter
  url: https://trust.buildops.com/
- type: TermsOfService
  url: https://www.buildops.com/terms-of-service
- type: PrivacyPolicy
  url: https://www.buildops.com/privacy-policy
- type: DomainSecurity
  url: security/buildops-domain-security.yml
- type: Documentation
  name: BuildOps Data Dictionary
  url: https://developer.buildops.com/docs/data-dictionary/4b402d5ab3edd-build-ops-datasets
- type: Blog
  url: https://buildops.com/resources
- type: GitHubOrganization
  url: https://github.com/BuildHero
- type: Security
  name: BuildOps Security Policy
  url: https://buildops.com/security-policy
- type: VulnerabilityDisclosure
  url: security/buildops-vulnerability-disclosure.yml
- type: TrustCenter
  name: Trust center profile
  url: security/buildops-trust-center.yml
- type: Compliance
  name: SOC 2 Type I
  url: https://trust.buildops.com/
- type: Plans
  url: plans/buildops-plans-pricing.yml
- type: RateLimits
  url: rate-limits/buildops-rate-limits.yml
- type: Packages
  url: packages/buildops-packages.yml
- type: LLMsTxt
  url: llms/buildops-llms.txt
x-enrichment:
  date: '2026-08-10'
  status: minimal
  artifacts_added: 8
  pass: local-v1
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: The BuildOps Dev Center advertises a "BuildOps Public API" with REST endpoints and webhook callbacks, then gates
    the reference behind "Invite Required - reach out to your IM or CSM"; the linked doc node 404s to the public and the workspace's
    only published Stoplight project is a Data Dictionary with zero API nodes and zero operations. The contracts demonstrably
    exist behind that wall - the springdoc endpoint /v3/api-docs answers 401 rather than 404, and GraphQL introspection is
    refused with 403 - so this is a gate, not an absence.
  evidence:
  - url: https://developer.buildops.com/docs/buildops-public-api
    status: 404
  - url: https://developer.buildops.com/
    status: 200
  - url: https://stoplight.io/api/v1/workspaces/d2s6MTY5MTA1/projects
    status: 200
  - url: https://api.core.live.buildops.com/v3/api-docs
    status: 401
  - url: https://graphql.live.buildops.com/graphql
    status: 403
  - url: https://public-api.live.buildops.com/openapi.json
    status: 404
  checked: '2026-08-10'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/buildops"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/buildops/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/buildops/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.