Crunchbase Company Page Scraper
Crunchbase company pages are a common starting point for funding research, competitor tracking, and investor mapping.
This scraper takes a public Crunchbase URL, renders the page in a real browser, and hands back either the rendered HTML or structured JSON. You supply the URL and the extraction rules; the service handles proxies, rendering, and anti-bot work on its side.
What one request returns
A request is built around a single public Crunchbase URL. The service fetches the page, executes its JavaScript, and returns the post-render HTML. If you want structured output instead of markup, you attach extraction rules and the response comes back as JSON.
Fields commonly available on public Crunchbase company pages include the company name, founding date, funding round history, total raised, team size, industry, founder profiles, and key investor relationships. What you actually receive depends on what the page renders and on the rules you write — the scraper does not add data that is not on the page.
Two extraction paths exist:
- Selector rules — you point at elements with CSS selectors (or XPath) and name the output fields yourself. Precise, but it breaks when the page markup changes.
- AI extraction rules — you describe the fields you want in natural language and the service maps them. More tolerant of layout shifts, less deterministic about exact output shape.
If neither is supplied, you get the rendered HTML and parse it yourself.
Matching the parameter to the job
The three common Crunchbase jobs differ less in the URL than in the parameters and extraction rules you attach.
| Job | What you are after | Parameters that matter | Output to expect |
|---|---|---|---|
| Funding analysis | Round history, amounts, dates, total raised | render_js=true, selector or AI rules scoped to funding sections | JSON array of rounds plus a total |
| Executive research | Names and titles of leadership | render_js=true, rules targeting the people section | Name/title pairs, sometimes with profile links |
| Partnership and investor mapping | Board memberships, investor portfolios, disclosed partnerships | render_js=true, stealth_proxy=true if the run is large, rules spanning multiple page sections | Relationship records that usually need joining across several company pages |
The third job is the one that most often surprises teams: a single company page gives you that company's relationships, not the full network. Building an investor map means collecting many pages and reconciling names yourself.
A worked example on one company page
Suppose you want to compare funding across a list of 200 startups. For each company you would:
- Collect the public Crunchbase company URL.
- Send it with
render_js=trueso the funding section is present in the returned HTML. - Attach extraction rules for company name, founding date, each funding round, and total raised.
- Store the JSON rows keyed by company URL.
What you get back is a per-company record. What you do not get back is a normalized currency, a deduplicated investor list, or a resolved parent/subsidiary relationship — those are your transformations. Plan for a cleaning step between the scrape and the analysis, and keep the raw JSON so you can re-derive fields when your rules change.
A practical check before scaling: run the same URL twice and diff the output. Fields that change between runs (view counts, recently-updated badges) should be excluded from your rules so they do not create false diffs downstream.
Three different failures, three different fixes
A failed run is not one problem. Distinguishing these three saves the most time:
- Blocked request. The response is a challenge page or an error rather than the company page. Fix: enable
stealth_proxyon the request so traffic routes through residential IPs. - Missing content after a successful fetch. The HTML arrives but the funding or people section is empty. This is a JavaScript-rendering gap, not a block. Fix: set
render_js=trueso the page executes before capture. - Empty or wrong fields in otherwise correct JSON. The page rendered and the request succeeded, but your selectors no longer match. Fix: re-inspect the page and update the rules, or move that field to AI extraction rules.
A geo-specific variant sits alongside these: if content differs by visitor location, pass country_code to route through a residential IP in that country.
How requests translate into credits
Credits are consumed per successful request, and the advanced parameters change the multiplier:
- A base request starts at 1 credit.
- Enabling JavaScript rendering makes that request cost 5 credits.
- Enabling premium proxies costs 10 credits without JS rendering, or 25 credits with it.
So a Crunchbase page fetched with both rendering and premium proxies consumes 25 credits, not 1. At 25 credits per page, a 1,000-page run costs 25,000 credits — worth calculating before choosing a tier.
API credits are valid for one month and do not roll over. Concurrent requests are the number of calls that can be in flight simultaneously. Plan tiers differ on credits, concurrency, and support level; the plan table below lists each tier's figures as published at the time of capture, so confirm current pricing before purchase.
Getting to a first request
The path from zero to a working call is short:
- Create an account and take the API key and starting credits.
- Pick a client: Python, Node.js, Go, PHP, Ruby, Java, or raw cURL.
- Send the Crunchbase URL as a GET or POST to the API endpoint.
- Add parameters only as the job requires — rendering, stealth proxy, country code, extraction rules.
If you prefer not to write code, the dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in any of the supported languages.
Before you collect
Scraping public pages does not remove your obligations. Crunchbase's own terms govern what you may do with its data, and personal data about founders and executives is still personal data under privacy regimes. Decide in advance what you will store, how long you will keep it, and whether your use case needs a licensed data source instead.
| Plan | Price | API credits | Concurrent requests | JS rendering | Premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Prices and limits as published at the time of capture; all prices exclusive of VAT. Verify current pricing before purchase.
Frequently asked questions
What data can I extract from Crunchbase?
Whatever the public page renders is fair game. Point CSS selectors at the elements you want through extract_rules, or describe the fields in plain language through ai_extract_rules; either route returns structured JSON rather than raw markup.
How do I get started scraping Crunchbase?
Sign up, grab your API key, and send a GET request with the target URL. We render the page, rotate proxies, and return the data. 1,000 free credits to test.
Will I get blocked when scraping Crunchbase?
Requests are routed through rotating residential proxies and driven by a real headless browser, so they resemble ordinary visitor traffic. When a target tightens its defenses, switch on stealth_proxy for that request.
Can I scrape Crunchbase without writing code?
Yes. Our dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.
How do I handle JavaScript when scraping Crunchbase?
Set render_js=true. The page then loads inside a real headless browser, its JavaScript runs on the server, and you receive the HTML as it looks after rendering.
Can I scrape Crunchbase from a specific country?
Yes. Add country_code to the request and it exits through a residential IP in that country — handy whenever the visible content shifts by visitor location.