canonical: https://jentic.com/apis/agaveapi.com/agave

# Agaveapi Agave Unified Construction API

Jentic publishes the only available OpenAPI specification for Agave Unified Construction API, keeping it validated and agent-ready. Agave is a unified API for construction software integrations - instead of integrating separately with Procore, PlanGrid, Autodesk Build, and other construction platforms, an app integrates once with Agave and gets normalised access to projects, RFIs, submittals, documents, and vendors across all connected systems. The API uses Link tokens to handle the per-customer connection flow.

## For AI agents

Read and write construction project data - projects, RFIs, submittals, documents, vendors - across Procore, PlanGrid, Autodesk Build, and other platforms through one unified API.

## Scope

Does not handle accounting general ledger entries, payroll, or jobsite IoT telemetry - use for unified construction project, RFI, submittal, document, and vendor operations only.

## Capabilities

- Create a Link token to connect a customer's construction platform account to the integration
- List and inspect construction projects across all linked source systems
- Read and create RFIs (Requests for Information) without per-platform integrations
- Manage submittals across the connected project management platforms
- Sync construction documents from the source platform into downstream systems
- List vendors and subcontractors associated with a project
- Enumerate the linked accounts a customer has connected through Agave

## Use cases

### Construction Project Management Integration

Construction tech vendors (analytics, scheduling, AI assistants, accounting integrations) use Agave to read project data from whichever PM platform their customer happens to use - Procore, PlanGrid, Autodesk Build - without writing N integrations. The Link flow handles the connection per-customer; the integration then calls /projects, /rfis, /submittals, and /documents using a unified schema.

Example prompt: After a customer completes the Link flow, list their projects via GET /projects and pull all open RFIs via GET /rfis for the most recent project

### RFI and Submittal Workflow Automation

Project managers use third-party tools that read and post RFIs and submittals through Agave so the same workflow runs across platforms. The /rfis and /submittals endpoints return a normalised payload regardless of source, letting an automation rule (e.g., 'remind PM 3 days before submittal due') fire reliably across a portfolio with mixed PM tooling.

Example prompt: List all submittals via GET /submittals due in the next 14 days, then send each project manager a Slack reminder with the submittal title and due date

### Construction Document Sync

BIM and document collaboration tools use Agave to ingest the latest drawings and documents from the customer's project platform on a schedule. GET /documents returns a unified document list with metadata (revision, project, type) the downstream tool can use to upsert into its own storage.

Example prompt: Pull GET /documents for each linked project nightly and upsert any new revisions into the BIM document store

### AI Agent Construction Operations

Construction AI agents use Agave through Jentic to read RFIs, submittals, and project documents for the customer's connected platform and answer natural-language questions about project status. Jentic isolates the bearer token and Agave Link account references per call, so the agent never holds raw construction data credentials.

Example prompt: Search Jentic for 'list construction rfis', load the GET /rfis schema, and execute it for a specific project to summarise open RFIs in a status report

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/link/token/create` | Create a Link token for the connect flow |
| GET | `/linked-accounts` | List linked customer accounts |
| GET | `/projects` | List construction projects |
| GET | `/projects/{project_id}` | Retrieve a specific project |
| GET | `/rfis` | List RFIs across projects |
| GET | `/submittals` | List submittals across projects |
| GET | `/documents` | List project documents |
| GET | `/vendors` | List project vendors |

## Key resources

- **Authentication** — Link token creation and linked account management
- **Projects** — Construction projects across linked platforms
- **RFIs** — Requests for Information
- **Submittals** — Submittal records and statuses
- **Documents** — Construction documents and drawings
- **Vendors** — Project vendors and subcontractors

## Why Jentic

- **Setup:** Wiring the Agave Unified Construction API by hand means handling both a bearer token and an API key plus per-customer linked-account references, then coding calls across projects, RFIs, and submittals. Through Jentic you install once, import the Agave Unified Construction API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Agave puts the project id in the URL path (`/projects/{project_id}`), so a rule can pin the agent to one project. You choose which operations it may call, such as reading RFIs, submittals, and documents, so anything you leave out is not reachable.
- **Credential handling:** Your Agave bearer token, API key, and linked-account references are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list construction RFIs for a project', and Jentic returns the matching Agave operation with its parameter schema so the agent picks the right unified endpoint without browsing the reference docs.

## Related APIs

- **Procore API** — Direct API for the Procore construction platform, deeper but single-vendor.
- **Stripe API** — Payments platform commonly used to charge construction subcontractors and pay vendors.
- **Salesforce API** — CRM commonly used by construction firms for sales pipeline tracking.

## FAQ

### Why is there no official OpenAPI spec for Agave Unified Construction API?

Agave does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agave Unified Construction API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Agave Construction API use?

Agave uses two credentials together: a server-side bearer token (Authorization header) plus an API-Key header for the integration. Through Jentic, both are stored encrypted and injected per call so the agent never sees them.

### Can I read Procore data with the Agave Construction API?

Yes. Once your customer completes the Link flow for their Procore account, GET /projects, /rfis, /submittals, and /documents return Procore data through Agave's unified schema - no separate Procore integration required.

### What are the rate limits for the Agave Construction API?

The public spec does not list explicit limits. Agave proxies to upstream platforms (Procore, PlanGrid, etc.) which have their own limits, so heavy fetches should be paginated and back off on HTTP 429.

### How do I list a customer's RFIs through Jentic?

Search Jentic for 'list construction rfis', load the GET /rfis schema, and execute it referencing the customer's linked account id. Jentic returns the normalised RFI payload directly to the agent.

### How does the Link token flow work?

Call POST `/link/token/create` from your backend to mint a short-lived Link token, hand it to the customer's browser, and the customer authenticates against their construction platform. Agave returns a permanent linked-account id you reference on subsequent /projects, /rfis, and /documents calls.

### Can I limit what my agent is allowed to do with the Agave Construction API?

Yes. Because Jentic One is self-hosted, your own rules decide which Agave operations and credentials the agent may use. Since Agave puts the project id in the URL path (`/projects/{project_id}`), you can pin the agent to a single project, and you choose which operations it may call, such as reading RFIs, submittals, and documents. Anything you leave out, including creating Link tokens or listing vendors, stays unreachable to the agent.