TX Procurement Change Monitor, ESBD Alerts (tx-esbd-changes)

Monitor the Texas government procurement feed and get only what changed since your last run - new solicitations, plus updates to ones you already saw, each carrying a field-level diff (field / oldValue / newValue).

Point it at a schedule and it becomes an alert feed: a bid extends its close date, an addendum lands, an award appears.

Low cost

From $0.03 per record - you are charged per changed record delivered, never for the query itself. The first run establishes your baseline and delivers (and charges) nothing. Runs are capped at $10.

What you get

New solicitations come back as normal normalized records; changed ones additionally carry changedFields:

{
  "bidNumber": "802-27-75102-BR",
  "title": "17ft Center Console Mud Boat Packages",
  "status": "Addendum Posted",
  "closeDate": "8/21/2026 2:00 PM",
  "changedFields": [
    { "field": "closeDate", "oldValue": "8/7/2026 2:00 PM", "newValue": "8/21/2026 2:00 PM" },
    { "field": "status",    "oldValue": "Posted",           "newValue": "Addendum Posted" }
  ]
}

changedFields is what separates this from a plain re-pull: you learn what moved, not just that something did. Records carry the same normalized shape as the rest of the family (agency, nigpCodes structured, publishedDate, closeDate, url, ).

Inputs

Input	What it does
snapshotKey	Names the stored snapshot to diff against. Use a distinct key per deployment so a test run never overwrites your production baseline.
pages	Scan depth from the newest record (24 records per page). Default 50. Capped at 300 per run.

Example inputs

A daily alert sweep - run it on a schedule and each run delivers only what moved since the last one:

{ "pages": 50 }

A wider sweep - raise pages to look further back from the newest record:

{ "pages": 300 }

A separate baseline for a second feed - set a distinct snapshotKey per deployment so two monitors never overwrite each other. The first run of a given key establishes its baseline and emits nothing; changes appear from the next run on:

{ "pages": 50, "snapshotKey": "my-watchlist-v2" }

Why this is hard

The source orders by last modified, not posted date, so "the top of the feed" is not "the newest solicitations" - a diff that assumes otherwise attributes the wrong records to the wrong run.

Matching is done on the bid number, an exact identifier, rather than on position in the feed - so a solicitation that moves in the ordering doesn't read as new.

The diff deliberately watches only the three fields that actually carry news - status, closeDate and lastModified - rather than comparing whole records. A whole-record comparison over this source produces constant noise (fields that restate themselves between fetches), which buries the real signal; narrowing to those three is what makes an alert worth opening.

Example output

A newly seen solicitation - the full normalized record, flagged changeType: "new":

{
  "platform": "tx-esbd",
  "agency": "Tx Dept Crim. Justice/inst Div - 696",
  "agencyNumber": "696",
  "title": "Region 1 Locks and Parts",
  "bidNumber": "IW265385",
  "status": "Posted",
  "publishedDate": "9/16/2026",
  "closeDate": "9/30/2026 3:00 PM",
  "nigpCodes": [
    {
      "code": "45055",
      "description": "Locks, Key Blanks, And Locksmith Tools  (Including Time Locks)"
    }
  ],
  "url": "https://www.txsmartbuy.gov/esbd/IW265385",
  "internalId": "558671",
  "created": "9/11/2026 2:14 pm",
  "lastModified": "9/16/2026 12:01 am",
  "changeType": "new"
}

A solicitation you have already seen comes back carrying changedFields instead - a field / oldValue / newValue list, as shown under What you get above.

The rest of the Texas family

Your goal	Actor
Find bids by keyword, NIGP, agency, status	tx-esbd-search
Check one specific bid by its number	tx-esbd-get
Monitor new & changed solicitations on a schedule	tx-esbd-changes - you are here
Who won state contracts, at what amounts	tx-esbd-awards
Find / vet a vendor - HUB, SDV, small business, NIGP capability	tx-cmbl-vendors
Find disabled-veteran (DV) HUB vendors	tx-hub-certified
Statewide contracts - who's on each SPD/TxSmartBuy contract	tx-smartbuy-contracts
Pull the raw full corpus (query + monitor) - power users	sled-tx-procurement

Notes

• Data source: Texas Comptroller - ESBD. Public state records.
• No login, no anti-bot - uses the official public JSON API.
• Each snapshotKey keeps its own baseline, so one account can run several independent monitors.
• Also available as a hosted MCP tool (j0401--tx-esbd-changes) for AI assistants.

License

MIT - see ./LICENSE.

Disclaimer

This product is an independent data service and is not affiliated with, endorsed by, or sponsored by the State of Texas or any government agency. All solicitation data is public government information. We recommend verifying any opportunity on the official portal before acting.