What a public bid feed is worth, and what it should cost.

Almost every bad purchase in this category starts the same way: a contractor asks for "government bids" and gets quoted a product that solves a different problem than the one they have. There are three jobs here. They are priced differently, they integrate differently, and only one of them is genuinely hard.

If you are going to pipe a bid feed into anything automated, these are the four properties that decide whether the integration is a scoped project or an open-ended one. They are worth more than coverage claims, because coverage you can verify after you buy, and these you cannot.

• A published spec you can read before you buy This is the difference between an integration you can scope and quote, and one where the first honest estimate arrives after the contract is signed. One platform in this field publishes a full OpenAPI spec at a public URL. Most publish nothing.
• An update-check field for incremental sync A documented "what changed since" timestamp is what makes a delta poll cheap and correct. Without one you are re-scanning the whole result set on a schedule and diffing it yourself, which is slower, more expensive, and quietly misses amendments.
• A saved-search handle, so precon owns targeting If a saved search built in the web interface can be referenced by ID from the API, your estimating lead retunes what the team hunts for without a developer touching anything. If it cannot, every change to a NAICS code or a dollar threshold becomes a ticket.
• Solicitation documents reachable by API A row in a table is not a bid package. If the drawings and specs cannot be pulled programmatically, somebody is downloading them by hand, and the automation stops one step short of the thing that actually costs time.

Where this gets uncomfortable

One platform in this comparison ships all four. Its full OpenAPI specification sits at a public URL, so an integrator can scope the work before anyone signs a contract. Its documented update-check field makes incremental sync straightforward. Saved searches are addressable by ID. Documents come back as download URLs, though those expire after about an hour, so you fetch on demand rather than caching the link.

The capture-intelligence platform is a harder read, and not because the API is bad. It is because almost nothing about it is knowable from outside the paywall. The only public documentation we could find is a four-page PDF dated June 24, 2015. There is no developer portal, no OpenAPI spec, no published endpoint reference and no sandbox. An integrator cannot scope the build until the customer has already bought.

And there is one line in that document worth reading twice, because if it means what it appears to mean, it reintroduces exactly the manual step an automation exists to delete. From the platform's own Web Services API documentation:

"Users can select opportunities for download by selecting the 'Add to Web Services Download' button. Opportunities are not pushed immediately. The selected set of Opportunities is available to be downloaded via the API."

GovWin IQ Web Services API documentation, PDF dated June 24, 2015. Retrieved July 31, 2026.

The same document also says a search can run "either by applying search filters or referencing one of your saved searches," which suggests a filter-driven pull may bypass that button entirely. We could not resolve this from public documentation, and we are not going to pretend we did. If you are evaluating that platform, this is the single question to put to their sales engineer in writing before you sign: does the API return opportunities matching a saved search automatically, or does a human have to select them first?

There is a second unknown alongside it. The daily download volume is capped, and the cap is contractual rather than published. The number appears in your negotiation, not in any document you can read beforehand.

Every aggregator sells breadth, and breadth is a coverage claim you cannot verify from outside. So before we ingest a state, we take it apart ourselves: what does the law require, which portal is authoritative, is there an aggregate feed, and does the gate sit on viewing a solicitation or on responding to one. Here is that teardown for Arkansas, which we ran on August 5, 2026. The answers surprised us, and one of them is stronger than anything a vendor can offer.

The statute does something no commercial database can

Arkansas Code § 22-9-203 governs how public improvement contracts get advertised — major repairs, alterations, erection of buildings or other structures, other permanent improvements. Above an estimated cost of $35,000, such a contract cannot be entered into unless notice of intention to receive bids was published first. For a county, municipality, school district or other local taxing unit, that notice must run once a week for not less than two consecutive weeks, in a newspaper of general circulation published in the county where the improvements are to be made, with the last publication no less than one week before the day fixed for receiving bids.

Read what that means commercially. Every county, municipal and school-district construction project in that state above $35,000 is required by statute to appear in a newspaper legal notice. Not as a best-effort commercial database with coverage gaps and a sales rep to explain them — as a legal precondition to entering the contract at all. A feed built on that surface is complete by construction for that class of work, and no aggregator can make the same claim about its own coverage.

Two qualifiers, because the detail is the whole argument

It is the newspaper, and a trade journal does not replace it. For local taxing units the statute is explicit: a trade journal reaching the construction industry may be published in addition to the required newspaper notice, never instead of it. State agencies are the exception. Their branch of the same statute reads "newspaper ... or in a trade journal," so for state-agency work the newspaper surface is not guaranteed and the completeness argument above does not hold. Most public building work a contractor would chase is let by the local bodies rather than the state agency, which is exactly why this distinction is worth stating instead of glossing.

There is a second mandated surface. If the local body accepts electronically submitted bids, it must also post notice on the website of a vendor designated under the Fair Notice and Efficiency in Public Works Act (§ 22-9-901 et seq.). That is a second statutorily required posting, in a structured electronic venue, running in parallel with the newspaper notice.

We read this against the copy of the statute published on the state Department of Education's own document server, which is current through the 2019 Regular Session. Statutes get amended. Confirm the current text before building anything expensive on it, and confirm the equivalent rules for your own state, because they are not the same.

Which means the newspapers are the feed

The state press association runs a statewide public-notice aggregator where member newspapers upload their notices daily. It is the electronic face of that statutory mandate, it requires no login, and it carries category filters including Architecture, Construction/Engineering and Demolition/Excavating, plus filters for all 75 counties, specific publications, date ranges and keywords.

And the state eProcurement portal mostly is not

This is the part we got wrong going in. We assumed the state's eProcurement system was where public construction lived. It is publicly readable without a login — the gate sits on responding to a solicitation, not on viewing one, which is useful to know. But on the day we checked it, the open-bid list carried two solicitations, both services, and zero construction. It is where state agencies buy goods and services. Register anyway, because it costs nothing but an afternoon. Do not model it as the primary feed for building work.

The signal that arrives 12 to 24 months early

The statutory notice is the last step, not the first. A district approves a project, picks a delivery method and interviews contractors before that notice ever runs. By the time the legal notice publishes, the relationships are frequently already formed. School board agendas are where that shows up first, and they are tractable because districts publish through a small number of common agenda platforms with predictable public URL shapes. A bond or millage election is the loudest early signal there is: money gets approved 12 to 24 months before a bid notice runs.

A government feed opens the prime lane — the jobs where you bid the agency directly. That is a real and often underused lane for a self-performing contractor. But it is worth being clear about what it does not do.

Sub work on public projects mostly still reaches you the same way it always has: as an invitation from the prime contractor, arriving down the rail you are already running. Buying a government bid platform does not change how that invitation gets to you. If most of your public work arrives as a sub invite, a gov feed is an expansion into a new lane, not an improvement to your existing one. Price it accordingly, and be honest with yourself about which lane you are actually trying to fix.