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

# Crunchbase Enterprise API

The Crunchbase Enterprise tier exposes 57 endpoints covering organisations, people, funding rounds, acquisitions, investments, IPOs, layoffs, key employee changes, ownership, jobs, and many other relationship entities. It supports entity lookups, per-card field-set retrieval, faceted search, autocomplete, and deleted-entity tracking. Authentication uses an API key passed in the X-cb-user-key header.

## For AI agents

Run faceted searches and entity lookups across Crunchbase's full Enterprise dataset - organisations, people, IPOs, layoffs, ownership, key employee changes, and more.

## Scope

Does not handle CRM record creation, outbound messaging, or financial transaction execution - use for reading Crunchbase Enterprise company, people, and event data only.

## Capabilities

- Look up any of 17 entity types (organisations, people, funding rounds, acquisitions, investments, IPOs, jobs, locations, ownerships, press references) by Crunchbase entity ID
- Retrieve a single field-card on any entity for narrow, low-cost reads
- Run structured faceted searches over 20 entity types using rich query bodies
- Autocomplete identifiers across entity types for type-ahead components
- Track deleted entities globally or scoped to a specific collection
- Discover key employee changes and layoff events to monitor company signals

## Use cases

### Enterprise Account Intelligence

Build a 360-degree picture of a target enterprise account by combining organisation lookups with linked funding rounds, IPOs, key employee changes, and layoff events. The Enterprise tier exposes the full relationship graph in a single API.

Example prompt: GET `/entities/organizations/{entity_id}` for the target, then POST `/searches/key_employee_changes` and `/searches/layoffs` filtered by organization_identifier to assemble a recent-signal feed.

### Investor and IPO Monitoring

Watch IPOs, ownership changes, and fund activity in real time by polling search endpoints with date filters and resolving each event to its full detail. Enables capital-markets and competitive-intelligence dashboards.

Example prompt: POST `/searches/ipos` filtering went_public_on within the last 30 days, then GET `/entities/ipos/{entity_id}` per result for amount_raised, valuation, share_price, and stock_exchange_symbol.

### Talent and Workforce Signals

Track hiring and attrition signals at target firms by querying the key_employee_changes, layoffs, and jobs entity searches. The Enterprise API surfaces these as searchable Crunchbase collections rather than scraped events.

Example prompt: POST `/searches/layoffs` filtered by key_event_date within the last 14 days, then enrich each result with GET `/entities/organizations/{entity_id}` using the layoff's organization_identifier for the affected company.

### Card-Level Field Reads

Reduce response size by requesting only the field card you need on an entity (e.g. just the raised_funding_rounds card for an organisation) instead of the full entity payload. Useful for high-volume enrichment pipelines.

Example prompt: Call GET `/entities/organizations/{entity_id}/cards/{card_id}` with card_id=raised_funding_rounds to fetch only funding context for a target organisation, narrowing further with card_field_ids.

### Agent-Driven Deal Research

Allow an AI deal-research agent to answer multi-hop questions ('Which Series B fintechs in NYC had layoffs this quarter?') by chaining searches and lookups through Jentic so the API key stays in your own Jentic One instance.

Example prompt: Search Jentic for 'find recent layoffs at fintech companies', load the layoffs search operation, and execute it with the relevant filters.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/entities/organizations/{entity_id}` | Look up an organisation |
| POST | `/searches/organizations` | Faceted search over organisations |
| POST | `/searches/funding_rounds` | Search funding rounds |
| POST | `/searches/ipos` | Search IPO events |
| POST | `/searches/layoffs` | Search layoff events |
| POST | `/searches/key_employee_changes` | Search key employee changes |
| GET | `/autocompletes` | Autocomplete identifiers across entity types |
| GET | `/deleted_entities` | Track deleted entities |

## Key resources

- **Entity** — Lookup endpoints for 17 entity types: organisations, people, funding rounds, acquisitions, investments, IPOs, ownerships, jobs, addresses, degrees, categories, category groups, events, event appearances, funds, locations, and press references. Each also has a single-card variant.
- **Search** — Faceted POST search across 20 collections: organisations, people, funding rounds, acquisitions, investments, events, event appearances, press references, funds, IPOs, ownerships, categories, category groups, locations, jobs, key employee changes, layoffs, addresses, degrees, and principals. Layoffs, key employee changes and principals are search-only, with no lookup endpoint.
- **Autocomplete** — Type-ahead identifier suggestions across all entity types.
- **Deleted Entities** — Track deleted entities globally or per collection for downstream cache invalidation.

## Why Jentic

- **Setup:** Wiring the Crunchbase Enterprise API by hand means placing your key in the X-cb-user-key header, building the POST search bodies for organizations, funding rounds, IPOs, and layoffs, and handling autocomplete yourself. Through Jentic you install once, import the Crunchbase Enterprise API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Crunchbase Enterprise puts the entity id in the URL path for lookups (`/entities/organizations/{entity_id}`), so a rule can pin your agent to reading one organization. You choose the operations it may call, so the search endpoints for layoffs or key employee changes are not included unless you add them.
- **Credential handling:** Your Crunchbase Enterprise API key is stored once, encrypted, by your own Jentic One instance and injected into the X-cb-user-key header at execution time. 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 'search funding rounds', and Jentic returns the matching Crunchbase Enterprise operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Crunchbase API** — Smaller v4 surface focused on the core entity types.
- **Crustdata API** — Alternative company and people enrichment dataset.
- **Cruise Control API** — Outbound review-request automation that benefits from enriched contacts.

## FAQ

### Which OpenAPI specification does this Crunchbase Enterprise API entry describe?

Crunchbase's own. The document is published on the Crunchbase SwaggerHub organisation at https://api.swaggerhub.com/apis/Crunchbase/crunchbase-enterprise_api/1.0.3 and this entry is that document: the same 57 operations, the same https://api.crunchbase.com/api/v4 server, and the same X-cb-user-key security scheme. Crunchbase's documentation site also publishes newer per-package definitions, so check its reference pages if you need a collection this one does not carry.

### What authentication does the Crunchbase Enterprise API use?

The Enterprise API uses an API key passed in the X-cb-user-key request header, required by 57 of the 57 operations this document declares. Crunchbase's own documentation also shows the same key sent as a user_key query parameter, which this document does not declare. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so the agent never receives its raw value.

### Can I track layoffs and key employee changes with the Crunchbase Enterprise API?

Yes. POST `/searches/layoffs` and POST `/searches/key_employee_changes` accept filter bodies and return matching events, each carrying an organization_identifier and a key_event_date. Neither collection has a lookup endpoint, so expand a result with GET `/entities/organizations/{entity_id}` on that organization_identifier rather than an `/entities/layoffs` path.

### How do I retrieve only the funding card for an organisation through the Crunchbase Enterprise API?

Use GET `/entities/organizations/{entity_id}/cards/{card_id}` with card_id=raised_funding_rounds, and narrow the response further with card_field_ids. This returns a narrow payload instead of the full entity body, which helps in high-volume enrichment pipelines.

### What are the rate limits for the Crunchbase Enterprise API?

The OpenAPI specification does not state a rate limit, and Crunchbase does not publish one in its API documentation. Confirm the limits that apply to your package with Crunchbase, and handle HTTP 429 responses defensively.

### How do I run a Crunchbase Enterprise search through Jentic?

Install Jentic One on its own machine, run `jentic register` on the machine your agent runs on, then import the Crunchbase Enterprise API from the API Directory and store your API key once. Your agent searches by intent for 'find recent layoffs at fintech companies', loads the schema for POST `/searches/layoffs`, and executes it with your filter body while Jentic injects the X-cb-user-key header.

### Is there a Crunchbase MCP server?

Yes. Crunchbase runs an official remote MCP server at https://mcp.crunchbase.com, authenticated with OAuth 2.1 and sold as a per-user MCP seat on your workspace. You can also connect the Crunchbase Enterprise API directly through Jentic: your agent gets the full 57-endpoint surface from the spec, no extra tool definitions are loaded into its context, your API key is injected at call time by your own self-hosted Jentic One instance instead of sitting in an MCP config file, and your rules decide which operations the agent may call.

### Can I limit what my agent is allowed to do with the Crunchbase Enterprise API?

Yes. Because Jentic One is self-hosted, you decide which Crunchbase Enterprise operations and credentials your agent may use. You can allow only entity lookups such as GET `/entities/organizations/{entity_id}`, which puts the entity id in the URL path so a rule can pin the agent to reading a single organisation. The faceted search endpoints like POST `/searches/layoffs` and POST `/searches/key_employee_changes` are not available to the agent unless you explicitly add them to its allowed operations.