# Machine Shop Capability Detector (`signalserver/machine-shop-capability-detector`) Actor

- **URL**: https://apify.com/signalserver/machine-shop-capability-detector.md
- **Developed by:** [Joep van Acht](https://apify.com/signalserver) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $500.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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Machine Shop / Contract Manufacturer Capability Detector

### What you are looking at

A list of job shops gives you a name, a headcount and a zip code.

### Why it costs you

It does not say which shops run 5-axis, hold AS9100, or cut Inconel. So reps qualify on the call instead of before it, territories get planned on guesswork, and a chunk of the book is shops that were never going to buy. That data exists only as prose on a capabilities page, so no database holds it.

### What this actor does

Point this actor at a list of shop websites. It crawls each shop's own capability, equipment and quality pages and returns machine brands, certifications (AS9100, ISO 9001, IATF 16949, ISO 13485, ITAR, NADCAP, AWS, AISC), processes from 5-axis and Swiss through welding, fabrication, foundry and finishing, materials, industries served, the advertised tolerance, and the shop-floor ERP or quoting system where one is exposed.

### Start here

Paste a handful of shop domains into `startUrls` and run it. Compare the output against shops you already know before you scale it to a territory.

### Output fields

- `vertical_relevance`
- `company`
- `website`
- `final_url`
- `top_detection`
- `vendor`
- `confidence`
- `evidence`
- `machine_brands`
- `machine_brand_count`
- `certifications`
- `processes`
- `materials`
- `industries_served`
- `tolerance_claim`
- `has_rfq_form`
- `all_detections`
- `categories`
- `pages_crawled`
- `status`

### Measured accuracy

96 to 100% on qualified shops across 8 stress rounds on fresh OpenStreetMap samples in 5 US regions. Processes fill 85-100%, materials 54-90%, certifications 23-50%. Machine brands are the sparsest field (12-23%) because many shops do not publish an equipment list.

### Deploy

```bash
APIFY_PUSH_TOKEN=$APIFY_TOKEN_PERSONAL python3 push_to_apify.py
```

SDK-free by design: plain Apify REST via run env vars. Do not reintroduce the apify/crawlee SDK without pinning every transitive dependency.

# Actor input Schema

## `startUrls` (type: `array`):

Websites to scan. Paste URLs, use Bulk edit for a list, upload a file, or link a Google Sheet.

## `maxSubpages` (type: `integer`):

How many same-site pages to crawl beyond the homepage.

## `concurrency` (type: `integer`):

Sites scanned in parallel.

## `proxyConfiguration` (type: `object`):

Optionally route through Apify Proxy (helps with IP-blocked hosts).

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://qualitycnc.com"
    },
    {
      "url": "https://fmmachine.com"
    }
  ],
  "maxSubpages": 5,
  "concurrency": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Rebuilds the capability profile of a machine shop or contract manufacturer from its website: shop-floor ERP (ProShop, JobBOSS, E2, Global Shop, Epicor, DELMIAworks), quoting stack (Paperless Parts, Xometry, Fictiv), machine brands (Haas, Mazak, Okuma, DMG MORI, Makino, Citizen), certifications (AS9100, ISO 9001, IATF 16949, ISO 13485, ITAR, NADCAP), processes, materials, industries served and tolerance claims. Built for ERP/MES vendors, tooling and materials distributors and industrial marketplaces.

# 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 = {
    "startUrls": [
        {
            "url": "https://qualitycnc.com"
        },
        {
            "url": "https://fmmachine.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("signalserver/machine-shop-capability-detector").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 = { "startUrls": [
        { "url": "https://qualitycnc.com" },
        { "url": "https://fmmachine.com" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("signalserver/machine-shop-capability-detector").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 '{
  "startUrls": [
    {
      "url": "https://qualitycnc.com"
    },
    {
      "url": "https://fmmachine.com"
    }
  ]
}' |
apify call signalserver/machine-shop-capability-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,signalserver/machine-shop-capability-detector"
        }
    }
}

```

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/WgBoPTvaM8bcmDN0P/builds/vwU1HgKirB0h7n5PO/openapi.json