# City Council Contract Awards & Rezonings API (Agenda Data) (`implementable_antler/agenda-money-extractor`) Actor

Contract awards, vendors, $ amounts, rezonings, annexations, bonds and parcels extracted from city & county council agendas (Legistar) in the western US, with approval status from minutes. Government contracts and land-use leads as CSV/JSON/API.

- **URL**: https://apify.com/implementable_antler/agenda-money-extractor.md
- **Developed by:** [Blake Runckel](https://apify.com/implementable_antler) (community)
- **Categories:** Lead generation, Business, Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 results

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

## City Council Contract Awards & Rezonings API (Agenda Data)

Turn city council and county board **agendas into structured data**: **government contract awards** (vendor, dollar amount, not-to-exceed), **rezonings, variances, annexations**, bond issues, RFPs and settlements, with **parcel numbers / addresses** and the **approval status from the minutes**. 109 US cities and counties in 26 states (Boston, Denver, Phoenix, Columbus, Pittsburgh, Baltimore, Milwaukee, Kansas City, Nashville, Louisville, Sacramento, San Jose, Seattle, Broward County, Clark County NV, DuPage County, and more). Includes a weekly **"who won city money"** ranking of the largest **city contract awards** by vendor and amount. Export CSV, Excel or JSON, or call it as an API.

**Who buys this:** contractors and subcontractors chasing **public contract awards and bid leads**; homebuilders and land acquisition teams tracking **rezoning and annexation**; muni-bond and equity analysts following **city vendor spend**; journalists and government-affairs teams. Existing agenda scrapers give you a PDF link; this gives you the vendor, the dollars and the parcel.

### Sample output

| meetingDate | jurisdiction | signalType | amount | amountType | vendors | parcels / addresses | status | title |
|---|---|---|---|---|---|---|---|---|
| 2026-10-20 | Denver | contract_award | $11,000,000 (new total $82,200,000) | change | Securitas Security Services USA, Inc. |  | Approval Review | Amends a contract with Securitas Security Services USA, Inc. to add $11,000,000.00 for a new total of $82,200,000.00 |
| 2026-10-20 | Sacramento | contract_award | $675,000 | notToExceed | Robert Thompson (dba Legacy Ranching) |  | Agenda Ready | \[Contract] Grazing Services - Fuel Reduction and Vegetation Management |
| 2026-10-20 | Clark County | contract_award | $600,000 (new total $1,600,000) | change | Full Circle Events, Inc. |  | Approved | Approve an Amendment and increase funding to the Contract with Full Circle Events, Inc. |
| 2026-10-21 | Phoenix | contract_award | $206,631 | total | MCI Communications Services LLC |  | Agenda Ready - Fire Department | Verizon Connectivity Contract - RFA 26-0358 Request for Award |
| 2026-10-27 | San Jose | contract_award | $1,200,000 | notToExceed | HomeFirst Services of Santa Clara County | 901 E. Santa Clara Street, 1780 Hillsdale Avenue | Agenda Ready | Grant Agreement with HomeFirst Services of Santa Clara County for City Designated Overnight Warming Locations |
| 2026-10-22 | Fresno | annexation |  |  |  |  | Agenda Ready | HEARING to Adopt Resolutions and Ordinance to Annex Territory and Levy a Special Tax Regarding City of Fresno Community Facilities District No. 9 |
| 2026-10-20 | San Jose | rezoning |  |  |  | 525 Race Street | Agenda Ready | GP26-002 - Early Consideration for a Privately-Initiated General Plan Amendment |
| 2026-10-19 | Denver | rezoning |  |  |  | 2246 North Federal Boulevard | Second Reading w/Public Hearing | A bill for an ordinance changing the zoning classification for 2246 North Federal Boulevard |

### Quick start

```json
{
  "clients": [
    "sanjose",
    "sacramento",
    "denver"
  ],
  "daysBack": 14,
  "daysAhead": 14,
  "signalTypes": [
    "contract_award",
    "rezoning"
  ],
  "minAmountUsd": 100000,
  "maxItems": 200
}
```

### Input

| Field | Description |
|---|---|
| `clients` | Jurisdiction ids (see README coverage table), e.g. seattle, sanjose, sacramento, denver, phoenix, bend, deschutes. Empty = the 10 largest-budget defaults. |
| `daysBack` | Meetings from this many days ago. |
| `daysAhead` | Include upcoming meetings whose agendas are already posted (proposed items). |
| `dateFrom` | YYYY-MM-DD; overrides Days back. |
| `dateTo` | YYYY-MM-DD; overrides Days ahead. |
| `signalTypes` | Only these signal types. Empty = all. |
| `minAmountUsd` | Only items whose extracted amount is at least this. Items without an amount are dropped when set. |
| `keywords` | Only items whose title or vendor contains any of these (case-insensitive). |
| `allBodies` | By default only councils, boards of supervisors/commissioners and planning commissions are read. |
| `maxMatterTexts` | Full item text (recommendation/resolution) is fetched for items whose title has no $ amount. Lower = faster. |
| `maxPdfs` | PDF fallback (only where the host's robots.txt allows). |
| `maxItems` | Maximum rows. |

### Coverage

109 US cities and counties in 26 states on the public Legistar Web API (verified 2026-10-20). Counts: signals / contract awards with a $ amount, 30-day test run (2026-09-20 to 2026-10-20).

| State | Jurisdictions (`id`: signals / priced awards) |
|---|---|
| AR | Jonesboro (`jonesboro`: 15/7) |
| AZ | Mesa (`mesa`: 17/10), Phoenix (`phoenix`: 64/48), Pima County (`pima`: 61/33) |
| CA | Alameda (`alameda`: 18/15), Chino (`chino`: 12/5), Costa Mesa (`costamesa`: 10/5), Cupertino (`cupertino`: 8/3), Dublin (`dublin`: 2/2), Fontana (`fontana`: 17/7), Fresno (`fresno`: 16/7), Fullerton (`fullerton`: 15/6), Goleta (`goleta`: 3/1), Hayward (`hayward`: 9/5), Hesperia (`hesperia`: 8/4), Huntington Beach (`huntingtonbeach`: 17/2), Manhattan Beach (`manhattanbeach`: 4/3), Monterey County (`monterey`: 84/54), Mountain View (`mountainview`: 9/4), Murrieta (`murrieta`: 395/3), Napa (`napa`: 37/27), Newport Beach (`newportbeach`: 17/0), Oakland (`oakland`: 34/13), Pomona (`pomona`: 30/7), Redondo Beach (`redondo`: 29/18), Rialto (`rialto`: 16/9), Sacramento (`sacramento`: 50/45), Salinas (`salinas`: 4/4), San Bernardino (`sanbernardino`: 118/59), San Jose (`sanjose`: 16/7), San Mateo County (`sanmateocounty`: 38/32), Santa Barbara County (`santabarbara`: 61/32), Santa Clara County (`santaclara`: 22/13), Solano County (`solano`: 28/11), Stockton (`stockton`: 17/14), Sunnyvale (`sunnyvaleca`: 11/6), Visalia (`visalia`: 24/14), Westminster (`westminsterca`: 6/0) |
| CO | Arapahoe County (`arapahoe`: 6/0), Colorado Springs (`coloradosprings`: 21/0), Denver (`denver`: 253/170), Douglas County (`douglascounty`: 40/22) |
| FL | Brevard County (`brevardfl`: 17/0), Broward County (`broward`: 88/49), Clearwater (`clearwater`: 55/36), Coconut Creek (`coconutcreek`: 9/5), Coral Gables (`coralgables`: 25/5), Doral (`doral`: 13/3), Fort Lauderdale (`fortlauderdale`: 41/9), Hillsborough County (`hillsboroughcounty`: 0/0), Martin County (`martin`: 9/6), Miramar (`miramar`: 8/3), Ocala (`ocala`: 52/23), Pinellas County (`pinellas`: 47/27), Venice (`venice`: 28/2), Wellington (`wellington`: 19/12) |
| GA | Fulton County (`fulton`: 49/25) |
| IL | DuPage County (`dupage`: 81/60), Joliet (`joliet`: 45/30), Naperville (`naperville`: 21/18), Rockford (`rockfordil`: 58/27) |
| KS | Olathe (`olatheks`: 38/0) |
| KY | Louisville Metro (`louisville`: 33/5) |
| MA | Boston (`boston`: 60/43) |
| MD | Baltimore (`baltimore`: 29/3) |
| MI | Ann Arbor (`a2gov`: 41/24) |
| MN | St. Paul (`stpaul`: 44/2) |
| MO | Kansas City (`kansascity`: 131/34) |
| NC | Durham County (`durhamcounty`: 24/5), Guilford County (`guilford`: 20/13), Mecklenburg County (`mecklenburg`: 7/0), Wake County (`wake`: 9/1) |
| NH | Concord (`concordnh`: 11/0) |
| NJ | Newark (`newark`: 86/7) |
| NV | Clark County (`clark`: 99/43) |
| NY | Albany County (`albanycounty`: 12/11), Yonkers (`yonkersny`: 7/0) |
| OH | Cincinnati (`cincinnatioh`: 74/16), Columbus (`columbus`: 281/154), Hudson (`hudson`: 44/0), Toledo (`toledo`: 101/64) |
| PA | Pittsburgh (`pittsburgh`: 152/79) |
| TN | Nashville (`nashville`: 72/1) |
| TX | Corpus Christi (`corpuschristi`: 35/13), Killeen (`killeen`: 29/15), League City (`leaguecity`: 24/18), McKinney (`mckinney`: 25/18), Mesquite (`mesquite`: 42/26), New Braunfels (`newbraunfels`: 36/0), Pflugerville (`pflugerville`: 19/8), Plano (`plano`: 21/14), Round Rock (`roundrock`: 7/0), San Marcos (`sanmarcos`: 8/1) |
| VA | Alexandria (`alexandria`: 11/0), Hampton (`hampton`: 8/0), Richmond (`richmondva`: 125/2) |
| WA | Bellevue (`bellevue`: 7/0), King County (`kingcounty`: 8/2), Olympia (`olympia`: 8/0), Redmond (`redmond`: 6/2), Seattle (`seattle`: 3/0), Snohomish County (`snohomish`: 0/0), Tacoma (`cityoftacoma`: 25/9), Whatcom County (`whatcom`: 30/13) |
| WI | Dane County (`dane`: 33/0), Madison (`madison`: 190/12), Milwaukee (`milwaukee`: 34/2), Milwaukee County (`milwaukeecounty`: 20/1), Waukesha (`waukesha`: 8/1) |

Default (empty `clients`): seattle, kingcounty, sanjose, oakland, sacramento, denver, phoenix, mesa, fresno, clark. Bend and Deschutes County, OR are **not** included: their agenda portals' robots.txt disallow automated access.

### Fields

`recordId`, `jurisdiction`, `state`, `platform`, `legistarClient`, `meetingDate`, `body`, `agendaNumber`, `fileNumber`, `matterType`, `signalType` (primary), `signalTypes` (all), `title`, `amount` (the amount of this action: for amendments the added/removed amount, else the contract / not-to-exceed / award value), `amountType` (change / notToExceed / total / stated / bondAmount), `contractTotal` (new or revised contract total when stated), `amounts` (every $ figure with its text, a notToExceed flag and its kind: change / total / budget / stated), `vendors` (private or nonprofit counterparties; empty when the item names none; public agencies, grantors, applicants and settlement parties are never listed as vendors), `parcels` (APN/parcel ids), `addresses`, `acres`, `consent`, `status` (action and pass/fail from minutes, or the agenda status), `statusNormalized` (approved / failed / continued / withdrawn / pending), `passed`, `tally`, `textSource` (title or matterText), `documentUrl`, `agendaUrl`, `minutesUrl`, `meetingUrl`, `sourceUrl`, `extractionMethod`, `source`.

Re-run on a schedule: when the minutes post, the same `recordId` comes back with `statusNormalized` moving from pending to approved/failed.

### How it works

1. Meetings and agenda items come from the public **Legistar Web API** (only jurisdictions that publish it without a token).
2. When an item title has no dollar figure, the item's full legislative text (recommendation/resolution) is read from the same API.
3. Signals, amounts, vendors, parcels, addresses and acres are extracted with **deterministic rules (no AI guessing)**, so the same input always gives the same output. Every row links to its source.
4. PDF attachments are read only from hosts whose robots.txt allows it (Legistar's attachment host does not, so most rows use the API text).

### Limitations

- Extraction is rule-based. On a 2026-10-20 ten-city feed test (243 contract-award rows, checked against the Legistar source text), a 124-row held-out half scored: vendor 84%, amount 71%, award type 75%, is-a-contract-award 81%. Common misses: the amount picked up is a budget transfer or an old contract total; items that are grants received or intergovernmental deals flagged as awards. Two earlier 50-row blind holdouts of all agenda signals scored vendor 86–90%, amount 98–100%, item type 96%. Always check `amounts` and the source link before acting.
- Coverage is what each jurisdiction posts in Legistar; committee items are skipped unless `allBodies` is on.

### Pricing

**Pay per result: $8 per 1,000 extracted agenda signals ($0.008 per result)**, plus a $0.00005 Apify start fee per run. You pay only for rows written to your dataset; Apify platform usage (compute) is included in that price, not billed separately. Set a maximum cost per run in Apify Console or the API and the run stops at that limit. Users on the Apify free plan can try it within their free monthly credit.

### Attribution

Public meeting records published by each jurisdiction through Granicus Legistar. Independent tool by Ledger; not affiliated with or endorsed by Granicus or any jurisdiction.

# Actor input Schema

## `clients` (type: `array`):

Jurisdiction ids (see README coverage table), e.g. seattle, sanjose, sacramento, denver, phoenix, bend, deschutes. Empty = the 10 largest-budget defaults.

## `daysBack` (type: `integer`):

Meetings from this many days ago.

## `daysAhead` (type: `integer`):

Include upcoming meetings whose agendas are already posted (proposed items).

## `dateFrom` (type: `string`):

YYYY-MM-DD; overrides Days back.

## `dateTo` (type: `string`):

YYYY-MM-DD; overrides Days ahead.

## `signalTypes` (type: `array`):

Only these signal types. Empty = all.

## `minAmountUsd` (type: `integer`):

Only items whose extracted amount is at least this. Items without an amount are dropped when set.

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

Only items whose title or vendor contains any of these (case-insensitive).

## `allBodies` (type: `boolean`):

By default only councils, boards of supervisors/commissioners and planning commissions are read.

## `maxMatterTexts` (type: `integer`):

Full item text (recommendation/resolution) is fetched for items whose title has no $ amount. Lower = faster.

## `maxPdfs` (type: `integer`):

PDF fallback (only where the host's robots.txt allows).

## `maxItems` (type: `integer`):

Maximum rows.

## Actor input object example

```json
{
  "clients": [
    "sanjose",
    "sacramento",
    "denver"
  ],
  "daysBack": 14,
  "daysAhead": 14,
  "signalTypes": [],
  "allBodies": false,
  "maxMatterTexts": 300,
  "maxPdfs": 20,
  "maxItems": 200
}
```

# Actor output Schema

## `results` (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 = {
    "clients": [
        "sanjose",
        "sacramento",
        "denver"
    ],
    "daysBack": 14,
    "maxItems": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("implementable_antler/agenda-money-extractor").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 = {
    "clients": [
        "sanjose",
        "sacramento",
        "denver",
    ],
    "daysBack": 14,
    "maxItems": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("implementable_antler/agenda-money-extractor").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 '{
  "clients": [
    "sanjose",
    "sacramento",
    "denver"
  ],
  "daysBack": 14,
  "maxItems": 200
}' |
apify call implementable_antler/agenda-money-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,implementable_antler/agenda-money-extractor"
        }
    }
}
```

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/tGQCYb0icou27dPH7/builds/KaXzAM7fz6nrIPZGm/openapi.json