Crunchbase APIs for AI Agents
Data EnrichmentCompany DataMixed ProvenanceAPI keyAgent Ready
For Agents
APIs2 in catalogue
Endpoints72 indexed
AuthAPI key — 1 credential for all 2 APIs
ProvenanceMixed provenance
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.
Crunchbase pairs a broad company and funding dataset with a relationship graph that links organisations to their people, investors, funding events, and workforce signals, all reachable through entity lookups and faceted search rather than scraped sources. The Enterprise tier widens that graph to IPOs, layoffs, key employee changes, and ownership as first-class entities.
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
Credentials: Both APIs authenticate with a Crunchbase API key passed in the X-cb-user-key header, so one Crunchbase key can cover both surfaces subject to the access tier your Crunchbase contract grants.
Across 2 Crunchbase APIs: 1 vendor-official, 1 Jentic-generated, all indexed by Jentic and kept validated and agent-ready.
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.
Crunchbase API Catalog
2 APIs across 1 product group. All share one credential.
Data Enrichment2
Crunchbase Enterprise APIRun faceted searches and entity lookups across Crunchbase's full Enterprise dataset - organisations, people, IPOs, layoffs, ownership, key employee changes, and more.~57 endpointsCrunchbase APILook up companies, people, funding rounds, and investments on Crunchbase, plus run faceted searches and autocomplete queries against the v4 dataset.~15 endpoints
Which Crunchbase API should I use?
| I want to... | Use |
|---|---|
| Core firmographic and funding data on companies, people, funding rounds, acquisitions, investments, and funds | Crunchbase API |
| Wider relationship graph including IPOs, layoffs, key employee changes, ownership, and jobs | Crunchbase Enterprise API |
Install Jentic One Beta
Connect the Crunchbase APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Crunchbase APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcrunchbase.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcrunchbase.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “find company funding and layoff data for a target account”.
What AI Agents Can Do with Crunchbase
Each workflow spans multiple Crunchbase APIs. Jentic routes each operation to the right API automatically.
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.
APIs used
Crunchbase API + Crunchbase Enterprise API
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.
APIs used
Crunchbase API + Crunchbase Enterprise API
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.
APIs used
Crunchbase API + Crunchbase Enterprise API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
FAQs
Specific to using Crunchbase APIs through Jentic.
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.
If you need a different Data Enrichment vendor
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.