Powersports and E-Mobility Safety Monitor

Match public agency events against supplied brands, models, categories, and keywords.

Uses CPSC and Federal Register sources, with optional NHTSA vehicle lookups. Source outages fail the run. A match requires review; an empty result is not a safety clearance.

Quick start

Paste this input into the Actor, or save it as input.json for the API example. Inline records with example.com URLs are fictional demonstration data. Form prefill values are examples, not defaults for empty API requests.

{
  "offline": true,
  "brands": [
    "Sur-Ron",
    "Talaria",
    "Segway"
  ],
  "productCategories": [
    "electric-dirt-bike",
    "battery"
  ],
  "keywords": [
    "thermal runaway",
    "fire hazard"
  ],
  "onlyNewEvents": false,
  "minimumMatchConfidence": 0.5,
  "stateStoreName": "safety-event-state-offline",
  "events": [
    {
      "eventId": "CPSC:demo-24-001",
      "eventType": "recall",
      "sourceAgency": "CPSC",
      "publishedAt": "2026-07-20T00:00:00Z",
      "title": "Example Brand recalls electric dirt bikes due to fire hazard",
      "summary": "The lithium-ion battery pack can overheat and enter thermal runaway, posing fire and burn injury hazards. Sold at specialty powersports dealers.",
      "hazard": "Fire and burn hazard",
      "remedy": "Stop use and contact the manufacturer for a free replacement battery",
      "statedBrands": [
        "Sur Ron",
        "Example Brand LLC"
      ],
      "statedModels": [
        "Sur Ron Light Bee X",
        "Model A"
      ],
      "sourceUrl": "https://www.cpsc.gov/Recalls/example",
      "effectiveDate": null,
      "commentDeadline": null,
      "raw": {}
    },
    {
      "eventId": "FR:demo-2026-14000",
      "eventType": "rule",
      "sourceAgency": "FederalRegister",
      "publishedAt": "2026-07-22T00:00:00Z",
      "title": "Safety Standard for Micromobility Products With Lithium-Ion Batteries",
      "summary": "The Commission proposes a mandatory safety standard addressing thermal runaway in lithium-ion battery systems used in micromobility products.",
      "hazard": null,
      "remedy": null,
      "statedBrands": [],
      "statedModels": [],
      "sourceUrl": "https://www.federalregister.gov/documents/example",
      "effectiveDate": null,
      "commentDeadline": "2026-09-15",
      "raw": {}
    },
    {
      "eventId": "CPSC:demo-24-002",
      "eventType": "recall",
      "sourceAgency": "CPSC",
      "publishedAt": "2026-07-18T00:00:00Z",
      "title": "Unrelated brand recalls kitchen blenders due to laceration hazard",
      "summary": "The blade assembly can detach during use.",
      "hazard": "Laceration hazard",
      "remedy": "Contact the manufacturer for a replacement",
      "statedBrands": [
        "Unrelated Kitchen Co"
      ],
      "statedModels": [
        "KB-100"
      ],
      "sourceUrl": "https://www.cpsc.gov/Recalls/example-2",
      "effectiveDate": null,
      "commentDeadline": null,
      "raw": {}
    }
  ]
}

Input and output

For NHTSA, sourceCoverage lists successfully queried vehicles, vehicles skipped by the source document cap, and whether results were truncated. A skipped vehicle receives a free vehicle_not_checked diagnostic with SOURCE_EVENT_LIMIT; an unsupported lookup uses VEHICLE_NOT_IN_SOURCE_CATALOG. Neither means recall-free. Increase the limit or split the vehicle list, and verify the exact year/make/model against NHTSA's catalog. Model-level matches do not establish whether a particular VIN is affected or whether its repair has been completed.

Brand matching accepts spacing and hyphenation variants such as Sur-Ron, Sur Ron, and SurRon, but requires the complete name rather than a substring of another brand. Severity rules recognize both singular and plural serious-injury wording. Matches still require review against the linked agency record.

Non-recall notices also need safety or equipment-standard context. A motorcycle mention in an administrative mileage-reimbursement notice does not produce a matched-event charge. Equipment notices such as motorcycle helmet labeling remain eligible.

The Input tab documents every supported option and default. For an offline demonstration, supply events and set offline: true. For live collection, set offline: false and supply matching criteria such as brands, keywords, or vehicles. This Actor does not accept sourceDatasetId. A run supports at most 10,000 supplied records. Split larger inputs into separate runs.

Returns shared signal envelopes: entityId, entityType, signalType, severity, confidence, observedAt, sourceUrl, evidence, and Actor-specific payload. Compatible envelopes are unwrapped on input; payload fields must still match this Actor’s expected input. A common envelope does not join or enrich separate observations automatically.

Confidence is a heuristic evidence/completeness indicator, not a calibrated probability. Inspect evidence and missing inputs before acting. Dataset exports support JSON and CSV; nested fields are available through the dataset API.

Pricing and spending limits

Pay per event, with platform usage included. The Apify Store pricing panel shows the current prices.

• $0.10 per matched safety event. One new source-backed safety event matched above the requested confidence threshold and delivered. No-results and vehicle-not-checked diagnostics are excluded.
• Startup: $0.005 per GB of allocated memory, with a minimum of one startup event. The default memory allocation is 1 GB or less.

Diagnostics and included extra signals have no output-event charge; the startup charge still applies. Set the maximum run cost to control spending. If the remaining budget cannot cover the next event, the Actor stops and returns the results already completed. Check the run summary before assuming the entire input was processed. Fees from a separate upstream scraper are not included.

Errors and repeat runs

Malformed or empty required input fails with an actionable error. Unsupported or insufficient records can produce free diagnostic signals or rejection counts in OUTPUT. Check the run status, summary, diagnostics, and billing record together; zero results does not establish that no opportunities or problems exist.

Use the same stateStoreName for sequential observations of the same population. Use a different name for independent workflows. Do not overlap runs sharing a state store. Only delivered listing/lot results advance their reporting snapshot; a budget cutoff defers remaining work. Repeated or interrupted runs can still produce duplicate outputs because dataset writes, charging and state updates are separate operations; deduplicate downstream by entity, signal type and observation time.

Run it from the API

Start asynchronously to avoid request timeouts on larger inputs. Use the returned run ID to wait for completion, then download its dataset.

curl --request POST 'https://api.apify.com/v2/acts/repairiq~powersports-safety-monitor/runs' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data-binary @input.json

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = JSON.parse(await (await import('node:fs/promises')).readFile('input.json', 'utf8'));
const run = await client.actor('repairiq/powersports-safety-monitor').call(input);
if (run.status !== 'SUCCEEDED') throw new Error('Run failed; inspect its log before using partial results.');
const dataset = client.dataset(run.defaultDatasetId);
for (let offset = 0; ; ) {
    const { items } = await dataset.listItems({ offset, limit: 1000 });
    for (const item of items) console.log(item);
    if (items.length < 1000) break;
    offset += items.length;
}

Limitations and support

Uses CPSC and Federal Register sources, with optional NHTSA vehicle lookups. Source outages fail the run. A match requires review; an empty result is not a safety clearance.

Use data you have permission to process, and respect source restrictions. No affiliation with the named software vendors, marketplaces, or agencies is implied. Report reproducible problems through the Actor Issues tab with a run ID and a minimal input; omit credentials and private customer data.

Local development

Requires Node.js 22 or newer. Run npm ci, npm run build, and npm test from this Actor directory. Put local input in storage/key_value_stores/default/INPUT.json, then run npm start. The repository root’s npm run verify also checks schemas, shared copies and real entry-point smoke scenarios.