TX ESBD Procurement Opportunities

Pull Texas Electronic State Business Daily (ESBD) solicitations - the official Texas state procurement portal - with structured NIGP commodity codes, full-corpus search, and change monitoring.

Built for AI agents, developers, and procurement tools that need a clean, queryable data layer over Texas state & local government bidding opportunities.

👋 First time here? Start with the right tool

There are 8 actors in the Texas procurement family - one per job. Don't guess; match your goal:

Your goal	Start here
Find bids / RFPs / contracts matching keywords, NIGP codes, agency or status	TX Government Contracts & Bids Search (tx-esbd-search) - start here
Check one specific bid by its bid number	TX Solicitation Lookup by Bid Number (tx-esbd-get)
Monitor new & changed solicitations on a schedule	TX Procurement Change Monitor (tx-esbd-changes)
Who won Texas state contracts, at what amounts	TX Government Contract Awards & Winners (tx-esbd-awards)
Find / vet a vendor - HUB, SDV, small business, NIGP capability, performance	TX Vendor Directory (CMBL) (tx-cmbl-vendors)
Find disabled-veteran (DV) HUB vendors - eligibility, county, NIGP	TX Disabled Veteran (DV) HUB Vendors (tx-hub-certified)
Statewide contracts - who's on each SPD/TxSmartBuy contract, by NIGP or vendor ID	TX Statewide Contracts (TxSmartBuy) (tx-smartbuy-contracts)
Pull the raw full corpus (query + monitor modes) - power users	TX ESBD Procurement Opportunities (sled-tx-procurement)

If you're a first-time user, recommended start: TX Government Contracts & Bids Search (tx-esbd-search) - the most common task is finding matching bids.

Predictable, low-cost pricing

• From $0.001 per record - the disabled-veteran (DV) HUB vendor directory costs a tenth of a cent per record; a single bid lookup is one cent.
• No surprise bills - every run is capped (main/search/awards/cmbl/hub/contracts $5 / changes $10 / get $1) so even a huge query can't run up a big charge.
• Free change monitoring on first run - the first changes run just establishes your baseline (no charge); you only pay for the alerts delivered after that.

Why this exists

Texas publishes all state solicitations on txsmartbuy.gov but only via an interactive web portal. Existing scrapers either:

• filter by keyword and drop the NIGP commodity codes (the most useful classification for matching your business),
• or only surface new opportunities, discarding the full history.

This suite treats the TX ESBD native JSON API as a first-class data source and exposes it as three semantic MCP tools.

What you get

Every solicitation record is normalized with structured NIGP codes (not a raw string):

{
  "platform": "tx-esbd",
  "agency": "Parks & Wildlife Department - 802",
  "agencyNumber": "802",
  "title": "17ft Center Console Mud Boat Packages",
  "bidNumber": "802-27-75102-BR",
  "status": "Awarded",
  "publishedDate": "7/24/2026",
  "closeDate": "8/7/2026 2:00 PM",
  "nigpCodes": [
    { "code": "12021", "description": "Boats, 21 Feet And Under" },
    { "code": "12063", "description": "Motors, Outboard, Gasoline" },
    { "code": "12090", "description": "Trailers, Boat" }
  ],
  "url": "https://www.txsmartbuy.gov/esbd/802-27-75102-BR",
  "created": "7/24/2026 8:25 am",
  "lastModified": "8/27/2026 4:10 pm"
}

Fields: platform, agency, agencyNumber, title, bidNumber, status, publishedDate, closeDate, nigpCodes (structured), url, created, lastModified.

Statuses: Posted / Awarded / Addendum Posted / Closed / No Award

Actors

Every actor is pay-per-event - you pay only for the records delivered (each actor's pricing tab shows its cap):

Actor	What it does	Price
TX Government Contracts & Bids Search, NIGP (AI-Ready) (tx-esbd-search)	Search by keywords / NIGP codes / agencies / status over the corpus.	$0.02 / matching record
TX Solicitation Lookup by Bid Number (ESBD) (tx-esbd-get)	Fetch a single solicitation by bid number.	$0.01 / record
TX Procurement Change Monitor (ESBD Alerts) (tx-esbd-changes)	New & updated solicitations since the previous run (field-level diff).	$0.03 / change alert
TX Government Contract Awards & Winners (ESBD) (tx-esbd-awards)	Who won Texas state contracts - winners, amounts, HUB status, VPTS performance grades. Our highest-value dataset.	$0.0175 / award record
TX Vendor Directory (CMBL) (tx-cmbl-vendors)	The full Texas Comptroller vendor list (~45k) - HUB, SDV, small-business flags, performance scores, NIGP capability, VPTS grade. Filter by keyword, city, category.	$0.0035 / vendor record
TX Disabled Veteran (DV) HUB Vendors (tx-hub-certified)	HUB directory - best for disabled-veteran (DV) vendors. Eligibility group, county, status, NIGP class. Caveat: currently-certified HUBs are ~99% DV; minority-owned certifications are mostly historical.	$0.001 / HUB vendor record
TX Statewide Contracts (TxSmartBuy) - Vendors, NIGP, VID (tx-smartbuy-contracts)	Comptroller statewide (SPD/TxSmartBuy) contracts - who's on each contract, with NIGP codes and exact vendor-ID enriched contractor profiles.	$0.02 / contract record
TX State Procurement Data (ESBD, NIGP Codes) (sled-tx-procurement)	The raw engine: full-corpus pull (query) and change diffing (monitor) with structured NIGP output. For developers who want the underlying data layer directly.	$0.02 / solicitation page (query or monitor)

For monitor needs, use tx-esbd-changes - it is purpose-built for change detection with field-level diff at $0.03/alert (cap $10), rather than sled's monitor mode at its flat $0.02/page (cap $5). Use sled in monitor mode only if you need the raw JSON structure or a custom integration.

For developers: the underlying data layer

The semantic actors (search / get / changes) are thin, focused views over one corpus. sled-tx-procurement is the engine underneath them - a raw, unopinionated data layer you can build your own pipeline on:

• mode: query - pull any slice of the full ~59k corpus with structured NIGP codes, filter server-side-equivalent by keyword / NIGP / agency / status, and get clean JSON records.
• mode: monitor - diff against a stored snapshot and emit only what changed (new / updated with oldValue / newValue), so you can run your own alerting without the semantic wrapper.
• Deterministic and inspectable - the exact same normalized schema the semantic tools use, no hidden transforms, no black box. What you get from the API is what your pipeline consumes.

The MCP tools are conveniences over this layer; if you prefer to wire the data yourself (Apify API - your database - your dashboards), this is the access point. Every other actor in this family is a packaged query against it.

Scanning depth & full-corpus chunking

pages is scan depth from the newest record, not a page offset - setting pages: 2500 scans every record (~40 min). main/search/changes/get run on a 30-min timeout, so for those a full scan must be chunked by date window or NIGP code (see below). tx-esbd-awards runs on a 60-min timeout and can do a full scan in one run.

Option A - date windows (via publishedAfter / publishedBefore, YYYY-MM-DD):

{"pages": 2500, "publishedAfter": "2026-01-01", "publishedBefore": "2026-03-31"}
{"pages": 2500, "publishedAfter": "2026-04-01", "publishedBefore": "2026-06-30"}

Run one chunk per quarter; each finishes well inside the timeout. The _meta record on every run reports the scanned date ranges, so you can confirm a chunk was fully covered.

Option B - NIGP code ranges (via nigpCodes):

{"pages": 2500, "nigpCodes": ["90000"]}   // Professional Services
{"pages": 2500, "nigpCodes": ["91000"]}   // Building Maintenance

Measured scan times (so you can size chunks): 100 pages ~ 95 s, 200 pages ~ 3 min, 500 pages ~ 8 min. For main/search/changes/get (30-min timeout) stay under ~1800 pages per run; tx-esbd-awards (60-min timeout) can run the full 2500.

Note: the source sorts solicitations by last modified, not posted date. publishedAfter filters correctly but a shallow scan can still miss old-posted records that were recently modified - use the _meta scan ranges to verify coverage.

MCP server

The three semantic tools are exposed via Apify's hosted MCP - no self-hosting needed.

{
  "mcpServers": {
    "tx-esbd": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes",
      "headers": { "Authorization": "Bearer <APIFY_TOKEN>" }
    }
  }
}

Tools available to your AI assistant:

• j0401--tx-esbd-search - keywords, nigpCodes, agencies, statuses, pages, limit
• j0401--tx-esbd-get - bidNumber, pages
• j0401--tx-esbd-changes - pages, snapshotKey

Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and any MCP client. Your APIFY_TOKEN from Apify Console -> Settings -> Integrations.

Talk to your AI assistant in plain English

Once the MCP tools are connected, you can ask your agent in natural language:

"Find Texas RFPs published in the last 7 days with NIGP code 92500 (Engineering Services), limit to 10."

"What is the current status and close date of bid UTSA129?"

"Have any addenda or deadline changes been posted in Texas procurement this week?"

The agent calls the MCP tools behind the scenes and returns structured answers you can feed straight into a spreadsheet, CRM, or another agent.

Use cases

• Government contractors - find bids matching your NAICS/NIGP codes so you never miss an opportunity in your category.
• Procurement AI startups - use the MCP server as a ready-made Texas data layer for your agent.
• Sales teams - identify which agencies award in your category for lead generation.
• Award intelligence - run tx-esbd-awards for the result, not the rumor: who actually won contracts in your NIGP category, at what amounts, and their HUB / VPTS performance grades. This is outcome data - the closest thing to a "who won the deal" answer - useful for competitive intelligence, win/loss analysis and market sizing, not just lead generation.
• Change alerts - run tx-esbd-changes on a schedule (Apify scheduler) to get notified of new postings and deadline changes. First run establishes a baseline (no charge); subsequent runs diff against it. Use a unique snapshotKey per deployment to keep baselines separate.
• AI workflows - feed structured opportunities directly into your agent's context without scraping HTML.

Notes

• Data source: Texas Comptroller - ESBD. All data is from public state records.
• No login, no anti-bot - uses the official public JSON API.
• Full corpus - ~59,000 active solicitations. pages = 24 records each; set pages: 2500 for the full snapshot (~40 min scan).
• Keyword search includes NIGP descriptions - searching "dental" also finds solicitations classified under NIGP Dental Services, even when the title doesn't say "dental".
• Default pages: 20 (search) / 50 (get, changes) - covers the newest ~480-1,200 records quickly. Raise it to search deeper; each run reports how many records it scanned so you know if results may be truncated.

Vendor profiles (CMBL + VPTS)

The CMBL actor returns each vendor's registration profile (HUB / SDV / small-business / QISV flags, business category, NIGP classification, performance scores) plus their VPTS performance grade, linked by exact vendor ID - no name guessing, so matches are exact (no false positives). Vendors without a VPTS record are returned with "vpts": null, never a guessed grade.

The awards actor also enriches winners with a VPTS grade when a name match is found - but note that ESBD awards carry no vendor ID, so this is a name-based match (roughly 3-4 in 10 awards find a VPTS record; the rest are vpts: null). For exact vendor-ID-linked performance, use the CMBL actor.

No subscription. You only pay for the records delivered.

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.