⚖️ SAM.gov Federal Contractor Exclusions & Debarment Tracker

FAR §9.4 makes federal contractor screening non-optional — this actor wraps the canonical data source. Every active exclusion, debarment, and suspension on SAM.gov, refreshed daily, normalized into a queryable schema with optional fuzzy-screening for vendor master cross-checks.

Federal Acquisition Regulation Subpart 9.4 ("Debarment, Suspension, and Ineligibility") requires contracting officers to review the System for Award Management exclusions list before every award — including subcontracts above the simplified acquisition threshold. The same rule cascades into prime contractors' subcontractor screening, M&A counterparty checks at federal contractor portfolios, and grantee monitoring at every federal grant-making agency. Buyers don't get to opt out. This actor is the cheapest, cleanest path to that compliance signal at machine scale.

This actor reads the official daily-refresh public extract published by GSA at sam.gov/data-services/Exclusions/Public V2. No third-party rewrite, no aggregator overlay. Every record links back to its sam_number and the original bulk file the row was parsed from.

---

What you get

• Full active exclusion list — every excluded individual, firm, and special-entity-designation record currently in force across all federal exclusion programs (Reciprocal, Procurement, Non-Procurement, etc.).
• Daily refresh — SAM.gov regenerates the public extract every business morning; new exclusions surface within 24 hours of agency entry.
• No authentication required (bulk mode) — the actor downloads the public ZIP directly from SAM.gov's GSA-managed CloudFront distribution. Optional API mode (mode=api) uses the live SAM.gov v3 Exclusions API for finer-grained filtering when you have a free SAM_API_KEY.
• Fuzzy vendor screening — pass a list of vendor / counterparty names; the actor returns the best-matching active exclusion record per name with a similarity score. Designed to drop straight into a procurement intake or KYC workflow.
• Normalized schema — name, dba_name, classification_type, full address breakdown, exclusion_program, exclusion_type, agency, active_date, termination_date, sam_number, cage, npi, duns, uei, cross_reference, plus a stable source_url for audit.

---

Use cases

• Federal contracting compliance (FAR §9.4) — pre-award screening at primes, subs, and resellers. The buyer has a regulatory mandate; the actor is the lowest-cost path to satisfying it at scale.
• M&A due diligence on contractor portfolios — screen every vendor on a target company's master vendor file (or every counterparty in a private-equity contractor portfolio) against the active exclusion list as part of pre-close diligence.
• KYC / sanctions-adjacent screening — augment OFAC, UN, EU Consolidated, and FCA screening with the SAM federal exclusions list for any client touching US government contracting or federal grants.
• Federal grant compliance — federal grantees must screen subrecipients under 2 CFR §200.214; same data, same workflow.
• Plaintiff law / investigative journalism — track new debarments by agency, by month, by exclusion program. Maps directly onto procurement-fraud and qui tam research workflows.

---

💰 Pricing Example

Multi-event Pay-Per-Event billing:

Event	Price	When charged
Actor start	$0.005	Once per run
Exclusion record	$0.10	Per debarment / suspension record extracted (primary)
Screening match	$0.05	Per vendor name screened against the exclusion list (fuzzy-match enabled)

Typical query costs:

• Daily-monitoring run (500 records, default) — 500 × $0.10 = $50.005
• Full-list audit pull (2,000 records) — 2,000 × $0.10 = $200.005
• Vendor screening sweep (100 vendor names against the active list) — 100 × $0.05 + $0.005 = $5.005 (records emitted only for matches above threshold)
• Smoke test (max_records: 10) — 10 × $0.10 = $1.005

Apify gives every new account a $5 free credit. That covers about 50 exclusion records or 100 vendor screenings out of the box — enough to validate the actor against your own vendor master before you pay a dime. Compare with BGov vendor monitoring at ~$1,500/seat/yr or commercial KYC vendors at $0.50-$2.00 per screening event.

---

🔗 Related Actors

NexGenData publishes a deep regulatory-enforcement and sanctions cluster — every major US federal regulator, every major international financial regulator, every sanctions list. Composable in any compliance workflow:

Actor	What it does
SEC Litigation Releases	Daily SEC civil enforcement press releases — settlements, charges, monetary relief
FTC Enforcement Actions	FTC consumer protection, antitrust, merger cases with respondents and order details
EPA ECHO Enforcement	EPA enforcement actions — environmental compliance violations and penalties
Australia ASIC Enforcement	ASIC enforcement actions, banning orders, civil penalties on the AU market
Hong Kong SFC Enforcement	Hong Kong Securities & Futures Commission disciplinary actions
Singapore MAS Enforcement	MAS enforcement actions on the Singapore market
India SEBI Filings	SEBI orders, prohibitive orders, settlement orders on the India market
Japan EDINET Insider Filings	EDINET-mandated material disclosures from Japanese listed entities
Delaware Corporations Search	Delaware DOC entity lookups — useful for resolving DBA / parent on flagged matches
US Government Contracts Search	Federal procurement awards from USA Spending — pair with exclusion screening for counterparty risk
SEC EDGAR Search	SEC EDGAR full-text search across all filings
SEC Schedule 13D/G Activist Tracker	5%+ activist filings and amendments
Regulatory Filings MCP	One-tool-call MCP server over the NexGenData regulatory cluster
Legal MCP Server	Legal-research MCP for AI agents — cross-jurisdiction filings + enforcement

Browse the full fleet: apify.com/nexgendata?fpr=2ayu9b

---

How to use

Default — daily monitoring of new exclusions

{
  "mode": "bulk",
  "since_date": "2026-05-01",
  "max_records": 500
}

This pulls every exclusion added or activated on or after 2026-05-01, capped at 500 records. Run this on a daily Apify schedule and you have a continuous federal-debarment feed.

Vendor master screening (fuzzy match)

{
  "mode": "bulk",
  "max_records": 1,
  "screening_names": [
    "Acme Defense Solutions LLC",
    "John Q Contractor",
    "Apex Federal Services Inc"
  ]
}

Each name in screening_names is fuzzy-matched against the entire active exclusion list. Per name, the actor emits a record with screening_query_name, match_score, matched (boolean, score ≥ 0.85), and the full attribution of the best matching exclusion record. Bills one screening-match event per name screened ($0.05 each).

Geographic + name slice

{
  "mode": "bulk",
  "state_filter": "CA",
  "name_filter": "Construction",
  "since_date": "2025-01-01",
  "max_records": 200
}

Filters to California-addressed exclusion records whose name contains "Construction", activated since 2025-01-01.

Live API mode (requires SAM_API_KEY)

{
  "mode": "api",
  "sam_api_key": "<your free SAM.gov API key>",
  "state_filter": "TX",
  "since_date": "2026-01-01",
  "max_records": 100
}

API mode pages the live SAM.gov v3 Exclusions API server-side. Required for date / state / name filters when you want server-side filtering rather than client-side filtering on the bulk extract. Free SAM.gov public-key tier: 1,000 calls/day.

Sample output

{
  "name": "Acme Defense Solutions LLC",
  "dba_name": "",
  "classification_type": "Firm",
  "address": "1234 Federal Way, Suite 200",
  "city": "Arlington",
  "state": "VA",
  "country": "USA",
  "zip_code": "22202",
  "exclusion_program": "Procurement",
  "agency": "Department of Defense",
  "ct_code": "TBD",
  "exclusion_type": "Ineligible (Proceedings Pending)",
  "additional_comments": "All Exclusions Must be Verified by Agency POC",
  "active_date": "2026-03-15",
  "termination_date": "2029-03-14",
  "record_status": "Active",
  "cross_reference": "",
  "sam_number": "S4MS0AB-12345",
  "cage": "1ABC2",
  "npi": "",
  "duns": "",
  "uei": "ABC123DEF456GHI789J0",
  "creation_date": "2026-03-15",
  "open_data_flag": "Y",
  "source": "sam.gov/bulk-public-v2",
  "source_url": "https://sam.gov/data-services/Exclusions/Public%20V2",
  "scraped_at": "2026-05-30T19:42:18Z",
  "bulk_file_name": "SAM_Exclusions_Public_Extract_V2_26150.ZIP"
}

Screening event sample:

{
  "screening_query_name": "Acme Defense Solutions LLC",
  "match_score": 0.937,
  "matched": true,
  "best_match_name": "Acme Defense Solutions, LLC",
  "best_match_classification": "Firm",
  "best_match_uei": "ABC123DEF456GHI789J0",
  "best_match_sam_number": "S4MS0AB-12345",
  "best_match_state": "VA",
  "best_match_exclusion_program": "Procurement",
  "best_match_agency": "Department of Defense",
  "best_match_active_date": "2026-03-15",
  "best_match_termination_date": "2029-03-14",
  "source": "screening",
  "scraped_at": "2026-05-30T19:42:19Z"
}

---

FAQ

Q: Where does the data come from? A: Primary source is the GSA-managed SAM.gov public extract at https://sam.gov/data-services/Exclusions/Public%20V2. The bulk ZIP / CSV is generated by the federal government daily. Optional API mode hits https://api.sam.gov/exclusions/v3/ with your registered key.

Q: Is this scraping? A: No — both modes use the government-published, machine-readable data products. The bulk extract is explicitly designed for programmatic ingestion; the v3 API is documented at open.gsa.gov/api/exclusions.

Q: How do I get a SAM API key? A: Register a free public account at sam.gov and request a public-tier API key — 1,000 calls/day at zero cost. Required only for mode=api. Bulk mode (default) needs no authentication.

Q: How current is the data? A: Bulk mode pulls the most recent daily extract — typically the previous business day's file. New exclusions entered today by an agency surface in tomorrow's extract. API mode is real-time within the agency-entry latency.

Q: What's the difference between the Reciprocal, Procurement, and Non-Procurement programs? A: Procurement = barred from federal contracts. Non-Procurement = barred from federal financial assistance (grants, loans). Reciprocal = barred from both. The exclusion_program field exposes which one applies; in practice most active exclusions are Reciprocal.

Q: Why is duns empty? A: The DUNS identifier was retired by GSA on 2022-04-04 and replaced with the Unique Entity Identifier (UEI). The bulk V2 extract no longer carries DUNS; the field is kept for downstream schema parity but is always blank in bulk mode. UEI is populated.

Q: Why does the actor bill per-record and per-screening? A: Two distinct buyer workflows. Per-record fits compliance-monitoring (audit, journalism, M&A diligence). Per-screening fits intake/KYC (one event per name screened, regardless of whether it matched). The multi-event model lets the actor serve both at the right price point each.

---

About NexGenData

NexGenData publishes 250+ premium financial, governance, regulatory, and market actors on Apify — primary-source data from every major US and international regulator, exchange, and disclosure portal. Consistent pay-per-event pricing, full audit trails, fleet-wide quality. Browse the full fleet: apify.com/nexgendata?fpr=2ayu9b

Contact: hello@thenextgennexus.com

---

The SAM.gov exclusion list is a public US-government dataset published under federal open-data policy. FAR Subpart 9.4 and 2 CFR §200.214 mandate review of the list before federal contract awards and before federal-grant subrecipient agreements. This actor reproduces the public record at machine scale — no part of the data is rewritten, inferred, or third-party-aggregated.