Bidlo

A heavy-civil market database exposed natively as machine-readable data rather than a UI: an MCP streamable-HTTP server plus a REST v1 API with an OpenAPI 3.1 spec, reading and writing the same collections the app shows. Entity model per the published docs: Projects with Project Items, Bid Items, Pre-Bid Q&A, Change Orders, Scopes and Files; Contractors with Facilities, Permits and related entities. Queryable fields include County, Bid Date, Type of Work, Primary Trade, Status (including Prequalified), Owner, Phone and Website. The standout collection is Soil Layer — geotechnical records carrying plasticity index and a geospatial location, queryable by radius around a lat/lng point — a subsurface-risk dataset sitting alongside the bid data. Field-level history is retained through the API so record changes are reconstructable, and the write path means bid results and contractor registries are maintained inside the system rather than merely observed.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Bidlo and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Heavy ConstructionApplication Software
Instruments: equities
Categories: Alternative

Dataset card

Type: not stated
Format: Tabular/JSON — REST v1 with an OpenAPI 3.1 schema, an MCP server exposing documents_query and related tools, cursor-paginated responses (limit 100, next_cursor), typed fields (date, text) with field IDs and value IDs, file attachments, comments, and full read/write. Agent-native by design: one of very few sources in this category already shaped for programmatic consumption.
Volume: Not published on the documentation page — record counts are absent by design. Structural scale indicators: a multi-collection entity model (Projects, Project Items, Bid Items, Pre-Bid Q&A, Change Orders, Scopes, Files, Contractors, Facilities, Permits, Soil Layer) at county-level granularity across a US footprint (the worked example targets Bexar County, Texas) with documented 100-per-page cursor pagination. Est. tens of thousands of projects and contractors with per-item bid detail; confirm counts per collection before pricing.
Users: Not disclosed; an 8-person construction-technology company with an app-plus-API product, so the base is contractor team accounts rather than registered consumers. Est. low hundreds of contractor accounts (inferred from headcount, startup-stage team, and a workflow product requiring per-team onboarding).
History: not stated
Update frequency: not stated
Growth: Active and building outward — the company has published a developer surface (MCP server, REST v1, OpenAPI 3.1 spec) rather than only a UI, which is a deliberate expansion move to invite third-party and agent consumption. An 8-person team that ships and documents a public API plus an MCP endpoint is investing, not maintaining.
Launched: ~2024-2026 (company record established mid-2024 in Orland Park, Illinois; the MCP-server-for-agents design places the developer surface at 2025-2026, since MCP adoption only became viable then. No launch date, press mention, or archive is published).
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site