Crunchbase Pro or Crunchbase by the Call: What Each Actually Returns

Copy this line to your agent to look up a company's funding rounds by the call.

set up https://monid.ai/SKILL.md and use crunchbase /search_organizations then /get_company_funding_rounds

On 2026-09-16 we asked the Crunchbase endpoints about Stripe. The search matched sixty-nine organisations, including a fashion retailer and a chai company. The profile returned seven fields and no funding total. The rounds endpoint returned twenty-five rounds, each with a type and none with an amount or a date. Everything the Pro seat is sold on was exactly what did not come back, and that is the cleanest description of the split we have found. This guide runs through Monid, the OpenRouter for agent tools.

What does Crunchbase Pro give you that the API does not?

The numbers, the interface, and the ability to ask the database a question rather than look up a company you already know.

What Pro is

A seat-based subscription to Crunchbase's interface: advanced search across the whole database, saved searches and alerts, the full funding record with amounts, dates, valuations and investors, and exports. It is priced per seat, annually, and it is a product a person opens.

What the per-call tier is

Three lookup endpoints over a subset of the same records: resolve a name to an organisation, read an organisation's profile, list its funding rounds. Each bills per call and returns a fixed field set. It is a product a pipeline calls.

The line between them, measured

We drew it by calling the per-call tier on a company whose funding history is as public as any company's. The fields that came back are the API tier. The fields that did not are what the seat is for. The next section is that list.

The honest framing

If your question is "show me every Series B in fintech this quarter", that is a database query and only the seat answers it. If your question is "has this company I already have raised, and how many times", the per-call tier answers it for cents. Most engineering-led use is the second; most analyst use is the first. The same seat-versus-call split for a different vendor is in the PitchBook pricing guide.

📖 See also Startup Funding Data by API: Crunchbase Alternatives That Bill Per Call

What do the Crunchbase endpoints actually return?

Seven fields for an organisation, three for a round, and the same seven whether you search or read the profile.

The search

crunchbase/search_organizations for Stripe: count: 69, fifteen returned, 21 seconds. The first five:

stripe                Stripe is a financial technology company that provides online payment…
stripe-stare          Stripe & Stare is an online retailer of fashion, sleepwear, and underwear…
recko-io              Recko is a financial operations platform for internet companies…
one-stripe-chai-co    One Stripe Chai Co. is a beverage brand that offers small-batch masala…
stripe-capital        Stripe Capital provides flexible financing solutions for business growth…

Sixty-nine matches for one of the most distinctive company names in technology. Name resolution is a real step here, as it is on every company-lookup endpoint we have measured, and the second match is a lingerie retailer.

Each entity carried seven property keys: identifier, short_description, rank_org, categories, location_identifiers, num_employees_enum, status.

The profile

crunchbase/get_organization_profile for slug stripe, 18 seconds:

{
  "identifier": { "permalink": "stripe", "value": "Stripe" },
  "short_description": "Stripe is a financial technology company…",
  "rank_org": "…",
  "categories": [ "…" ],
  "location_identifiers": [ "…" ],
  "num_employees_enum": "c_05001_10000",
  "status": "operating"
}

Seven keys. The same seven the search returned. We checked for twelve funding and financial fields by name: funding_total, last_funding_at, num_funding_rounds, last_funding_type, last_equity_funding_total, valuation, num_investors, founded_on, revenue_range, ipo_status, last_funding_total. Every one was absent. On this tier, the profile call is not a deeper record than the search hit; it is the same record fetched by slug instead of by query.

The rounds

crunchbase/get_company_funding_rounds with the uuid from the search, limit 10: count: 25, ten returned, 59 seconds. Each round:

{
  "identifier": { "value": "Series H - Stripe" },
  "investment_type": "series_h",
  "funded_organization_identifier": { "value": "Stripe" }
}

Three keys. The types on the page: five secondary_market, two series_c, one each of series_b, series_h, series_i. No money_raised, no announced_on, no valuation, no investor.

What that adds up to

You can learn that Stripe exists, what it does, its size band, and that it has raised twenty-five times including five secondary transactions and rounds up to Series I. You cannot learn how much, when, or from whom. That is the shape of a funding history without any of its size, which is exactly the finding from a different company on 2026-09-07, and it has not moved.

How can I get Crunchbase data through an API?

Three calls, resolve then read, and budget a minute per call rather than a second.

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-api-key> -l main

Step 1. Resolve the name

What it does. Turns a company name into a uuid and a permalink, which the other two calls need.

The endpoints. crunchbase/search_organizations, billed per call, takes query.

The call.

monid run -p crunchbase -e /search_organizations --query '{"query": "Stripe"}'

What comes back. count and a page of entities, each with identifier.uuid, identifier.permalink and the seven fields. Store both identifiers: the profile wants the permalink, the rounds want the uuid.

What it costs. A couple of cents per call. Current figures at monid.ai/tools.

Step 2. Read the profile if you need the size band

The endpoints. crunchbase/get_organization_profile, per call, takes slug.

monid run -p crunchbase -e /get_organization_profile --query '{"slug": "stripe"}'

What comes back. The same seven fields as the search hit. If you already have the search row, this call adds nothing on the current tier, and skipping it saves eighteen seconds and a charge.

Step 3. List the rounds

The endpoints. crunchbase/get_company_funding_rounds, per call, takes org_uuid and limit.

monid run -p crunchbase -e /get_company_funding_rounds --query '{"org_uuid": "<uuid>", "limit": 25}'

What comes back. count and a page of typed rounds. Read count, not the array length: ours said 25 and returned the 10 we asked for.

What it costs. Per call. And nearly a minute of wall clock, which is the next thing to design around.

📖 See also Turn a Domain Into Full Company Firmographics in One Call

Why does a funding round come back without a number?

Because the amount is the licensed field, and the per-call tier is drawn exactly around it.

What the round record is

A typed event. Series H - Stripe, secondary_market, Stripe. It tells you a thing happened and what kind of thing it was. It does not tell you its size, its date, its valuation or its participants, because those four fields are the ones a Pro seat exists to sell.

Why that is still useful

Twenty-five rounds including a Series I and five secondary-market transactions is a lot of information about a company's stage without a single dollar figure. A go-to-market motion that triggers on "recently raised" or "late stage" can run on this. A valuation model cannot. Deciding which of those you are building is the whole decision, and it is the same argument made about funding as a signal rather than a figure.

The latency is part of the design

Search took 21 seconds, the profile 18, the rounds 59. These are not interactive endpoints. A pipeline that resolves and reads a thousand companies overnight is the right shape; an agent answering a user's question while they wait is not, and for that job an enrichment endpoint that returns funding fields in a second, measured on the same company with 33 rounds and 14 stage types, is the better route even though it is a different provider's reconciliation of the same events.

The identifier hop

Search wants query, profile wants slug, rounds want org_uuid. Three sibling endpoints, three identifiers for one company, and every hop needs the previous response. That is the recurring tax noted on Ahrefs, on insider trading data and here.

Which endpoint should I use for which job?

Every row was verified with monid inspect on 2026-09-16. The table gives billing shape rather than figures, because shape drives design and current numbers live on monid.ai/tools.

The second row is in the table so you can see why not to call it. On this tier it returned the same seven fields as a search hit, eighteen seconds later, for another charge.

When is the Pro seat the right purchase?

Four cases, and they are common.

You query the market. "Every Series A in this sector since January" is a database question. No lookup endpoint answers it, and the seat's advanced search is the product built for it.

You need amounts, dates, valuations or investors. None of the four came back on any of the three calls. If a number is going into a model or a memo, this is the licensed half and you should pay for it.

A person browses. Saved searches, alerts, list building, export to a spreadsheet. That is what an interface is for and an API does not replace the person's morning.

You need it now. Sixty seconds for a rounds call is fine for a nightly job and unusable in a conversation. If latency matters and the fields you need are the ones that do come back, an enrichment endpoint on another provider returns them in a second.

And the disclosure: this is Monid's blog and we resell the per-call endpoints. The central measurement here is that they return the shape of a funding history and none of its size, which is not a flattering thing to say about what we sell, and the recommendation to skip one of our three calls is a recommendation to spend less.

Conclusion

Crunchbase Pro and Crunchbase by the call are the same database at two depths, and the line between them fell exactly where the seat's value is: on 2026-09-16 the per-call tier returned sixty-nine name matches, a seven-field profile and twenty-five typed rounds for Stripe, and not one amount, date, valuation or investor. The shape of the company and its history, without the size.

What matters more than which tier is which question you are asking. A lookup on a company you already have, for a signal about its stage, is the API and it costs cents. A query across the market, for numbers you will act on, is the seat. And on the API tier, skip the profile call: it returned nothing the search had not, eighteen seconds later.

Free next step: run monid inspect -p crunchbase -e /get_organization_profile and read the field list before writing any schema against it, then search one company you know well and count the matches. Start at monid.ai.

FAQ

Last updated September 2026.