Crunchbase API Alternatives: Getting Funding Data by the Call
Crunchbase and PitchBook sell seats. If you only need funding fields on a domain, an enrichment call carries them. What it returns, and what it gets wrong.

Crunchbase and PitchBook are sold the way market data is sold: a seat, a contract, an annual number. That is the right shape if a team lives in the product all day, and the wrong shape if what you actually need is four fields attached to a domain inside a pipeline nobody logs into.
This is about the second case. Monid is the OpenRouter for agent tools, and company enrichment endpoints in the catalogue carry funding history alongside firmographics, which most people using them do not realise.
Fair disclosure: you are on the Monid blog. The section on when you genuinely need Crunchbase or PitchBook is not a courtesy, and for a real share of readers it is the answer.
Is there a Crunchbase API alternative that bills per call?
Yes, if what you need is funding fields on a company rather than a funding database you can query.
That distinction decides everything, so it is worth being precise about which you have.
A funding database answers questions like "every Series B in fintech in Q2, sorted by size". You are querying rounds. That is what Crunchbase and PitchBook sell, and no enrichment endpoint substitutes for it.
Funding fields on a company answers "how much has this company raised, and when did they last do it", for a company you already identified. That is a lookup, and enrichment endpoints carry it.
Most GTM work is the second. You have an account list, and you want the funding signal on those accounts, not a market map.
monid inspect -p pdl -e /v5/company/enrich
monid run -p pdl -e /v5/company/enrich -i '{"website":"<domain>"}'
inspect is free and prints the schema and price. The call bills per company, so a hundred accounts is a hundred calls and a market map is not on the menu.
For agents
Grab an API key at app.monid.ai, then paste this to your agent and hand it the key:
set up https://monid.ai/SKILL.md
It learns the whole discover, inspect, run workflow itself. More in the agent quickstart.
For humans
npm install -g @monid-ai/cli
monid keys add -k <your-key> -l main
Give this to your agent![]()
Set up https://monid.ai/SKILL.md, and then use Monid to show me what I can do for Company Enrichment.What funding fields does one enrichment call actually return?
Five, and they are more detailed than the field list suggests. We ran one call on 2026-08-17 and read what came back:
total_funding_raised a single cumulative figure
latest_funding_stage e.g. "debt_financing"
last_funding_date e.g. "2026-06-09"
number_funding_rounds e.g. 30
funding_stages the full list of stage types the company has raised
That last field is the one worth having. On the company we tested it listed fourteen distinct stage types across thirty rounds: seed through Series H, plus convertible notes, secondary market activity, corporate rounds, debt financing and undisclosed.
A stage list is a funding history in one field. You cannot reconstruct dates or amounts per round from it, so it is not a substitute for a rounds table. What it does give you is shape: a company that has raised A through H is a different animal from one with a seed and a bridge, and the list says so without a second call.
Two more fields travel with it and matter for how you use the rest:
employee_count_by_country turns a headcount into a footprint, which is usually the better segmentation axis for anything territory-shaped.
likelihood is the provider's confidence that the company it matched is the one you asked for. It is the first field to read on any bulk run, because everything else is conditional on the match being right. It measures identity resolution and not field accuracy, so a high value does not mean the funding figures are current.
Where does this data get funding wrong?
In one specific and predictable place: latest_funding_stage on its own will mislead you.
On our measured company, that field read debt_financing. Read alone, that is a company taking on debt, which for most scoring models is a late, defensive or distressed signal. Read alongside funding_stages, which listed Series A through H, and number_funding_rounds at thirty, the picture is completely different: a heavily funded company that recently added a debt facility on top of a long equity history.
The latest round is not the company's stage. Debt, secondary sales, corporate rounds and convertible notes all show up as "latest" and none of them describes where a company sits in its lifecycle. A scoring rule keyed on that single field puts this company in the wrong bucket, and nothing in the response warns you.
Three more limits worth knowing before you build on this:
No per-round detail. You get a total and a count, not a table. Which investor led which round is a database question and this is a lookup.
Cumulative totals include everything. Debt and equity land in the same figure, so "raised" is not the same as "raised in equity", and comparisons between companies with different capital structures are not like for like.
Recency is not guaranteed. The date field says when the last observed round was, not when the last round happened. A company that raised last week may not show it yet, and the response does not distinguish "no round" from "no round we know about".
The working rule: use these fields to segment and prioritise, not to state facts about a company in a document someone will act on. If a number is going in front of an investment committee, buy the database.
📖 See also the provider comparison, where we measured a company record whose self-reported size band disagreed with its counted headcount.
How to use funding as a trigger without a database
The reason anyone wants this data is timing, and timing does not need a rounds table.
Score on the stage list, not the latest stage. A company whose funding_stages ends at seed is early and buys differently from one that has raised through Series D, and that read survives whatever the most recent instrument happened to be. This is the fix for the trap above, expressed as a rule.
Watch the date, not the total. last_funding_date moving is the event. The cumulative figure barely changes what you do; a round two weeks old changes who picks up the phone. Pair the lookup with a news watch on the same company and the announcement usually arrives before the enrichment record updates.
Combine with headcount, or you will misread the signal. Money raised without hiring is a different situation from money raised with a hiring spree. The same record carries employee_count_by_country, and postings data adds the direction of travel: we covered reading hiring as a buying signal separately.
Resolve first, always. Funding fields hang off a company, and a company hangs off a resolved domain. That step is free, and getting it wrong attaches one company's funding history to another's name. The resolution guide covers the ambiguity cases.
For the cost comparison against a firmographics-only provider, we priced the same job across two vendors previously, and for the wider question of leaving an enrichment subscription, that account is here.
When do you actually need Crunchbase or PitchBook?
Four cases, and they are common.
You are querying the market, not a list. "Show me every company that raised a Series A in this sector in the last six months" is a database query. There is no enrichment call that answers it, and framing it as one produces a worse version of the wrong thing.
You need round-level detail. Investors, lead investors, valuations, terms. That data is licensed, expensively, and it is the product these vendors actually sell.
You need it defensible. Diligence, board material, an investment memo. A cumulative figure from an enrichment API is a segmentation signal, not a citation, and the difference matters when someone asks where the number came from.
Your team lives in a UI. Analysts browsing, saving searches, sharing lists. We ship an API and a CLI.
The honest split: buy the database when funding data is the product you are working on, and buy calls when it is one attribute on a list you are prioritising. Most engineering-led GTM work is the second, and most investment work is the first.
Which endpoint should I use for which job?
| Job | Endpoint | Takes | Billing shape |
|---|---|---|---|
| Funding fields on a known company | pdl /v5/company/enrich | Website, name, LinkedIn URL | Per call |
| Firmographics plus assessment | akta /v1/company/enrichment | Domain | Per result |
| Resolve a name to a company first | akta /v1/company/search | Name or website | Free per call |
| Funding and launch news over time | akta /v1/news | Company | Per result plus flat fee |
| The company's own announcement | context.dev /web/scrape/markdown | URL | Per call |
Verified present on 2026-08-17 with monid discover. The billing column gives the shape rather than a figure, because figures move and monid inspect prints the current one for free.
The row worth pairing with the first: a news endpoint watching a resolved company catches the round when it is announced, which is the signal an annual snapshot misses by up to a year.
Conclusion
There is a Crunchbase alternative for one of the two jobs people use Crunchbase for. Funding fields attached to companies you already have: yes, per call, alongside the firmographics you were fetching anyway. A queryable database of rounds and investors: no, and any vendor claiming otherwise is selling you a lookup with a search box on it.
Two things matter more than the choice. latest_funding_stage is not the company's stage, and a scoring rule that treats it as one will file a Series H company as distressed the month it takes on debt. Read it with the stage list, always. And a cumulative total mixes debt with equity, so it ranks companies by capital raised rather than by anything about the business.
Start with the free part: monid inspect shows the full field list without spending, and resolution from a company name costs nothing, so you can build the domain list before deciding what to enrich. Begin at monid.ai.
FAQ
Can I get investor names and round sizes this way?
No. The enrichment response carries a cumulative total, a count of rounds, the stage types and the last date, and nothing about who invested or how much per round. That is the licensed part of this market and it is what the database vendors sell. If you need it, buy it; a lookup endpoint returning it cheaply would be the surprising thing, not the missing one.
How current is the funding data?
Current as of the last observation, which is not the same as current. The date field tells you when the most recent round it knows about happened, and there is no field distinguishing "this company has not raised" from "we have not seen a round". For anything time-sensitive, pair the lookup with a news endpoint on the same company: an announcement shows up there first.
Does total funding include debt?
Yes, and that is the trap. The cumulative figure sums whatever rounds are recorded, debt facilities and convertible notes included, so two companies with the same total can have very different equity stories. If your model cares about the distinction, use the stage list to see what kinds of round make up the history rather than treating the total as an equity figure.
Is this cheaper than a Crunchbase seat?
For the lookup job, yes, and the comparison is not really about price. A seat buys browsing, saved searches and a UI a person opens; a call buys one company's fields inside a pipeline. If nobody on your team would open the UI, you are paying for the half you do not use. If somebody would, the API does not replace them.
Last updated August 2026.

