# Money Engine (`rustic_soybean/money-engine`) Actor

- **URL**: https://apify.com/rustic_soybean/money-engine.md
- **Developed by:** [Chris Johnson](https://apify.com/rustic_soybean) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 product screeneds

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 Evidence Matcher

Screens product descriptions, UPCs and models against the official CPSC recall API.

Public Actor: https://apify.com/rustic_soybean/money-engine\
Actor ID: `g77MTIhevsiBYEeQa`

The Actor queries the requested recall-date range in yearly partitions, retries CPSC's intermittent embedded provider-error response, rejects records returned outside their requested year, deduplicates recalls, and reports the requested range, query count, per-window record counts, unique source/scanned counts, retrieval time, and truncation state. CPSC recall data is available from 1973 forward; the default range is 1973 through today with no record cap.

UPC evidence is accepted only from the structured CPSC `ProductUPCs` field. Digits appearing incidentally in prose are not treated as an identifier match. Results remain screening evidence, not confirmed product recall determinations.

Official source and API documentation: [CPSC Recall API](https://www.cpsc.gov/Recalls/CPSC-Recalls-Application-Program-Interface-API-Information).

### Input contract

Submit **1–200 products per run**; a single product is valid. Each row must contain a non-empty product name or description, UPC/GTIN, or model identifier. UPC/GTIN values must contain 8–14 digits (spaces and hyphens are allowed); model identifiers need at least four letters or digits. The runtime validates rows as well as the Store schema.

```json
{
  "products": [
    { "name": "Known recalled UPC verification item", "upc": "840059614922" }
  ],
  "startDate": "1973-01-01",
  "maxRecalls": 0
}
```

### Result interpretation

Each product produces one dataset row with a status, candidate matches, coverage metadata, official source reference, and a disclaimer. Candidate matches include the recall ID, recall URL, evidence type, confidence, and matched UPC/model values when a structured identifier matched. Descriptive matches are explicitly marked as descriptive only and require human verification. A no-match result means only that no candidate was found in the scanned date range. It does not establish that a product is safe or has never been recalled.

### Pricing

The current per-product and per-run prices are shown in the Apify Store Pricing tab. Apify platform usage may also apply depending on the Actor's configured pricing model; check the run cost and your account spending limit before processing a large catalog.

# Actor input Schema

## `products` (type: `array`):

Provide 1–200 products. Each row must include a non-empty name/description, UPC/GTIN, or model identifier.

## `maxRecalls` (type: `integer`):

Use 0 for the complete requested date range. Must be a non-negative whole number. A positive limit is reported as truncated and cannot produce a clean no-match result.

## `startDate` (type: `string`):

A real calendar date in YYYY-MM-DD format. CPSC recall data starts on 1973-01-01.

## `endDate` (type: `string`):

Optional real calendar date in YYYY-MM-DD format; defaults to today.

## Actor input object example

```json
{
  "products": [
    {
      "name": "Known recalled UPC verification item",
      "upc": "840059614922"
    }
  ],
  "maxRecalls": 0,
  "startDate": "1973-01-01"
}
```

# Actor output Schema

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

Dataset items containing each screened product, potential matches, evidence, and coverage metadata.

# 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("rustic_soybean/money-engine").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("rustic_soybean/money-engine").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 rustic_soybean/money-engine --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rustic_soybean/money-engine"
        }
    }
}
```

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/g77MTIhevsiBYEeQa/builds/enhTPnpIqjeWzyPkO/openapi.json