# CPSC Recall Catalog Match (`frankycheese/cpsc-recall-catalog-match`) Actor

Check catalog brands, model numbers, and product terms against official U.S. CPSC recalls. Get source-linked new matches and material corrections for ecommerce compliance and product-safety monitoring.

- **URL**: https://apify.com/frankycheese/cpsc-recall-catalog-match.md
- **Developed by:** [franklin mccheese](https://apify.com/frankycheese) (community)
- **Categories:** Automation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 new matched source events

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

## CPSC Recall Catalog Match

Check catalog brands, model numbers, and product terms against official U.S. CPSC recalls. Get source-linked new matches and material corrections for ecommerce compliance and product-safety monitoring.

- **Buyer:** retailer, marketplace, catalog, and product-safety teams
- **Result:** explainable recall candidates with the official CPSC notice, recall metadata, and replay-safe change detection
- **Official source:** CPSC SaferProducts recall API
- **First useful run:** one current `Fisher-Price` match
- **Maximum Actor charge for the prefilled run:** **$0.10**
- **Unchanged replay:** **$0** in Actor event charges

[Open the bounded Fisher-Price example](https://apify.com/frankycheese/cpsc-recall-catalog-match/examples/monitor-cpsc-product-recalls) or use the prefilled input in **Run**. Inspect the linked CPSC notice before routing a match into enforcement, removal, or customer-notification workflows.

### fastest test

The Store input is prefilled to return at most one current `Fisher-Price` match. It queries at most 100 source records and cannot create more than `$0.10` in Actor event charges.

```json
{
  "watchlistId": "fisher-price-recall-preview",
  "catalogTerms": ["Fisher-Price"],
  "baselineMode": "emit_matches",
  "maxEvents": 1,
  "maxTotalChargeUsd": 0.1,
  "maxSourceRecords": 100,
  "stateStoreName": "fisher-price-recall-preview-state",
  "resetState": false,
  "qualityTestMode": false
}
```

After checking the first result, replace `catalogTerms` with your own brands, model numbers, or product terms. For recurring monitoring, keep the same `watchlistId` and `stateStoreName`, switch `baselineMode` to `silent`, and schedule the Actor daily or weekly.

### what one match contains

A source check on November 1, 2026 matched `Fisher-Price` to this official record:

```json
{
  "eventType": "NEW_RECALL_MATCH",
  "sourceId": "10231",
  "title": "Fisher-Price Recalls Brunch & Go Stroller Toys Due to Choking Hazard",
  "publishedAt": "2025-04-10T00:00:00",
  "metadata": {
    "recallNumber": "25215",
    "products": [{"Name": "Brunch & Go Stroller Toys"}]
  },
  "sourceRecordUrl": "https://www.cpsc.gov/Recalls/2025/Fisher-Price-Recalls-Brunch-Go-Stroller-Toys-Due-to-Choking-Hazard"
}
```

Every delivered event also includes the watchlist ID, observation time, source fingerprint, source dataset, summary, and a stable event ID. A later material change to the same source record is emitted as `SOURCE_CORRECTION` rather than another new match.

### input behavior

- `catalogTerms` — up to 50 brands, models, or product phrases. Matching is case-insensitive against CPSC titles, descriptions, products, and manufacturers.
- `watchlistId` — identifies the monitoring job in output and event IDs.
- `stateStoreName` — persistent replay state. Keep it unchanged between scheduled runs to suppress duplicate events.
- `baselineMode` — `emit_matches` returns current matches; `silent` records the current source state without paid match events.
- `maxEvents` — hard limit on paid events from one run.
- `maxTotalChargeUsd` — hard limit on Actor event charges from one run.
- `maxSourceRecords` — hard limit on matching source records evaluated per run.
- `resetState` — clears replay history and can cause current matches to emit again.
- `qualityTestMode` — unbilled diagnostics only; it does not query CPSC or return business results. Leave it off for buyer runs.

### pricing

This Actor is pay per event. Apify platform usage is not charged separately for this Actor.

- new recall match — **$0.10**
- source correction — **$0.01**
- silent baseline, unchanged replay, empty result, or failed-source run — **$0** in Actor event charges

Examples:

- 1 new match: **$0.10**
- 10 new matches: **$1.00**
- 10 source corrections: **$0.10**

Use `maxEvents` and `maxTotalChargeUsd` together to fail closed before a run can exceed your budget.

### use in a workflow

1. run once with `emit_matches` to validate your terms;
2. switch to `silent` if you want a clean monitoring baseline;
3. schedule daily or weekly with the same state identifiers;
4. send new dataset rows through Apify integrations, API clients, webhooks, Sheets, Slack, email, or your compliance queue.

The Actor works through Apify Tasks, schedules, REST API, Python and JavaScript clients, and agent/MCP integrations.

### source, limitations, and support

The Actor reads the public CPSC SaferProducts recall API at run time and links every event to its official CPSC notice. Upstream records can be incomplete or corrected after publication. Text matching can produce false positives or miss products whose identifiers are absent from the source. A no-match result is not a safety clearance, and this Actor does not make legal or independent product-safety determinations.

For reproducible support, open an Apify issue with the run ID, non-secret input, expected term, and linked CPSC notice. Do not include credentials or private catalog data.

# Actor input Schema

## `watchlistId` (type: `string`):

Stable identifier for this monitoring job. Keep it unchanged between scheduled runs.

## `catalogTerms` (type: `array`):

Brands, model numbers, or product terms matched case-insensitively against CPSC titles, descriptions, products, and manufacturers.

## `baselineMode` (type: `string`):

Choose a free silent baseline or emit current matches as paid events.

## `maxEvents` (type: `integer`):

Hard cap on paid events emitted by one run.

## `maxTotalChargeUsd` (type: `number`):

Hard cap on pay-per-event charges for one run.

## `maxSourceRecords` (type: `integer`):

Hard cap on source records fetched and evaluated per run.

## `stateStoreName` (type: `string`):

Persistent replay state. Keep this name unchanged to suppress duplicate events across scheduled runs.

## `resetState` (type: `boolean`):

Discard prior replay state; may cause current matches to emit again.

## `qualityTestMode` (type: `boolean`):

Apify Store automated smoke-test mode. It validates runtime and input startup, emits one unbilled summary, and does not query sources, mutate state, deliver business events, or charge.

## Actor input object example

```json
{
  "watchlistId": "fisher-price-recall-preview",
  "catalogTerms": [
    "Fisher-Price"
  ],
  "baselineMode": "emit_matches",
  "maxEvents": 1,
  "maxTotalChargeUsd": 0.1,
  "maxSourceRecords": 100,
  "stateStoreName": "fisher-price-recall-preview-state",
  "resetState": false,
  "qualityTestMode": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `report` (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 = {
    "watchlistId": "fisher-price-recall-preview",
    "catalogTerms": [
        "Fisher-Price"
    ],
    "baselineMode": "emit_matches",
    "maxEvents": 1,
    "maxTotalChargeUsd": 0.1,
    "maxSourceRecords": 100,
    "stateStoreName": "fisher-price-recall-preview-state",
    "qualityTestMode": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("frankycheese/cpsc-recall-catalog-match").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 = {
    "watchlistId": "fisher-price-recall-preview",
    "catalogTerms": ["Fisher-Price"],
    "baselineMode": "emit_matches",
    "maxEvents": 1,
    "maxTotalChargeUsd": 0.1,
    "maxSourceRecords": 100,
    "stateStoreName": "fisher-price-recall-preview-state",
    "qualityTestMode": False,
}

# Run the Actor and wait for it to finish
run = client.actor("frankycheese/cpsc-recall-catalog-match").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 '{
  "watchlistId": "fisher-price-recall-preview",
  "catalogTerms": [
    "Fisher-Price"
  ],
  "baselineMode": "emit_matches",
  "maxEvents": 1,
  "maxTotalChargeUsd": 0.1,
  "maxSourceRecords": 100,
  "stateStoreName": "fisher-price-recall-preview-state",
  "qualityTestMode": false
}' |
apify call frankycheese/cpsc-recall-catalog-match --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,frankycheese/cpsc-recall-catalog-match"
        }
    }
}
```

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/TUMjXKXssVwcXKzCp/builds/4ZDEnNQRcnuFkYOe1/openapi.json