Crunchbase Enterprise API

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.