Agave
Agave is a unified API platform for the construction industry, enabling software companies and contractors to read and write data across 100+ construction and accounting software systems including Procore, Autodesk Build, QuickBooks, Sage, Viewpoint, and more.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Agave the way a machine reads it — 104 machine-readable artifacts across 11 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 — Agave scores 59.2/100 (developing), with a separate agent-readiness read of 55/100 (agent ready). 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 Agave
Each block below is one kind of artifact we hold for Agave. 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 11
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.
Agave Link Component
Agave Link is a front-end component that enables users to select source systems, authenticate with their construction software accounts, and share data with your application, ha...
Agave File Manager Component
Agave File Manager is a front-end component that allows users to pick files and folders from linked construction software accounts to share with your application.
Agave Budgets API
Project budget and cost management resources.
Agave Contracts API
Prime contracts and commitment management.
Agave Cost Codes API
Job cost codes and cost types.
Agave Employees API
Employee records and workforce management.
Agave Invoices API
Accounts payable invoices and billing.
Agave Link Sessions API
Agave Link session management for user authentication.
Agave Projects API
Construction project management resources.
Agave Timesheets API
Employee timesheet and labor tracking.
Agave Vendors API
Vendor and subcontractor management.
Scroll within the panel for all 11 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Agave Unified Construction API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Agave GraphQL Schema
This conceptual GraphQL schema represents the Agave Unified Construction API domain model. Agave provides a single API layer that normalizes data across 100+ construction and ac...
GRAPHQLPricing 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.
Agave Plans Pricing
PLANSRate 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.
Agave 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.
Agave Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Unified Construction API
Single REST API to read and write data across 100+ construction and accounting software systems with normalized data models.
Agave Link Authentication
Pre-built front-end component for user authentication that handles OAuth flows for all supported construction software platforms.
ERP Sync
Automatic synchronization of jobs, financials, timesheets, and cost data between field systems and ERP platforms.
AP Invoice Automation
AI-powered invoice capture, job matching, cost code coding, approval routing, and ERP sync for accounts payable workflows.
Passthrough Requests
Direct passthrough of requests to source system APIs with Agave handling authentication and protocol translation.
Webhooks
Real-time webhook notifications for data changes in connected construction software systems.
Sandbox Environments
Sandbox mode for testing integrations without affecting production data in connected systems.
Agave File Manager
Pre-built front-end component for browsing and selecting files from connected construction document storage systems.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Agave Unified Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Agave API Rules
SPECTRALAgave API Rules
SPECTRALJSON Schema 19
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
BudgetList
JSON SCHEMABudget
JSON SCHEMAContractList
JSON SCHEMAContract
JSON SCHEMACostCodeList
JSON SCHEMACostCode
JSON SCHEMAEmployeeList
JSON SCHEMAEmployee
JSON SCHEMAInvoiceList
JSON SCHEMAInvoiceRequest
JSON SCHEMAInvoice
JSON SCHEMALinkSessionRequest
JSON SCHEMALinkSession
JSON SCHEMAProjectList
JSON SCHEMAProject
JSON SCHEMATimesheetList
JSON SCHEMATimesheet
JSON SCHEMAVendorList
JSON SCHEMAVendor
JSON SCHEMAScroll within the panel for all 19 ·
JSON Structure 19
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Unified Api Budget List Structure
JSON STRUCTUREUnified Api Budget Structure
JSON STRUCTUREUnified Api Contract List Structure
JSON STRUCTUREUnified Api Contract Structure
JSON STRUCTUREUnified Api Cost Code List Structure
JSON STRUCTUREUnified Api Cost Code Structure
JSON STRUCTUREUnified Api Employee List Structure
JSON STRUCTUREUnified Api Employee Structure
JSON STRUCTUREUnified Api Invoice List Structure
JSON STRUCTUREUnified Api Invoice Request Structure
JSON STRUCTUREUnified Api Invoice Structure
JSON STRUCTUREUnified Api Link Session Request Structure
JSON STRUCTUREUnified Api Link Session Structure
JSON STRUCTUREUnified Api Project List Structure
JSON STRUCTUREUnified Api Project Structure
JSON STRUCTUREUnified Api Timesheet List Structure
JSON STRUCTUREUnified Api Timesheet Structure
JSON STRUCTUREUnified Api Vendor List Structure
JSON STRUCTUREUnified Api Vendor Structure
JSON STRUCTUREScroll within the panel for all 19 ·
Examples 19
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Unified Api Budget Example
EXAMPLEUnified Api Contract Example
EXAMPLEUnified Api Employee Example
EXAMPLEUnified Api Invoice Example
EXAMPLEUnified Api Project Example
EXAMPLEUnified Api Vendor Example
EXAMPLEScroll within the panel for all 19 ·
Security Posture 3
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Construction Software Integration
Construction software companies integrate with 100+ other platforms via a single API instead of building and maintaining individual integrations.
ERP and PM Sync
Automatically sync jobs, cost codes, and financials between project management systems like Procore and ERP systems like QuickBooks or Sage.
Invoice Processing Automation
Automate AP invoice capture, job matching, and ERP posting using AI-powered invoice processing workflows.
Job Costing
Pull budget, contract, commitment, and cost data from construction software for real-time job cost analysis and reporting.
Timesheet Integration
Sync employee timesheets from field systems to accounting ERPs to eliminate manual payroll data entry.
Document Management
Enable users to select and share files from connected construction document storage systems using Agave File Manager.
Integrations 10
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Procore
Full read/write integration with Procore for projects, budgets, contracts, commitments, and documents.
Autodesk Build
Integration with Autodesk Build for project management and document storage.
QuickBooks Online
Integration with QuickBooks Online for job costing, invoices, and financial data.
Sage 100 Contractor
Integration with Sage 100 Contractor for construction job costing and accounting.
Sage Intacct
Integration with Sage Intacct cloud ERP for construction financial management.
Viewpoint Vista
Integration with Viewpoint Vista for construction ERP including SQL-based data access.
ServiceTitan
Integration with ServiceTitan for field service management and job costing.
Acumatica
Integration with Acumatica cloud ERP for construction financial management.
Foundation
Integration with Foundation construction accounting software.
CMiC
Integration with CMiC enterprise construction ERP platform.
Scroll within the panel for all 10 ·
Resources
Every other property we hold for Agave — 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
Documentation 20
Reference material describing how the API behaves
Scroll within the panel for all 20 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 22
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 22 ·
Build 21
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 21 ·
Access & Security 5
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/agave · machine-readable index on apis.io