# DFW Public Bids Scraper (Dallas-Fort Worth Government RFPs) (`adaptive_depths/dfw-public-bids`) Actor

Open solicitations from 11 Dallas-Fort Worth public procurement portals (Bonfire + OpenGov), filtered by trade, keyword and agency.

- **URL**: https://apify.com/adaptive_depths/dfw-public-bids.md
- **Developed by:** [ryan smith](https://apify.com/adaptive_depths) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 bids

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## DFW Public Bids

Pulls **currently open** solicitations from 11 Dallas–Fort Worth public procurement portals and filters them by trade, keyword and agency.

**Sources (public, unauthenticated list endpoints only):** City of Dallas, City of Fort Worth, City of Arlington, Denton County, Dallas ISD, Tarrant County College, DART, DFW Airport, NTMWD (Bonfire); Collin County, Tarrant Regional Water District (OpenGov).

### Input

| Field | Description |
|---|---|
| `trades` | `fire_protection`, `hvac`, `janitorial`, `landscaping`, `roofing`, `painting` (default fire_protection + hvac) |
| `keywords` | Extra free-text keywords; matches are returned even if no trade matches |
| `agencies` | Limit to specific portals (empty = all 11) |
| `maxResults` | Cap on items (0 = unlimited) |

```json
{"trades": ["fire_protection", "hvac"], "keywords": ["generator"], "agencies": []}
```

### Output (one item per bid)

`agency, agency_type, platform, ref, title, summary, due (America/Chicago ISO), estimated_value, url, trades, keywordMatches, scrapedAt`.
A `RUN_SUMMARY` record in the key-value store lists per-portal counts/errors.

### Notes

- Bids already past their deadline are dropped. Only titles/summaries are matched; bid documents are not downloaded.
- Schedule daily for an alert feed. Pricing: see PRICING.md (pay per bid returned).

# Actor input Schema

## `trades` (type: `array`):

Trade profiles to match (title/summary keywords and NAICS/NIGP codes).

## `keywords` (type: `array`):

Optional. Any bid whose title/summary contains one of these is also returned.

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

Leave empty for all 11 DFW portals.

## `maxResults` (type: `integer`):

0 = no limit

## Actor input object example

```json
{
  "trades": [
    "fire_protection",
    "hvac"
  ],
  "keywords": [],
  "maxResults": 0
}
```

# Actor output Schema

## `bids` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 = {
    "trades": [
        "fire_protection",
        "hvac"
    ],
    "keywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("adaptive_depths/dfw-public-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 = {
    "trades": [
        "fire_protection",
        "hvac",
    ],
    "keywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("adaptive_depths/dfw-public-bids").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "trades": [
    "fire_protection",
    "hvac"
  ],
  "keywords": []
}' |
apify call adaptive_depths/dfw-public-bids --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,adaptive_depths/dfw-public-bids"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

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