Integrations, browser extension, and exports

Bidding-platform browser extension

The Chrome side-panel extension pairs a signed-in GAIA Civil tab with the user’s authorized session on a supported bidding platform. Strategies saved in Query Architect populate the extension’s GAIA Civil strategy dropdown, while an authorized user can also enter a Boolean query directly.

After the user reviews and selects projects and chooses Import selected projects, the extension automates the manual project click-through and plan-set download process. It applies the tenant-specific scope, gathers every authorized project document or page that matches it, and sends the resulting set directly to GAIA Civil. Opportunity screening places the set in the Project Hub Screening lane; full ingestion places it in the Full ingestion lane.

Quick Import removes the search-and-selection step when an authorized user is already viewing a single project document set. One button sends that project’s tenant-relevant matching pages directly into GAIA Civil screening.

• Every import remains user-initiated; batch search and selection and Quick Import are explicit user actions.
• Project metadata can be transferred even when entitled plan or specification files are unavailable.
• The extension does not automate sign-in, read passwords, or bypass source-platform permissions and document entitlements.
• Progress, limits, recovery behavior, and the selected processing path remain visible during the run.

Define each connection contract

• System and authenticated identity.
• Authorized objects, files, fields, and project scope.
• Read, write, or bidirectional data direction.
• Mapping, deduplication, retry, and failure behavior.
• Named approval point before an external write.
• Audit, retention, and deletion expectations.

Current customer-facing exports and downloads

The current signed-in workspace provides PDF-based report handoffs and source-document downloads. These controls preserve a reviewable artifact without implying that every internal service is a customer integration.

• Export Engineer Verification Packet.
• Export Report PDF and Export Chat PDF.
• Download a merged PDF created during project intake.
• Open or download the source PDF from Project Hub evidence details.

Implementation-specific interfaces

REST APIs, webhooks, MCP-compatible integrations, and JSON, CSV, and PDF outputs support approved workflows. Available interfaces and enabled user controls are separate: scope each connection, permission, output and destination for the customer workspace. Procore and AutoCAD / DXF are optional; native Salesforce, HubSpot and Dynamics connectors remain roadmap items.

Detail: MCP access and control plane

Model Context Protocol exposes approved tools and context to compatible AI clients. REST APIs, webhooks, MCP-compatible integrations, and JSON, CSV, and PDF outputs support approved downstream workflows.

Each connection is scoped to the authenticated customer, project, operation and allowed data. Define credentials, permissions, transport, mapping, retries, logging and human approval in its connection contract.

MCP changes where a workflow can start, not who can approve its result. A connected client cannot use a tool call to acquire broader project access or bypass external-write approval.

Detail: interface availability