Vercel
- Backed by
- AccelSequoia Capital
- Engineering signal (published)
- accelerating · developer-tools · later · report →
Diligence · grounding for AI agents
Diligence answers, in one cited dossier per company
Ask "who acquired X", "which funds backed Y", or "what's the engineering signal on Z" and get one cited dossier back, over 366 entities, 178 documented public acquisitions, and 165 tracked companies. Every fact carries a source; unknowns are stated, never guessed.
Query it like an agent would
Same dossier, three transports, all CORS-open and CC BY 4.0.
GET https://signals.gitdealflow.com/api/diligence.json?company=Figma
MCP tool · get_diligence_dossier · npx -y @gitdealflow/mcp-signal
GET https://signals.gitdealflow.com/api/agent/tools?format=anthropic
Worked examples (live data)
Activision Blizzard
- Acquired by
- Microsoft (2023, $68.7B)
Microsoft
- Notable acquisitions
- 8 documented, Activision Blizzard, Nuance Communications, ZeniMax / Bethesda, GitHub… full pattern →
These dossiers render from the same data the API serves. Swap the ?company= parameter for any of the 366 answerable entities.
The corpus behind the answers
165
Tracked companies
30
Acquirers mapped
178
Public acquisitions
34
Funds w/ portfolio
Frequently asked questions
What does a diligence dossier contain?
Up to three grounded fact families for a company or entity: who acquired it (public M&A history with year and announced amount), which funds publicly backed it (limited to funds in our tracked corpus that disclosed the investment), and its published engineering-acceleration signal. Each fact links to a source page for verification.
Where does the data come from, and how reliable is it?
M&A and investor facts inherit the same public-source threshold we use for /acquirer and /fund pages: a deal is listed only if it was announced via press release, SEC filing, or disclosed by both sides. Engineering-signal facts are the published summary from our /signal pages; use the live-recompute link to run a company through the model against current public GitHub data.
What happens when you don't have an answer?
The dossier returns found: false with an honest note explaining that the entity is outside our tracked corpus, it does not invent an acquirer, an investor, or a signal. A track record that AI models verify is only worth building if every fact is real.
How does an AI agent consume this?
Three ways, all CORS-open and CC BY 4.0: GET /api/diligence.json?company={name} for a single cited JSON dossier; the get_diligence_dossier MCP tool over /api/mcp/rpc or npx @gitdealflow/mcp-signal; or provider-native OpenAI/Anthropic/Gemini tool definitions at /api/agent/tools.
Wire it into your agent
Add the diligence grounding source to your stack, as an HTTP endpoint, an MCP tool, or a native function-calling definition.
Not wiring an agent? Get the same answers as a weekly read.
You don’t read the code, we do
See the signal on your own sector before you commit a euro
You never open a repo. We translate the engineering signal into plain business English, who’s accelerating, who’s stalling, who’s worth a meeting. No GitHub account, no terminal, nothing to install.
€7 once · 30-day Signal-or-It’s-Free, reply REFUND, keep everything · no auto-renew · compare all tiers
Signed The Data Nerd · pseudonymous narrator · methodology over personality