Auto Repair Acquisition Scorer avatar

Auto Repair Acquisition Scorer

Pricing

from $20.00 / 1,000 scored shops

Go to Apify Store
Auto Repair Acquisition Scorer

Auto Repair Acquisition Scorer

Rank independent repair shops for acquisition research using transparent component scores and red flags.

Pricing

from $20.00 / 1,000 scored shops

Rating

0.0

(0)

Developer

Ryan Carter

Ryan Carter

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

Screen supplied repair-shop facts with transparent heuristic scores.

This is a research prioritization score, not a valuation, verified business quality assessment, or evidence an owner wants to sell. Missing facts lower data completeness.

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.

{
"shops": [
{
"shopId": "demo-1",
"shopName": "Example European Auto",
"website": "https://example.com",
"independent": true,
"locations": 2,
"yearsInBusiness": 22,
"rating": 4.7,
"reviewCount": 240,
"specialties": [
"BMW",
"Mercedes-Benz"
],
"technologies": [
"Mitchell 1",
"Podium"
],
"capabilities": {
"onlineBooking": true,
"financing": false
},
"activeJobSignals": 2,
"capacityPressureScore": 52,
"cxRiskScore": 28,
"marketCompetitorCount": 12,
"ownershipSignals": [
"Founder-led business"
]
}
],
"minimumScore": 0,
"includeLowConfidence": true
}

Input and output

Malformed scored fields receive a free INVALID_SCORE_INPUT diagnostic while valid shops continue. Numeric counts must be nonnegative; ratings must be 1–5; risk and capacity scores must be 0–100; years in business must be 0–200. Lists and capability flags must use their documented types. confidenceBasis: input_completeness describes supplied data coverage, not the probability of a successful acquisition or a verified valuation.

The Input tab documents every supported option and default. Supply shops or a compatible 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.02 per scored shop. One supplied shop profile scored with the documented screening heuristics. This is not a valuation or a determination that a business is for sale.
  • 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.

The Actor does not schedule itself. Create an Apify task and schedule after checking the initial output.

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~auto-repair-acquisition-scorer/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/auto-repair-acquisition-scorer').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

This is a research prioritization score, not a valuation, verified business quality assessment, or evidence an owner wants to sell. Missing facts lower data completeness.

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.