# OIG Exclusion Check + OFAC Sanctions Screener (`hamsmoothie/exclusion-debarment-screener`) Actor

Screen names or NPIs against the HHS-OIG LEIE exclusion list and the OFAC SDN sanctions list in one run.

- **URL**: https://apify.com/hamsmoothie/exclusion-debarment-screener.md
- **Developed by:** [Maybe Quark](https://apify.com/hamsmoothie) (community)
- **Categories:** Other, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 one exclusion or sanctions list match (or a no-match record) for a screened name or npis

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

## OIG Exclusion Check and OFAC Sanctions Screening by Name or NPI

**Exclusion and Debarment Screener** checks names and NPIs against the HHS Office of Inspector General **LEIE** exclusion list and the US Treasury **OFAC SDN** sanctions list in a single run. Paste provider, employee, vendor or business names (or 10-digit NPIs) and get back every possible match, plus a `no_match` row for every clean query so you keep a dated screening record. Each run downloads the current official files, so there is no stale copy and no API key.

### Input

Provide `searchNames`, `npis`, or both. This example screens one vendor name and one NPI against both lists:

```json
{
  "searchNames": ["Acme Medical Supply"],
  "npis": ["1234567893"],
  "includeOfac": true,
  "emitNoMatch": true,
  "maxResultsPerQuery": 50
}
```

- `searchNames`: person or business names. A record matches when every word of your query appears in the listed name (case and punctuation ignored).
- `npis`: 10-digit NPIs checked against the LEIE list for exact matches.
- `includeOfac`: also check names against the OFAC SDN list (default true).
- `emitNoMatch`: output a `no_match` row per query and list (default true).
- `maxResultsPerQuery`: cap on matches per name or NPI per list (default 50).
- `recentLimit`: with no names or NPIs, return this many of the most recent LEIE exclusions (default 100).

### Output

One row per match or per clean query. Example `no_match` row:

```json
{
  "source": "OIG LEIE",
  "query": "Acme Medical Supply",
  "matchStatus": "no_match",
  "retrievedAt": "2026-10-14T20:00:00.000Z",
  "url": "https://exclusions.oig.hhs.gov/"
}
```

Match rows (`possible_match`, `exact_npi_match`, or `listed` in recent-exclusions mode) add these fields: `name`, `entityType`, `businessName`, `general`, `specialty`, `npi`, `city`, `state`, `zip`, `exclusionType`, `exclusionDate`, `reinstatementDate` for OIG LEIE rows, and `program`, `remarks`, `listEntryId` for OFAC SDN rows.

### Use cases

Search phrases this actor is built for:

- **"Check OIG exclusion list by name or NPI"**: screen a roster of clinicians or staff monthly and keep the `no_match` rows as dated evidence.
- **"OFAC SDN sanctions screening by name"**: check a new supplier or customer before the first payment.
- **"Screen vendors against LEIE exclusion and sanctions lists"**: one run covers both lists, and it can be called from Zapier, Make, n8n or code. It also works as a tool for AI agents through the Apify MCP server.

Typical users are healthcare compliance officers, credentialing and HR teams, and vendor-risk and KYB analysts.

### Pricing

Pay per result: each output row is one billable result, listed at $0.002 per row ($2 per 1,000). `no_match` rows count as results; set `emitNoMatch` to false to pay only for hits.

### Limits

- Matches are only possible matches. Confirm identity with an NPI or at the official source before acting; this is not legal advice.
- Only names and NPIs are matched. Dates of birth and street addresses are deliberately not used or returned.
- SAM.gov exclusions are not included.
- The LEIE file is refreshed monthly by OIG; OFAC changes whenever Treasury publishes updates.

### FAQ

**How fresh is the data?** Each run downloads the current LEIE and OFAC SDN files from the official sources.

**Why only "possible" matches?** Name matching alone is ambiguous. NPI matches are exact.

**What do I get with no input?** The most recent LEIE exclusions, up to `recentLimit`.

# Actor input Schema

## `searchNames` (type: `array`):

Person or business names. A record matches when every word of the query appears in the listed name. Leave empty (with no NPIs) to get the most recent LEIE exclusions.

## `npis` (type: `array`):

10-digit National Provider Identifiers to check against the OIG LEIE list.

## `includeOfac` (type: `boolean`):

Check names against the OFAC Specially Designated Nationals list as well as OIG LEIE.

## `emitNoMatch` (type: `boolean`):

Output a 'no_match' row per query and list so you keep a screening record.

## `maxResultsPerQuery` (type: `integer`):

Cap on matches returned per name or NPI per list.

## `recentLimit` (type: `integer`):

When no names or NPIs are given, return this many of the most recent LEIE exclusions.

## Actor input object example

```json
{
  "searchNames": [],
  "npis": [],
  "includeOfac": true,
  "emitNoMatch": true,
  "maxResultsPerQuery": 50,
  "recentLimit": 100
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("hamsmoothie/exclusion-debarment-screener").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("hamsmoothie/exclusion-debarment-screener").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 '{}' |
apify call hamsmoothie/exclusion-debarment-screener --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hamsmoothie/exclusion-debarment-screener"
        }
    }
}
```

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/WVQEZs4EG6LI2hmZH/builds/au3B0y1CFbvMH9QHf/openapi.json