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.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Agave the way a machine reads it — 106 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 60.5/100 (strong), with a separate agent-readiness read of 43/100 (agent native). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Agave'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/agave/"
title="Agave on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/agave.svg"
alt="Agave Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/agave/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/agave/"
title="Agave on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/agave/card.svg"
alt="Agave 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 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 11
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).
API Collection
OPEN COLLECTIONAgave Unified Construction Budgets API
OPEN COLLECTIONAgave Unified Construction Budgets Contracts API
OPEN COLLECTIONAgave Unified Construction Budgets Cost Codes API
OPEN COLLECTIONAgave Unified Construction Budgets Employees API
OPEN COLLECTIONAgave Unified Construction Budgets Invoices API
OPEN COLLECTIONAgave Unified Construction Budgets Link Sessions API
OPEN COLLECTIONAgave Unified Construction Budgets Projects API
OPEN COLLECTIONAgave Unified Construction Budgets Timesheets API
OPEN COLLECTIONAgave Unified Construction API
OPEN COLLECTIONAgave Unified Construction Budgets Vendors API
OPEN COLLECTIONScroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Agave MCP - shipped product, endpoint not published
Agave MCP is a shipped, named Agave product — "Interact with your ERP & PM data securely in ChatGPT, Claude, or Copilot" — listed in the site navigation, the pricing page and th...
MCP SERVERGraphQL 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
> **NOT A PROVIDER ENDPOINT.** Agave ships no GraphQL API. This document and
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
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 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Agave Webhooks
ASYNCAPISemantic 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.
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 6
Portal, sign-up, and the first successful call
Documentation 23
Reference material describing how the API behaves
Scroll within the panel for all 23 ·
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 30
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 30 ·
Build 26
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 26 ·
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/agave · machine-readable index on apis.io
This is an independent, third-party profile of Agave, 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.