canonical: https://jentic.com/apis/crunchbase.com

# Crunchbase APIs

Crunchbase provides firmographic, funding, and relationship data on private and public companies, the people behind them, investors, and market events. Its APIs let you look up organisations, people, funding rounds, acquisitions, investments, and funds by entity ID, run faceted searches with rich filter bodies, and drive type-ahead autocomplete. The Enterprise tier adds IPOs, layoffs, key employee changes, ownership graphs, jobs, and other relationship entities, plus deleted-entity tracking for keeping downstream stores in sync. Jentic publishes and maintains the OpenAPI specifications for both surfaces so AI agents can call them through structured tooling.

## For AI agents

An agent can look up and search Crunchbase organisations, people, funding rounds, acquisitions, investments, and funds, and on the Enterprise tier also monitor IPOs, layoffs, key employee changes, and ownership, then resolve any result to its full entity detail.

## Scope

Use for: Reading Crunchbase company, people, funding, investor, and market-event data through entity lookups and faceted search

Not supported:
- CRM record creation
- outbound messaging
- financial transaction execution
- real-time streaming
- write operations

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Crunchbase Enterprise API | data-enrichment | 57 | Run faceted searches and entity lookups across Crunchbase's full Enterprise dataset - organisations, people, IPOs, layoffs, ownership, key employee changes, and more. |
| Crunchbase API | data-enrichment | 15 | Look up companies, people, funding rounds, and investments on Crunchbase, plus run faceted searches and autocomplete queries against the v4 dataset. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Core firmographic and funding data on companies, people, funding rounds, acquisitions, investments, and funds | crunchbase-api | The v4 REST surface with 15 endpoints covers entity lookups, faceted search, and autocomplete for the core entity types at a lighter footprint. |
| Wider relationship graph including IPOs, layoffs, key employee changes, ownership, and jobs | main | The Enterprise tier exposes 57 endpoints across 18+ entity types, adding signal entities and per-card field reads the v4 surface does not include. |

## Cross-API use cases

### Account research with workforce signals

Pull core firmographic and funding context on a target company from the v4 surface, then layer on Enterprise-only signals such as recent layoffs and key employee changes to brief a sales or research team.

Example prompt: GET `/data/entities/organizations/{entity_id}` on the crunchbase-api surface for firmographics, then POST `/searches/layoffs` and `/searches/key_employee_changes` on the Enterprise surface filtered by that organisation to attach recent signals.

### Deal flow tracking across funding and IPOs

Monitor acquisitions and funding rounds through the v4 surface and IPO events through the Enterprise tier, resolving each event to full detail for a combined capital-markets feed.

Example prompt: POST `/data/searches/acquisitions` and `/data/searches/funding-rounds` on crunchbase-api with date filters, then POST `/searches/ipos` on the Enterprise surface and GET each `/entities/ipos/{entity_id}` for valuation and underwriter detail.

### Investor and portfolio mapping

Walk investor, fund, and funding-round edges on the v4 surface and extend the map with ownership entities available only on the Enterprise tier to trace holding structures.

Example prompt: POST `/data/searches/funding-rounds` on crunchbase-api filtered by investor, then POST `/searches/ownerships` on the Enterprise surface to resolve the ownership graph for the same organisations.

## Why Jentic

- **Setup:** Wiring both Crunchbase surfaces by hand means placing your key in the X-cb-user-key header, building POST search bodies for organisations, funding rounds, IPOs, and layoffs, and handling autocomplete on each API separately. With Jentic One installed, your agent finds and adds either Crunchbase API from the Jentic directory to your workspace, stores the key once, and calls both.
- **Permission scoping:** Crunchbase puts the entity id in the URL path for lookups, so a rule in your own Jentic One instance can pin your agent to reading a single organisation or person. You choose which operations it may call, so the Enterprise search endpoints for layoffs or key employee changes are excluded unless you add them.
- **Credential handling:** Your Crunchbase API key is stored encrypted by your own Jentic One instance and injected into the X-cb-user-key header at execution time across both surfaces. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find recent layoffs at fintech companies' or 'find company funding history', and Jentic returns the matching Crunchbase operation with its input schema so the agent calls the right endpoint on the right surface without browsing the reference docs.

## Related vendors

- **Crustdata** — Alternative company and people enrichment dataset for coverage or licensing gaps in Crunchbase.
- **Clearbit** — Firmographic and company enrichment often used alongside funding data for account research.
- **Apollo** — Company and contact data provider used for sales prospecting on top of firmographic enrichment.
- **PitchBook** — Adjacent private-market and funding intelligence source for investor and deal research.

## FAQ

### What data can I get across the Crunchbase APIs?

Between the two surfaces you can read organisations, people, funding rounds, acquisitions, investments, events, and funds, and on the Enterprise tier also IPOs, layoffs, key employee changes, ownership, jobs, and other relationship entities. Both support entity lookups by ID, faceted search, and autocomplete.

### What is the difference between the Crunchbase API and the Crunchbase Enterprise API?

The Crunchbase API is a 15-endpoint v4 surface focused on the core entity types. The Crunchbase Enterprise API is a 57-endpoint surface that adds IPOs, layoffs, key employee changes, ownership, jobs, per-card field reads, and deleted-entity tracking across 18+ entity types. Pick the lighter surface for core firmographic and funding needs and the Enterprise tier when you need the wider relationship graph and signal entities.

### Does one credential work across both Crunchbase APIs?

Yes. Both APIs authenticate with a Crunchbase API key in the X-cb-user-key header, so a single key can call both surfaces as long as your Crunchbase contract grants the relevant access tier.

### Are these official Crunchbase OpenAPI specifications?

Crunchbase does not publish OpenAPI specifications. Jentic generates and maintains the specs for both surfaces, validates them against the live API, and keeps them agent-ready so AI agents and developers can call Crunchbase through structured tooling.

### Can I use these APIs to write data back to Crunchbase or a CRM?

No. Both surfaces are read-only for Crunchbase data. They do not create CRM records, send outbound messages, or execute transactions. Use them to look up and search company, people, funding, and event data, then hand results to a separate system for any write action.

### How do the Crunchbase APIs handle records that get removed from the dataset?

Both surfaces expose deleted-entity tracking so a downstream cache or CRM can stay in sync. You can poll for entities deleted globally, and the Enterprise tier also scopes deletions to a specific collection.