# Government Procurement Bids & RFPs (SLED eProcurement) (`jadey_orbit/gov-procurement-bids`) Actor

Open bids and RFPs from US state & local government eProcurement platforms — Bonfire, DemandStar, PlanetBids and more — normalized into one feed with agency, deadline, category and links. Pay per bid.

- **URL**: https://apify.com/jadey\_orbit/gov-procurement-bids.md
- **Developed by:** [Matt Sparks](https://apify.com/jadey_orbit) (community)
- **Categories:** Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 bid record delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Government Procurement Bids & RFPs (SLED eProcurement)

**Open bids and RFPs from US state & local government eProcurement platforms — normalized into one feed.** Instead of checking a different portal for every city, county, and school district, get every open solicitation across **Bonfire** and **OpenGov Procurement** in a single structured dataset. Pay per bid.

### What you get per bid

`platform`, `agency`, `agencyPortal`, `title`, `bidNumber`, `status`, `publishedDate`, `closeDate`, `url`.

```json
{
    "platform": "opengov",
    "agency": "Orange County, CA",
    "title": "Refuse Collection Vehicles and Supporting Equipment",
    "bidNumber": "27-06T",
    "status": "open",
    "publishedDate": "2026-07-14",
    "closeDate": "2026-08-18",
    "url": "https://procurement.opengov.com/portal/ocgov/projects/573"
}
```

### Why this actor

- **Many agencies, one call** — pulls open solicitations across a built-in directory of government portals on each platform, normalized to one schema.
- **Public bid boards** — these platforms exist to post public solicitations; no login, no private data.
- **Bring your own agency** — add any Bonfire subdomain or OpenGov portal code via the `agencies` input to track exactly the governments you sell to.
- **Pay per bid** — no subscription. Compare: GovSpend and Deltek GovWin sell state/local bid intelligence at $11k–$42k/year.

### Coverage

| Platform | Method | Status |
|---|---|---|
| **Bonfire** (`*.bonfirehub.com`) | public JSON API | ✅ live |
| **OpenGov Procurement** (`procurement.opengov.com`) | public portal | ✅ live |
| Ionwave, PlanetBids | browser-based | roadmap |
| DemandStar, BidSync | login-gated (excluded) | — |

The actor ships with a directory of confirmed public portals on each platform and lets you add your own. (These platforms don't publish a tenant list, so coverage grows over time — request agencies via the Issues tab.)

### Pricing

| Event | Price | When charged |
|---|---|---|
| Actor start | $0.02 | Once per run |
| Bid record | $0.02 | Per bid delivered |

**Example**: 300 open bids across the built-in directory ≈ $0.02 + $6.00 = **$6.02**.

### Input

```json
{
    "platforms": ["bonfire", "opengov"],
    "agencies": ["broward", "ocgov"],
    "keyword": "consulting",
    "openOnly": true,
    "maxBids": 500
}
```

- **platforms** — which eProcurement platforms to pull from
- **agencies** — optional: your own portals (Bonfire subdomain or OpenGov code) added to the built-in directory
- **keyword** — only keep bids whose title/number contains this text
- **openOnly** — only solicitations whose close date is in the future

### Use cases

- **Government contractors** — find every open RFP you can bid on, across jurisdictions
- **Sales teams selling to government** — monitor buying activity by agency
- **Market intelligence** — track what state & local governments are procuring
- **Nonprofits & researchers** — the public solicitation record, structured
- **AI agents** — an MCP-callable "what RFPs opened this week for X?" tool ([Apify MCP server](https://docs.apify.com/platform/integrations/mcp))

### Notes

- Only public bid-listing data is collected — no login, no account, no private data.
- The listing carries title, agency, bid number, and close date; full documents/categories live on each portal's detail page (linked via `url`).
- Want more platforms (Ionwave, PlanetBids), category/NAICS enrichment, or webhook alerts on new matching bids? Open an issue in the **Issues** tab.

# Actor input Schema

## `platforms` (type: `array`):

Which eProcurement platforms to pull open bids from. Leave empty for all supported platforms.

## `agencies` (type: `array`):

Optional: your own agency portal identifiers to add to the built-in directory. For Bonfire use the subdomain (e.g. <code>broward</code> for broward.bonfirehub.com); for OpenGov use the portal code (e.g. <code>ocgov</code>). These are tried against every selected platform. Empty = use only the built-in directory.

## `keyword` (type: `string`):

Only keep bids whose title/description contains this text (case-insensitive).

## `openOnly` (type: `boolean`):

Only include solicitations whose close date is in the future.

## `maxBids` (type: `integer`):

Maximum number of bid records to return.

## `proxyConfiguration` (type: `object`):

Proxy settings. Residential recommended for large multi-agency pulls.

## Actor input object example

```json
{
  "platforms": [
    "bonfire",
    "opengov"
  ],
  "agencies": [],
  "openOnly": true,
  "maxBids": 500,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "agencies": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("jadey_orbit/gov-procurement-bids").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "agencies": [] }

# Run the Actor and wait for it to finish
run = client.actor("jadey_orbit/gov-procurement-bids").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "agencies": []
}' |
apify call jadey_orbit/gov-procurement-bids --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=jadey_orbit/gov-procurement-bids",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/qW0mYMXCaTWav4Zke/builds/jyYco8IvFOC5yInIg/openapi.json