Crunchbase API: Data, Pricing, and Limits Explained

The first time my team needed funding data at scale, I did what everyone does. I opened Crunchbase, searched a company, and copied the numbers into a spreadsheet by hand. Fine for ten companies. A nightmare for two thousand.

So we went looking for the API. And that’s where I learned the first hard lesson: buying a Crunchbase Pro seat does NOT give you API access. They’re two different products, on two different budgets. I wish someone had told me that before I spent a week assuming otherwise.

This guide is the honest version I wish I’d had. What the Crunchbase API actually gives you in 2026, what it costs, where it quietly falls short, and how to plug it into your CRM without creating a duplicate mess. Let’s get into it.

📌 TL;DR: The Crunchbase API delivers firmographics, funding rounds, investor data, and AI predictions through three packages: Fundamentals, Insights, and Predictions. But API access is a separate enterprise data-licensing contract, not part of a Pro web seat, and the old free API tier is gone. Expect custom annual pricing, cursor pagination, and a 200-calls-per-minute rate cap. Great for funding intelligence. Overkill if you just need company websites.

What Is the Crunchbase API?

The Crunchbase API is a REST endpoint that pulls Crunchbase’s company, funding, and investor data straight into your app, CRM, or database. Instead of clicking around the website, your code sends a request and gets structured JSON back. If APIs are new territory for you, here’s a plain-English primer on how an API works before we go deeper.

It runs on version 4. You authenticate with a user key, ask for the fields and “cards” you want, and Crunchbase returns the record. The current base URL is https://api.crunchbase.com/v4/data/, and yes, that exact path matters, because plenty of older tutorials still show the legacy one. The official API docs are the source of truth here.

That’s the pitch. Now here’s the part most guides skip.

Does Crunchbase Have a Free API?

No. Crunchbase no longer offers a free or low-cost self-serve API tier. The old “Basic” API that a lot of older tutorials reference has been retired. So if you land on a blog telling you to grab a free key in five minutes, that blog is out of date.

What CAN you get without a paid contract? A little. Crunchbase’s Open Data Map exposes basic firmographics like company name, website URL, and the unique Crunchbase identifier without a full license. That’s enough to match entities and confirm a company exists. It is NOT enough for funding history, financials, or predictions.

And this is the trap I fell into. A Crunchbase Pro seat (the web subscription your sales team logs into) does not include API access. Pro also caps how many rows you can export by hand. So the moment you need bulk data or automation, you’re pushed toward the enterprise API, which is a separate line item entirely.

💡 Watch out: "Can I just add the API to my Pro plan?" No. Web seats and API access are billed separately. Ask for API pricing specifically, or you'll budget for the wrong product.

What Data Do You Get? The Three Crunchbase API Packages

Crunchbase sells its API data in three packages: Fundamentals, Insights, and Predictions. Each one builds on the last, and you license the depth you need. Here’s the plain-English version, based on the official API packages overview.

Fundamentals (the core data)

This is the foundation layer, and it splits into three chunks. Core Firmographics covers company names, legal status, employee counts, and key leadership. Advanced Firmographics adds ownership structures, accelerators, and deeper context for firmographic segmentation. And Core Financials is why most people show up: funding stages, round history, valuations, and investor details.

If you’re doing data enrichment inside your CRM, Fundamentals is the tier you live in.

Insights (AI analyses)

The middle layer analyzes past and present private-market activity. It blends Crunchbase’s historical data with real-time engagement signals from its user base to surface trends and growth patterns. Think “which segments are heating up,” not just “what happened.”

Predictions (forecasts)

The top layer forecasts future market movements: funding rounds, exits, growth, layoffs, and closures. Crunchbase says it runs seven prediction models and claims 84% of real funding rounds are correctly forecast, per its API product page. Treat those as vendor claims, and treat the predictions themselves as one signal. Never the whole decision.

Here’s how the packages stack up:

That’s the data. Now let’s talk about getting your hands on it.

How Do You Access the Crunchbase API?

You access it by signing an enterprise licensing deal, receiving a user key, and sending authenticated requests to the entity endpoints. The most common starting point is the Entity Lookup, where you pass a company’s permalink and ask for specific fields.

Here’s a real Entity Lookup request in Python. It pulls Airbnb’s basics plus its founders, investors, and funding rounds:

import requests

url = "https://api.crunchbase.com/v4/data/entities/organizations/airbnb"

headers = {
    "X-cb-user-key": "your_api_key_here",
    "Content-Type": "application/json"
}

params = {
    "field_ids": "identifier,name,short_description,rank_org,website,founded_on",
    "card_ids": "founders,investors,funding_rounds"
}

response = requests.get(url, headers=headers, params=params)
print(response.json())

Two identifiers matter here, and mixing them up will cost you. The permalink (here, airbnb) is the human-readable slug. The UUID is the machine ID underneath. Permalinks can shift when companies rebrand or merge, so store the UUID as your permanent key and treat the permalink as a convenience. For the full field and card list, check the Crunchbase API docs. Don’t guess at field names, they’re specific.

One more 2026 note: Crunchbase now lists an MCP server among its products, which lets AI assistants query the data directly. If your team is wiring company data into an internal AI workflow, ask about it during the sales conversation.

Watch the rate limits and pagination

Two things will bite you here. First, rate limits. Crunchbase documents a cap of 200 calls per minute on its API endpoints. Blow past that and you get an HTTP 429 “Too Many Requests” error, not a friendly warning. Build in backoff and retry logic from day one.

Second, the v4 API uses cursor-based pagination. That means you page through big result sets by following a cursor token from one response to the next, not by asking for page 2. Miss that detail and your script quietly stops at page one. Ask me how I know.

What Does the Crunchbase API Cost?

API access is enterprise-only, with custom annual pricing, so there’s no public price tag. Even the “Explore API Pricing” button on Crunchbase’s own product page leads to a contact form, not a rate card. You get quoted based on your use case.

And the biggest cost driver isn’t volume. It’s HOW you use the data:

• Internal use license: enriching your own Salesforce or HubSpot records. Cheaper.
• Commercial license: showing Crunchbase data inside a product you sell to customers. Much more expensive.

Teams in RevOps communities commonly report entry deals starting in the low five figures per year and climbing from there. Treat that as a ballpark from practitioners, not an official quote, because your number depends on packages and license type. A useful negotiation lever: if you only need funding rounds and not predictions, say so. Dropping packages you won’t touch is your best pricing move.

🧠 Budget tip: There's also a Daily CSV Bulk Export. If your data team just wants to load everything into Snowflake or BigQuery once a day, that architecture can be cheaper and simpler than hammering the REST API in real time. Ask about both.

How Do You Match Crunchbase Data to Your CRM?

Match on the website domain first, then the LinkedIn URL, then the Crunchbase UUID. Never on the company name alone. This is the step that quietly makes or breaks the whole project, and it’s the one nobody warns you about.

Here’s the problem. Your CRM has “Meta.” Crunchbase has “Meta Platforms.” A name-only match either misses the record or, worse, creates a duplicate. And once you’ve got duplicate accounts, your reps stop trusting the data. Game over.

Duplicates kill trust. So here’s the fix. Use the domain as your primary join key, because it’s the one field both systems almost always share. Fall back to the LinkedIn URL for companies with messy or shared domains. Then store the Crunchbase UUID on every matched record, so future syncs are instant lookups instead of fuzzy searches. Domain-based data matching beats name matching by a wide margin on real B2B lists.

→ Clean domain → match on domain → fall back to LinkedIn URL → store the UUID → future syncs are one clean call. That’s the whole trick.

REST API or Daily CSV Bulk Export?

Choose the REST API for real-time, record-by-record lookups, and the Daily CSV Bulk Export when you want the whole dataset in your own warehouse. A lot of buyers say “API” when what their data team actually wants is the bulk export. Getting this wrong costs real engineering time.

Think of it this way. The REST API is a librarian you ask one question at a time. The bulk export is the whole library, delivered to your door once a day. Different jobs.

If your engineers want to run their own queries in BigQuery or Snowflake, the bulk export usually wins on both cost and sanity. Ask Crunchbase about both when you’re scoping the contract.

The Autocomplete cost trap

One quiet way to blow your rate limit: wiring the Autocomplete endpoint to a live search box. Every keystroke fires a call. Type “airbnb” and you’ve just made six requests. Multiply that by real users and you’ll hit the 429 wall fast.

So cache entity data locally. Pull the records you need, store them, and serve searches from your own copy. Save the live API calls for the moments you genuinely need fresh data.

Who Actually Uses the Crunchbase API?

Four groups get the most out of it, and they use it in very different ways. Knowing which one you are shapes the license you should buy.

• RevOps and SalesOps teams. They outgrow manual exports, then use the API to score and route inbound leads in Salesforce or HubSpot based on total funding.
• VC and PE deal sourcers. They don’t want real-time pings. They want the whole dataset in a local database to run proprietary scoring on early-stage targets.
• SaaS product managers. They embed company or investor data inside a product they sell. That means a commercial license and a hard focus on uptime and rate limits.
• Data scientists. They need historical data, not just the current state, to train models on what makes startups succeed or stall.

The trigger for most of them is the same: a company grows up. Founder-led sales with manual Crunchbase searches turns into a real SDR team that needs automated account scoring. And that’s when the API stops being a nice-to-have.

Where the Crunchbase API Falls Short

Crunchbase is excellent at funding data. It is NOT the best at everything. Being honest about the gaps saves you money and disappointment.

• Contact data lags. Emails and phone numbers aren’t Crunchbase’s strength. Specialized providers refresh those faster.
• Coverage skews to funded startups. A bootstrapped local business or a quiet mid-market company may have a thin profile or none at all.
• Freshness varies by field. Funding rounds update fast. Fields like employee counts or valuations on early-stage rounds can lag or sit empty.
• The build is real work. A resilient integration with retries, error handling, and matching logic takes weeks of engineering time, not a weekend.

🔍 Compliance note: Crunchbase data is subject to GDPR and CCPA rules, and your contract spells out data-retention rights. Check what happens to enriched records if you ever cancel, because some licenses require you to delete data you pulled.

When Crunchbase Is Overkill

Here’s the honest bit. If all you actually need is a company’s website from its name, an enterprise Crunchbase contract is a sledgehammer for a thumbtack.

Plenty of teams sign up for funding intelligence and then realize the job in front of them is just filling in missing domains on a lead list. For that, a focused tool that converts company names to domains costs a fraction and runs in bulk. You can often stack a cheap domain-finder step first and only pay premium rates for the rows that still need funding depth.

Match the tool to the task. That’s it.

My Crunchbase Integration, Honestly

Let me tell you how this went for me, because the lessons above weren’t free. Back in my Hamburg startup days, we had a target list of about 1,400 companies and a plan to score them by funding stage. I assumed our Pro seat covered the API. It didn’t. That assumption cost us a week of planning built on the wrong budget, and one awkward meeting where I explained why.

Then came the matching pass. Our first run joined on company names. It was a mess. Duplicates, misses, a rep asking why one account existed twice with two different funding totals. We rebuilt the join on domains with the UUID stored on each record, and the second pass was boring in the best way.

What surprised me most? The fill rates. Funding data on venture-backed accounts was rich. But a chunk of our quiet, bootstrapped mid-market targets barely had profiles. So we kept a second data source for those rows. Plan for that from the start and you’ll skip my week of pain.

How We Know This (and What to Double-Check)

Everything above comes from hands-on integration experience plus a fresh read of Crunchbase’s current documentation and product pages in August 2026. The package structure, the 200-calls-per-minute limit, and the base URL all come straight from the official docs. The prediction accuracy figures are Crunchbase’s own published claims, labeled as such.

What we can’t verify: private enterprise quotes. Pricing is negotiated deal by deal, so the community ballparks here are directional only. And API terms change without notice. Before you budget or build anything, spend ten minutes on Crunchbase’s current docs and confirm the limits yourself. That habit is free and it has saved me twice.

Frequently Asked Questions

Does Crunchbase have a free API?

No. Crunchbase retired its free and low-cost self-serve API tiers. You can pull very basic firmographics through the Open Data Map without a full license, but funding, financials, and predictions require a paid enterprise contract.

Is Crunchbase API access included in a Pro plan?

No. A Crunchbase Pro web seat and API access are separate products with separate pricing. Pro caps manual exports too, which is usually what pushes teams toward the API in the first place.

What is Crunchbase used for?

Crunchbase is used for company and startup intelligence: funding rounds, investors, valuations, firmographics, and market research. Sales and investment teams use it to source deals, score accounts, and research competitors.

How much does the Crunchbase API cost?

Pricing is custom and enterprise-only, so there’s no public rate card. Your cost depends mainly on license type (internal use versus commercial) and which data packages you need. Practitioners commonly report entry deals starting in the low five figures per year.

Who owns Crunchbase?

Crunchbase is owned by Crunchbase, Inc., an independent venture-backed company. It started in 2007 as TechCrunch’s startup database, passed to AOL in 2010, and spun out as its own company in 2015.

Is Crunchbase reputable?

Yes, Crunchbase is a widely used and established source for private-market data. Its records blend contributions, partner feeds, and analyst validation, so quality is strong but not perfect. Spot-check any record that drives a real decision.

Do I need a sales rep to get an API key?

For full API access, yes. Since it’s an enterprise data-licensing agreement, you go through Crunchbase’s team to scope your use case, agree on packages, and sign a contract before you get production keys.

What is a good Crunchbase API alternative for finding company websites?

If your only goal is turning company names into website domains, a dedicated name-to-domain tool is faster and far cheaper than a Crunchbase contract. Crunchbase makes sense when you specifically need funding and investor intelligence. And if your pipeline runs on LinkedIn, the LinkedIn Sales Navigator API is another gated-but-powerful option I’ve broken down.

You Got This

So here’s the short version. The Crunchbase API is powerful for funding intelligence, it lives behind an enterprise contract, and it rewards teams who plan the licensing, the rate limits, and the CRM matching before they write a line of code.

Start by writing down the ONE job you actually need done. If it’s funding data, Crunchbase earns its keep. If it’s just missing company websites, save your budget and reach for a focused domain tool instead. You’ve got this.