# FIPS 201 Approved Products List Scraper (`tehsnarf/idmanagement-fips201-approved-products`) Actor

Scrapes and normalizes the federal FIPS 201 Approved Products List (idmanagement.gov) into one flat dataset covering approved, awaiting-approval, legacy, and removed PACS/PIV products.

- **URL**: https://apify.com/tehsnarf/idmanagement-fips201-approved-products.md
- **Developed by:** [Chris Hoover](https://apify.com/tehsnarf) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## FIPS 201 Approved Products List Scraper

Scrapes and normalizes the U.S. federal FIPS 201 Approved Products List
(idmanagement.gov) — the official registry of Physical Access Control System
(PACS) infrastructure, PIV smart cards, and validation systems approved for
government procurement — into one flat, consistently-typed dataset. Covers
approved, awaiting-approval, legacy, and removed products across all 9
sections of the page in a single run.

The source page mixes 9 differently-shaped HTML tables (different column
sets per section: PACS pairs, combined-infrastructure rows, PIV card rows,
removed-product rows with removal reason). This Actor reconciles all of them
into one schema so you don't have to hand-merge sections yourself.

### Use cases

1. **Federal procurement/compliance due diligence** — verify a PACS or PIV
   product is currently on the Approved Products List before purchase or
   contract award.
2. **Vendor risk monitoring** — track when a product moves to the Removed
   Product List and why (`removalReason`), to flag deployed products that
   have lost approval.
3. **Integrator/reseller catalog building** — pull the full current APL
   (PACS infrastructure + matching validation systems + APL numbers) to
   populate an internal compliant-products catalog.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `startUrls` | array | `[{"url": "https://www.idmanagement.gov/fips201/"}]` | Page(s) to scrape — the whole APL lives on one page |
| `maxItems` | integer | 500 | Max product rows to scrape (the full list is ~60 rows) |
| `delaySeconds` | number | 1.0 | Polite delay before each fetch |
| `concurrency` | integer | 5 | Fetch concurrency (only relevant if multiple `startUrls` are supplied) |

### Output fields

| Field | Description |
|---|---|
| `section` | Source page section heading |
| `category` | `PACS` / `PIV Card` / `PIV Card/Reader` |
| `topology` | `13.01` / `13.02` / `Cloud 13.01` / `Cloud 13.02` / `N/A` |
| `approvalStatus` | `Approved` / `Awaiting Approval` / `Legacy` / `Removed` |
| `productName` | PACS infrastructure, PIV card, or solution name |
| `productAplNumber` | APL # for the product/infrastructure row |
| `validationSystem` | Validation system name (PACS rows, nullable) |
| `validationAplNumber` | Validation system APL # (nullable) |
| `supplier` | Supplier (removed PIV/reader rows only, nullable) |
| `productNumber` | Product number (removed PIV/reader rows only, nullable) |
| `validDate` | Valid date (PIV card rows, nullable) |
| `removalDate` | Removal date (removed rows only, nullable) |
| `removalReason` | Removal reason (removed rows only, nullable) |
| `productPdfUrl` | Absolute URL to the product's linked PDF (nullable) |
| `validationPdfUrl` | Absolute URL to the validation system's linked PDF (nullable) |
| `updateType` | New/Update flag (awaiting-approval rows only, nullable) |
| `testingStatus` | Testing status (awaiting-approval rows only, nullable) |
| `sourceAnchor` | Direct link to the source section on idmanagement.gov |

### Example output

```json
{
  "section": "Approved 13.01 Topology PACS Products",
  "category": "PACS",
  "topology": "13.01",
  "approvalStatus": "Approved",
  "productName": "AMAG Symmetry Professional v9.8",
  "productAplNumber": "10047",
  "validationSystem": "HID Global Validation System for AMAG Symmetry Professional v9.8",
  "validationAplNumber": "10048",
  "supplier": "",
  "productNumber": "",
  "validDate": "",
  "removalDate": "",
  "removalReason": "",
  "productPdfUrl": "https://www.idmanagement.gov/docs/apl-10047-symmetry.pdf",
  "validationPdfUrl": "https://www.idmanagement.gov/docs/apl-10048-amag.pdf",
  "updateType": "",
  "testingStatus": "",
  "sourceAnchor": "https://www.idmanagement.gov/fips201/#approved-1301-topology-pacs-products"
}
```

### Pricing

$4 per 1,000 results (Pay-Per-Event). Example costs:

| Results | Cost |
|---|---|
| 100 | $0.40 |
| 500 | $2.00 |
| 1,000 | $4.00 |
| 5,000 | $20.00 |

The full current APL is ~60 rows, so a single full run costs under $0.25 —
pricing is set for recurring/scheduled monitoring use cases (tracking
removals and new approvals over time), not one-off bulk volume.

### Notes

Public `.gov` data, no login required. This Actor does not imply any GSA
endorsement — it independently republishes publicly available approval-list
data for procurement/compliance research purposes.

# Actor input Schema

## `startUrls` (type: `array`):

Page(s) to scrape. Defaults to the FIPS 201 Approved Products List itself — the whole APL lives on this one page.

## `maxItems` (type: `integer`):

Maximum number of product rows to scrape

## `delaySeconds` (type: `number`):

Polite delay each fetch waits before requesting

## `concurrency` (type: `integer`):

How many start URLs to fetch at once (each still waits delaySeconds before requesting)

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.idmanagement.gov/fips201/"
    }
  ],
  "maxItems": 500,
  "delaySeconds": 1,
  "concurrency": 5
}
```

# 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("tehsnarf/idmanagement-fips201-approved-products").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("tehsnarf/idmanagement-fips201-approved-products").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 tehsnarf/idmanagement-fips201-approved-products --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tehsnarf/idmanagement-fips201-approved-products"
        }
    }
}

```

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/o64LX2dnZeROvXwc1/builds/J8z3xcPfPgSOT0Oo2/openapi.json