# Screen a supplier list for exclusions

To screen a supplier list for exclusions with an AI agent, give it the UEIs or CAGE codes and ask it to call exclusion_check for each. Every answer says whether an active exclusion matches, with the matching records and the date of the exclusions extract, which you can keep as your screening record.

Compliance and procurement teams at primes, grantees and universities. Federal rules bar contractors from subcontracting with excluded parties above a threshold (FAR 52.209-6) and require grantees to check before lower-tier awards; screening a whole list at once is faster than the SAM.gov search page.

## The prompt

```
Screen these 30 suppliers against the SAM.gov exclusions list by UEI. Return a table of supplier, UEI, excluded yes or no, and any matching record, and tell me the date of the exclusions data you used.
```

## What the agent calls

1. exclusion_check: One check per identifier against the active exclusions in the daily extract.

```json
{"name":"exclusion_check","arguments":{"q":"ABCDEFGH1234","user_request":"supplier exclusion screening"}}
```

## Sample output

Trimmed; field names and structure match the live response, values are shortened or illustrative.

```json
{
  "data": {
    "query": "ABCDEFGH1234",
    "excluded": false,
    "matches": [],
    "answer": "No active exclusion matches ABCDEFGH1234 in the exclusions extract dated 2026-11-12."
  },
  "meta": {
    "as_of": "2026-11-12"
  }
}
```

## How to read the answer

- excluded is true only for active exclusions. Terminated ones are history and do not bar an award.
- The answer sentence carries the extract date. Keep it with the supplier file: it is the evidence of when you screened.

## Make it yours

- Screen by exact legal name for parties without a UEI, then review any match by hand.
- Re-screen monthly or before each new subcontract action.

## Pitfalls

- Name matching can produce false positives and misses. Prefer UEI or CAGE; treat a name match as a lead to review, not a finding.
- Exclusions of individuals are in the source data but never get pages here; the API answers checks without publishing them.

## The same job over REST

```bash
curl "https://samgovapi.io/api/v1/exclusions/check?q=ABCDEFGH1234" -H "Authorization: Bearer $SAMGOVAPI_API_KEY"
```

Plan: every plan. Credits: 1 credit per lookup; one per supplier.

## Questions

### How fresh is the exclusions data?

The exclusions extract is loaded daily and every answer states its date. For an award decision on the day, confirm on sam.gov.

### What is the difference from the exclusion flag on a registration?

The flag is part of the registration record and changes with the registration extract; exclusion_check reads the exclusions extract directly.

All recipes: https://samgovapi.io/agents/recipes.md

Independent. Not affiliated with, endorsed by or sponsored by GSA, SAM.gov or any U.S. government agency. Registering in SAM.gov is free at sam.gov.