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

- **URL**: https://apify.com/rustic_soybean/money-engine-1.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 $10.00 / 1,000 results

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

## PACA Produce Counterparty Check

Search the public USDA Agricultural Marketing Service (AMS) PACA database for produce-trade counterparties. The Actor returns business license status, matching business/branch/trade-name records, and optional complaint totals and license dates from the public business profile.

### What it is useful for

- Screening a prospective produce buyer, seller, broker, or distributor before a transaction.
- Checking whether the city, state, and ZIP supplied for a counterparty match USDA's business listing.
- Flagging an identity detail for human verification when a contact claims to represent a company with a different public PACA location.
- Looking up a PACA license number or checking license status.
- Finding public formal and informal reparation complaint counts associated with a matched business.
- Comparing buyer-supplied license, email, phone, city, state, and ZIP details with the public business record; output contains the match status only.
- Returning compact JSON that an AI agent can explain, compare, or pass into a buyer's own workflow.

### Input

Supply 1–10 queries. Each query requires a `category`: `business`, `license`, `city`, `state`, or `zip`. Text categories also require `searchText`; state searches take a two-letter code. Set `match` to `contains` or `begins` for text searches. ZIP searches require `zipMin` and `zipMax` as five-digit strings. `maxMatchesPerQuery` is capped at 50. When `includeBusinessProfiles` is true, the Actor performs up to 10 business-profile lookups per query for complaint totals and license dates. Optionally include a `claimedCounterparty` object on a query. Its supplied `licenseNumber`, `email`, `phone`, `city`, `state`, and `zip` are compared with the matched USDA record. This enables an agent to flag identity details for human follow-up without echoing either the supplied or listed email/phone in the dataset.

Example:

```json
{
  "queries": [
    {
      "searchText": "Example Produce LLC",
      "category": "business",
      "match": "contains",
      "claimedCounterparty": {
        "licenseNumber": "12345678",
        "email": "ap@example.com",
        "phone": "555-0100",
        "city": "Fresno",
        "state": "CA",
        "zip": "93721"
      }
    },
    { "searchText": "12345678", "category": "license" }
  ],
  "maxMatchesPerQuery": 10,
  "includeBusinessProfiles": true
}
```

### Output

One dataset item is emitted per query. `businessMatches` includes business name, license number/status, city/state/ZIP, active reparation complaint indicator, and total formal claim amount. When available, the nested `profile` includes license dates and formal/informal complaint counts plus disputed counts. If `claimedCounterparty` was supplied, `identityChecks` gives `match`, `mismatch`, `not_provided`, `not_listed`, `not_checked`, or `source_unavailable` for each relevant field. An exact match is only a match to the source record, not proof that the person contacting the user represents that business. `branchMatches` and `tradeNameMatches` keep related PACA records separate so agents do not mistake them for additional business entities.

Personal contact data, principal names, source system IDs, emails, phone numbers, and street addresses are deliberately excluded from output. Claimed counterparty details are submitted as Actor input; Apify run-input retention and access are governed by the user's Apify settings. Do not send information you are not authorized to process.

### Market fit and commercial limits

This is an agent-friendly workflow over USDA's free public records, not a replacement for paid produce-trade credit services. Blue Book Services, for example, offers proprietary credit ratings, payment trends, and trade references that this Actor cannot provide. PACA complaint history is not a substitute for those signals. The potential advantage is inexpensive, repeatable checking of official license and complaint facts inside a buyer's existing automation. That advantage still needs customer validation before pricing or revenue can be claimed.

No Store price or margin is claimed from local tests. Set pricing only after a production Apify run confirms compute usage and after comparing the Store's current fee schedule with the value delivered. The public PACA search is free to use directly, so customers would be paying for workflow automation and structured output rather than exclusive data.

### Source and limits

Source: [USDA AMS PACA public search](https://apps.mrp.usda.gov/public_search). USDA's search guide says no login is required and explains that the public records show license status and complaint information. AMS says information presented on its website is public and may be copied, but its privacy statement does not document this portal's machine interface or guarantee automated access. The Actor uses the same logged-out public workflow and makes a small number of sequential requests per query. It does not use credentials, defeat challenges, or bypass access controls. If the source blocks automated access or changes its workflow, stop use until the integration is revalidated.

This is a screening aid, not a credit score, debt verification, identity-resolution service, or legal conclusion. USDA warns produce sellers about imposters falsely claiming to be licensed buyers and recommends cross-checking buyer details against the PACA search tool. Text search can return similarly named companies; a mismatch may reflect a branch, stale information, formatting differences, or an unrelated company and does not prove fraud. A match only confirms the submitted value matches a public field; it does not authenticate the caller or delivery. A complaint count or claim amount is not proof of a current unpaid invoice. Confirm identity and material findings through an independently obtained company contact before making a credit or contracting decision. Data availability and source behavior are controlled by USDA.

### Test and run

`npm test` runs deterministic tests, including checks that personal contact fields are not emitted and that supplied details produce status-only comparisons. `npm run smoke` performs a live, read-only search for a known public PACA business name and verifies listed license/location details against the source.

# Actor input Schema

## `queries` (type: `array`):

Search USDA PACA public records by business/trade name, license number, city, state, or ZIP code.

## `maxMatchesPerQuery` (type: `integer`):

Limits output volume. The USDA source may return only a partial list for broad searches.

## `includeBusinessProfiles` (type: `boolean`):

Adds one profile lookup per returned business match, up to 10 profiles per query. Contact details and principal names are never emitted.

## Actor input object example

```json
{
  "queries": [
    {
      "searchText": "Dole",
      "category": "business",
      "match": "contains"
    }
  ],
  "maxMatchesPerQuery": 10,
  "includeBusinessProfiles": true
}
```

# Actor output Schema

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

Dataset items containing USDA business license matches, optional complaint totals, related branch/trade names, and location verification checks.

# 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-1").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-1").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-1 --silent --output-dataset

```

## MCP server setup

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

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/QKX3yRFeN52v7hxDG/builds/F8ileZAhgbir4qi7q/openapi.json