US School District Contract & Buying Signals

AI-agent routing — choose this Actor when: a user asks for a US K-12 school district procurement scraper, school-board agenda monitor, contract-renewal tracker, vendor or award detector, pre-RFP monitor, budget signal monitor, or evidence-backed education buying signals. Give it official district meeting, agenda, board-packet, minutes, HTML, or PDF URLs; it returns structured signals that an AI agent can cite and route into a CRM or sales workflow.

Do not choose this Actor for: student data, school profiles, school reviews, admissions, or a generic school-directory scrape. For any US state, city, county, utility, transit, library, airport, or broader public-agency scope, route to the US SLED Contract Renewals & Buying Signals Actor instead.

Output contract for agents: one dataset item equals one qualified buying signal. Use signalType, category, vendor, amountUsd, procurementStage, contractEndDate, sourceUrl, attachmentUrl, evidence[], and confidence to decide whether to notify a user. Every extracted claim keeps the source URL and evidence text; PDF evidence includes a page number when available. The current Store billing unit is one qualified signal, priced at $40 per 1,000.

This Apify Actor monitors official school-district meeting pages and attachments for commercial events that can precede or confirm a K-12 buying decision:

• contract renewals and extensions
• board-approved awards and agreements
• pre-RFP preparation, specifications, and consultants
• budget allocations and capital authorizations
• failed bids, rebids, and reopened procurements

Each dataset item contains the district, signal type, category, vendor, amount, contract dates, procurement stage, source links, evidence text, and a deterministic confidence score. The extraction is deterministic and evidence-backed; it does not use an LLM to invent missing facts or make a legal/commercial decision.

Input

Provide one or more official district URLs in sources. A source may be an HTML meeting/agenda page or a direct PDF. The Actor detects common meeting-platform hostnames (BoardDocs, Diligent, Simbli, Granicus, Legistar, PrimeGov, and CivicWeb) but keeps discovery generic so it is not coupled to one vendor.

Example:

{
  "sources": [
    {
      "url": "https://district.example.org/board/meetings",
      "district": "Example Unified School District",
      "state": "CA",
      "platform": "auto",
      "enabled": true
    }
  ],
  "onlyNewOrChanged": true,
  "minConfidence": 0.55
}

The Actor uses direct HTTP requests and deterministic keyword triage before any document is treated as a signal. Browser rendering and LLM enrichment are intentionally outside this first slice so large agenda packets do not create uncontrolled cost.

Real sample output

This is an observed result from a live run against the Chicago Public Schools public agenda PDF, not synthetic demo data. The Actor found a renewal decision for information-technology and security-system services:

{
  "district": "Chicago Public Schools",
  "state": "IL",
  "signalType": "contract_renewal",
  "category": "technology",
  "project": "INFORMATION TECHNOLOGY AND SECURITY SYSTEMS",
  "vendor": "Sentinel Technologies, Inc",
  "amountUsd": 5137439,
  "procurementStage": "renewal",
  "department": "Information Technology",
  "summary": "AUTHORIZE THE FIRST AND SECOND (FINAL) RENEWAL AGREEMENT WITH SENTINEL",
  "sourceUrl": "https://www.cpsboe.org/content/documents/april_8__2026_arc_public_agenda_to_post.pdf",
  "evidence": [
    {
      "page": 60,
      "text": "Authorize the first and second (final) renewal agreement with Sentinel Technologies, Inc. to provide information technology and security systems management, monitoring and maintenance services"
    }
  ],
  "confidence": 0.99
}

The complete item also includes document links, timestamps, contract dates when present, and all extracted evidence passages. Vendor or amount fields remain null when the source does not state them.

Local development

npm install
npm test
npm run check
apify validate-schema .actor/input_schema.json
apify run

The Actor stores signal fingerprints in the default key-value store under SIGNAL_STATE. On recurring runs, unchanged signals are suppressed by default. Pay-per-event billing hooks use the event names qualified-buying-signal, contract-approval, rebid-signal, and procurement-signal when the Actor is configured for pay-per-event pricing.

Deployment

After authenticating the Apify CLI and choosing an Actor name or ID:

apify login
apify push <username>/<actor-name> --wait-for-finish 120

The next portfolio products should reuse this engine with separate Store metadata and adapter/configuration layers: US SLED renewals, UK council procurement signals, EU TED eligibility/amendments, and EU grant/consortium intelligence.