B2B Website Lead Scoring & Company Enrichment API — Apify Actor

Score public company websites as a low-cost company enrichment API for B2B lead scoring, CRM enrichment, ICP fit, account qualification, ABM account scoring, lead prioritization, sales prospecting, RevOps, GTM research, market mapping, account research, and website analysis. It returns one company-level row per website so growth teams can prioritize accounts before deeper manual research.

This Actor is designed for an Apify Store / Pay-Per-Event (PPE) path, not direct email outreach. It does not harvest emails, phone numbers, people, LinkedIn profiles, or login-wall data.

Fast buyer workflow

1. Paste a list of public company website URLs from a CRM export, CSV, Clay table, Apollo account export, HubSpot/Salesforce/Pipedrive/Zoho account list, ABM target-account list, or AI-agent workflow.
2. Add your ICP keywords, such as B2B, SaaS, RevOps, GTM, automation, integration, lead scoring, CRM, ABM, account research, account scoring, lead prioritization, buying signals, website analysis, HubSpot, Salesforce, Pipedrive, Zoho, Clay, Apollo, Zapier, n8n, or Make.com.
3. Export the dataset rows to JSON/CSV or read them through the Apify API/MCP server.
4. Route fit_score, crm_segment, fit_reasons, and recommended_action back into Clay, HubSpot, Salesforce, Pipedrive, Zoho, Airtable, Google Sheets, Zapier, n8n, Make.com, or an AI sales/research agent.

The output is intentionally flat, company-level JSON so it works in Apify API calls, MCP/AI-agent tools, Clay's Apify integration, CRM imports, and spreadsheet workflows without custom parsing.

Buyer use cases

Use this Actor when you need quick, low-cost account screening from public websites:

• score B2B lead lists before SDR/BDR outreach;
• qualify inbound accounts against an ICP;
• enrich CRM/company records with public positioning signals;
• compare SaaS, agency, platform, and service-provider websites;
• map a market segment for RevOps, GTM, sales ops, demand generation, or agency prospecting;
• filter out poor-fit or risky websites before paying for deeper enrichment.

Search terms this Actor is designed to satisfy: B2B lead scoring, website lead scoring, website qualification, ICP fit, account qualification, account research lead scoring, CRM account research, CRM enrichment, CRM enrichment API, company enrichment, company enrichment API, domain enrichment, domain enrichment API, public web research CRM, ABM account scoring, account-based marketing lead scoring, lead prioritization CRM, demand generation account scoring, RevOps account scoring, sales intelligence website analysis, website analysis lead generation, company scoring API, B2B website analyzer CRM, website qualification API, MCP CRM enrichment, GTM research, RevOps, Clay enrichment, Apollo account enrichment, HubSpot enrichment, Salesforce account scoring, Pipedrive CRM enrichment, Zoho CRM enrichment, Airtable lead scoring, Google Sheets lead scoring, Zapier lead scoring, n8n enrichment, Make.com workflow automation, no-code CRM lead scoring, sales pipeline scoring, MCP, AI agents, x402, agentic payments, lead generation, company scoring, account scoring, website analysis.

Copy-paste API quickstart

Use the Actor as a small company scoring API or B2B website analyzer when a workflow needs flat lead-fit rows instead of a contact database.

Apify API callers can run a sample synchronously:

curl -X POST "https://api.apify.com/v2/actors/jorokotev~public-website-lead-fit/run-sync-get-dataset-items" \
  -H "Authorization: Bearer <APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"source":"sample","maxResults":3}'

AI-agent and MCP buyers can also probe Apify's x402 payment flow without an Apify token. A valid payment client should receive payment terms first, then retry with a payment signature:

curl -i -X POST "https://api.apify.com/v2/actors/jorokotev~public-website-lead-fit/run-sync-get-dataset-items" \
  -H "X-APIFY-PAYMENT-PROTOCOL: X402" \
  -H "Content-Type: application/json" \
  -d '{"source":"sample","maxResults":1}'

For CRM and Clay workflows, map fit_score, fit_label, crm_segment, fit_reasons, recommended_action, and summary back into account fields, then use your approved contact-data provider only if the account passes your ICP gate.

Published example tasks

Use the public example tasks when you want a pre-filled buyer workflow instead of starting from a blank input form:

• Score B2B SaaS websites for ICP fit — sample SaaS account scoring for ICP fit and B2B lead qualification.
• Qualify RevOps and sales automation accounts — RevOps, sales automation, CRM, pipeline, and revenue-intelligence account screening.
• Enrich a CRM company list from public websites — company-level CRM enrichment rows from public website URLs.

What it does

Input public company website URLs, choose target ICP keywords, and get one structured lead-fit row per returned company:

• fit score and label;
• matched ICP keywords;
• trust-signal gaps;
• public page title / HTTP status / fetch status;
• risk flags;
• fit reasons, CRM segment, and recommended next action;
• concise summary;
• redacted text excerpt.

Data and privacy policy

• Public website URLs only.
• Company-level analysis only.
• Emails, phone numbers, social profile URLs, and simple person-role hints are redacted from excerpts.
• No contact harvesting or contact export.
• No LinkedIn/login-wall/profile scraping.
• URL mode fetches only user-supplied URLs; it is not an open-ended crawler.
• URL mode blocks localhost, embedded credentials, cloud metadata hosts, private/link-local/reserved IPs, and redirects to non-public addresses before fetch.
• robots.txt is respected by default.

Apify monetization posture

The intended Apify-only monetization path is PPE:

1. Keep the synthetic apify-actor-start event at the default low price.
2. Use Apify's synthetic default dataset item event (apify-default-dataset-item) for per-result charging, because every pushed result row is the value unit.
3. Keep result pricing at the current cautious first-launch setting Joro selected: $0.002/result unless manually changed later.
4. Keep strict caps: maxUrls <= 50, maxResults <= 50, per-URL timeout <= 30s, max bytes <= 300 KB.
5. Do not enable custom Actor.charge() events for this first Store launch; per-result billing should come from Apify's automatic dataset-item synthetic event to avoid double-charging or charge-without-row edge cases.

Example input — live URL mode

{
  "source": "urls",
  "startUrls": [
    {"url": "https://example.com"}
  ],
  "targetKeywords": ["B2B", "SaaS", "RevOps", "GTM", "automation", "integration", "lead scoring", "CRM", "ABM", "account research", "account scoring", "lead prioritization", "buying signals", "website analysis", "Clay", "HubSpot", "Salesforce", "Pipedrive", "Zoho", "Apollo", "Zapier", "n8n", "Make.com", "Airtable", "Google Sheets"],
  "negativeKeywords": ["casino", "adult", "crypto pump", "personal blog"],
  "minFitScore": 0,
  "maxUrls": 10,
  "maxResults": 10,
  "timeoutSeconds": 10,
  "maxBytes": 300000,
  "respectRobotsTxt": true,
  "includeErrorRows": false
}

Example input — sample mode

{
  "source": "sample",
  "targetKeywords": ["B2B", "SaaS", "RevOps", "GTM", "automation", "integration"],
  "negativeKeywords": ["casino", "adult", "crypto pump"],
  "minFitScore": 50
}

Output fields

• company, url, page_title
• http_status, fetch_status
• fit_score, fit_label
• matched_keywords, negative_keywords
• trust_signals, missing_trust_signals
• risk_flags
• fit_reasons
• crm_segment
• recommended_action
• automation_note
• summary
• redacted_text_excerpt
• observed_at, source_mode

API, MCP, Clay, and CRM usage

• Apify API users can run the Actor synchronously and receive dataset items directly, or run asynchronously and read the default dataset.
• AI agents and API buyers can also use Apify's x402 agentic-payment flow: call the Actor without an Apify token using X-APIFY-PAYMENT-PROTOCOL: X402, receive 402 Payment Required, then retry with a valid PAYMENT-SIGNATURE header from an x402-compatible wallet/client.
• MCP / AI-agent users can expose Apify Actors through the Apify MCP server and consume the same flat dataset rows.
• Clay users can launch Apify Actor runs or retrieve results through Clay's Apify integration, then map fit_score, crm_segment, and recommended_action into a table.
• Apollo, HubSpot, Salesforce, Pipedrive, Zoho, and CRM users can import CSV/JSON rows as account-level enrichment, ABM scoring, and lead-prioritization fields. This Actor only scores companies; use your approved CRM/contact-data provider for any person/contact enrichment.
• Zapier, n8n, Make.com, Airtable, and Google Sheets users can trigger small public-URL batches and route flat result rows into existing review or enrichment workflows.

Local checks

cd /home/hercules/hermes-workspace/deep-research/apify-hermes-passive-income-20260704/templates/public-website-lead-fit-actor
python3 -m py_compile src/lead_fit.py src/main.py tests/conftest.py tests/test_lead_fit.py
PYTHONPATH=. uvx --with pytest pytest -q
PYTHONPATH=. python3 -m src.main
APIFY_CLI_DISABLE_TELEMETRY=1 apify validate-schema

Verified public Store / PPE status

• Public Actor slug: jorokotev/public-website-lead-fit.
• Pricing: Apify Pay Per Event (PPE), with one value event per default dataset item (apify-default-dataset-item) at $0.002/result.
• The Actor uses Apify's synthetic dataset-item charging; there is no custom Actor.charge() path in the code.
• Public URL guardrails, input schema validation, dataset schema validation, and local tests are part of the release package.
• Buyer guidance: start with sample mode or a small public-URL batch, then increase up to the documented maxUrls / maxResults caps.