Crunchbase Company Scraper — Profiles, Funding & Investors

Crunchbase Company Scraper — Profiles, Funding & Investors

Used by VC analysts building deal sourcing pipelines, growth teams enriching prospect lists with funding signals, and AI agents doing investor research mid-conversation.

Scrape Crunchbase company profiles with funding round count, investor count, headcount range, categories, website, HQ location, social links, and Crunchbase's own growth & heat momentum scores — no API key or login required. Provide company slugs or search keywords and get clean JSON output instantly.

$9.00 per 1,000 company records (Pay Per Event) — clean, flat output that undercuts the heavier raw-dump scrapers.

---

What You Get

Each record contains these fields:

Field	Description
name	Company display name
permalink	Crunchbase slug (URL-safe ID)
short_description	One-line company description
categories	Industry category names (list)
headquarters	City, Region, Country
num_employees	Headcount band (e.g. c_05001_10000, 10001+)
website	Company homepage URL
contact_email · contact_phone	Primary public contact email & phone
num_contacts · num_contact_emails · num_contact_phones	Contacts-on-file counts
web_visits_monthly · web_visits_mom_pct	SEMrush monthly web traffic + MoM change
num_technologies	BuiltWith count of technologies used
num_funding_rounds	Count of all funding rounds
last_funding_type	Most recent round type (e.g. series_c, seed, secondary_market)
investor_count · num_investments	Distinct investors · investments made
legal_name · stock_symbol	Registered legal name · public ticker
growth_score	Crunchbase growth score (0–100 momentum)
heat_score	Crunchbase heat score (0–100 trending intensity)
rank_org_company	Global Crunchbase company rank (lower = bigger)
company_type	for_profit / non_profit
ipo_status	private / public / delisted
num_acquisitions	Count of acquisitions made
linkedin_url · facebook_url · twitter_url	Company social profiles
founded_on · total_funding_usd · last_funding_at	Populated when Crunchbase exposes them publicly; null for profiles where these are login-gated
url	Full Crunchbase profile URL
scraped_at	ISO timestamp of this run
parse_confidence	0.0–1.0 data quality score
warnings	Machine-readable quality flags

---

Input

Organization Slugs (direct lookup — recommended)

Fetch specific companies by their Crunchbase permalink (the slug in the URL crunchbase.com/organization/<slug>):

{
  "organizationSlugs": ["airbnb", "stripe", "openai", "anthropic"]
}

Search Queries

Find companies by keyword:

{
  "searchQueries": ["generative AI startup", "fintech payments"],
  "maxSearchResults": 25
}

No API key, no login, no proxy configuration needed. Just add the slugs and run.

---

Use Cases

• VC sourcing — enrich a list of portfolio-company slugs with funding totals, round count, investors, and categories in bulk
• Sales intelligence — qualify leads by funding stage, headcount, and category before outreach
• Competitive research — profile every competitor by funding, HQ, employee band, and industry categories
• AI agent tools — mid-conversation lookups: "How much has Anthropic raised?", "Get all Series A AI startups"

---

Use with AI agents (MCP)

Point your MCP client at this tool for real-time Crunchbase lookups mid-conversation:

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.apify.com/?actors=bovi/crunchbase-scraper",
        "--header",
        "Authorization: Bearer <YOUR_APIFY_TOKEN>"
      ]
    }
  }
}

Minimal agent input (direct slug lookup):

{
  "organizationSlugs": ["anthropic", "openai", "stripe"]
}

No API key needed from the caller — just slugs.

---

Sample Output

{
  "name": "Stripe",
  "permalink": "stripe",
  "short_description": "Stripe is a financial technology company that provides online payment processing and payment infrastructure.",
  "categories": ["B2B", "Financial Services", "FinTech", "Payments", "Mobile Payments"],
  "headquarters": "South San Francisco, California, United States",
  "num_employees": "c_05001_10000",
  "website": "https://stripe.com",
  "contact_email": "dpo@stripe.com",
  "contact_phone": "+1 888 926 2289",
  "num_contacts": 4741,
  "web_visits_monthly": 192623772,
  "num_technologies": 72,
  "last_funding_type": "secondary_market",
  "num_funding_rounds": 23,
  "investor_count": 68,
  "num_investments": 95,
  "num_acquisitions": 21,
  "growth_score": 99,
  "heat_score": 77,
  "rank_org_company": 76,
  "company_type": "for_profit",
  "ipo_status": "private",
  "linkedin_url": "https://www.linkedin.com/company/stripe",
  "url": "https://www.crunchbase.com/organization/stripe",
  "parse_confidence": 1.0
}

Note: founded_on, total_funding_usd and last_funding_at are returned when Crunchbase exposes them publicly; for profiles where these are login-gated they come back null (the values are not available to any logged-out scraper).

Run status

The actor stores a run-level RUN_STATUS key containing per-outcome counts and coverageComplete.

Outcome codes:

• ok — the protected target was fetched and parsed successfully
• challenge_page — a challenge page was returned instead of the protected target
• auth_or_proxy_error — authentication or proxy access prevented access to the protected target
• fallback_unavailable — the fallback path was not available
• fallback_exhausted — fallback attempts ended without obtaining the protected target
• transport_error — a network or other transport failure prevented completion

coverageComplete is true when every requested target has a recorded outcome, including non-success outcomes; otherwise it is false.

---

Pricing

Pay-per-result (PPE) — one charge per company profile returned. Every profile includes the full field set: contacts (email/phone), web-traffic, tech count, funding rounds, investors, growth/heat scores and social links.

• 100 profiles = a few cents
• 1,000 profiles = the per-1K rate shown on the pricing tab

No subscription, no API key, no per-field upcharge — every record is the complete profile.

---

vs other Crunchbase scrapers

	This actor	pratikdani/crunchbase-companies	vulnv/crunchbase-scraper-pro	davidsharadbhatt
Output style	clean flat fields	98 raw nested objects	97 flat fields	bulk CSV
Usable without post-processing	✅	❌ (raw dump)	✅	✅
Contact email + phone	✅	nested	✅	partial
Web traffic + tech count	✅	nested	✅	❌
Growth / heat momentum scores	✅	nested	✅	❌
Targeted single-company lookup	✅	✅	✅	❌ (min 1,000)
parse_confidence quality flag	✅	❌	❌	❌
Store rating	new	⭐1.5	⭐5	⭐4.8

The market leader by volume returns a 98-field raw dump that buyers must flatten themselves (hence its low rating). This actor returns the same depth as clean, flat, ready-to-use columns.

FAQ

Do I need an API key or login? No. Provide company slugs (e.g. stripe, airbnb) and run — no Crunchbase account, no proxy config.

Why is total_funding_usd sometimes null? Crunchbase gates the exact total-funding figure behind login for many companies. We return it when it's public; otherwise it's null — no logged-out scraper can read it. Funding-round count, last-round type, and investor count are always returned.

What's the difference vs the high-volume competitor? That actor dumps ~98 raw nested Crunchbase objects you have to parse yourself. This actor flattens the same data into clean, documented columns plus contact email/phone and web-traffic — ready for your CRM or sheet.

Is this affiliated with Crunchbase? No — independent tool, public data only.

---

What parse_confidence Means

• 1.0 — all key fields present
• 0.8–0.9 — minor optional fields missing (normal for early-stage companies)
• < 0.7 — critical fields missing; inspect warnings for details

Common warning codes:

• name_missing — no company name found
• short_description_missing — no description (common for very new companies)
• permalink_missing — slug not returned

---

Integrations

Built for VC analysts and growth teams building deal-sourcing pipelines with startup funding history and investor signals — the JSON/dataset output drops into the tools you already run:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into Google Sheets, Airtable, Slack, HubSpot, or your database: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client.
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

---

Not affiliated with Crunchbase. Crunchbase is a trademark of Crunchbase Inc.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Companies France
• Companies House UK Scraper
• Seeking Alpha Scraper
• Transfermarkt Scraper
• Unusual Options Activity
• Yahoo Finance Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.