Crunchbase
Look up companies, people and funding rounds from Crunchbase's private-market dataset.
About
Crunchbase ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.crunchbase- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Analytics & BI
Overview
Crunchbase licenses its private-market dataset — company profiles, funding history, investors and people — through a single read-only REST API, and this app puts that data into a workflow: autocomplete to resolve a fuzzy name into the exact entity a search or lookup needs, structured search across organizations, people and funding rounds with the same predicate/operator query language the Crunchbase UI itself uses, and direct entity lookups by UUID or permalink for enriching a record once you already know which one you want.
The API is licensed in tiers — Basic, Advanced and Enterprise — and higher tiers unlock more fields and endpoints on the same key; this app calls the same v4 surface regardless, so what actually comes back depends on the connected key’s package. Search bodies model Crunchbase’s own field_ids/query/order/predicate shape directly rather than flattening it into a fixed form, because the field and operator vocabulary is too large (93 organization fields, 20 operators) to model any other way without losing what makes the API useful.
Every write in this API is a no-op: Crunchbase’s REST API is read-only, so every action here is a read, a search, or an autocomplete.
Build with Crunchbase
Three routes to the same 7 actions. The Workflow tab is generated from Crunchbase's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Search Organizations
search-organizations Search Crunchbase organizations (companies, investors, schools).
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Crunchbase's real ids.
{
"manifestVersion": "2",
"name": "crunchbase-example",
"steps": [
{
"id": "autocomplete",
"uses": {
"app": "io.w6w.crunchbase",
"action": "autocomplete",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"query": "<query>"
}
}
]
}Here are some of the things you can do
-
Autocomplete
readautocomplete -
Get Funding Round
readget-funding-round -
Get Organization
readget-organization -
Get Person
readget-person -
Search Funding Rounds
searchsearch-funding-rounds
+2 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Crunchbase, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Crunchbase. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "autocomplete",
payload: {
query: "<value>",
// collectionIds: "<value>",
// limit: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action autocomplete --payload '{"query":"<value>"}'Give an AI agent Crunchbase — without giving it Crunchbase's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.crunchbase#autocomplete",
"input": {
"query": "<query>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Crunchbase connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Crunchbase's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Crunchbase itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Crunchbase declares its own checks, so its health is a property of the app rather than something the host guesses at.