GV
GV (formerly Google Ventures) is the venture capital arm of Alphabet, founded in 2009 by Bill Maris and headquartered in the San Francisco Bay Area with additional offices in New York, Cambridge, and London. With Alphabet as its sole limited partner, GV operates with the reliability of a single LP, the autonomy of a traditional venture firm, and deep technical expertise, investing from seed through growth stage across technology and life sciences. Its focus areas span AI, enterprise, consumer, frontier tech, and life sciences, with a heavy recent emphasis on the AI frontier, from applications and developer tools to infrastructure and healthcare. GV manages over $13 billion in assets and supports roughly 400 active portfolio companies across North America, Europe, and Israel. The firm has backed notable companies including Uber, Slack, GitLab, Nest, Flatiron Health, Lemonade, Vercel, Isomorphic Labs, and insitro, with a track record of more than 80 IPOs and 230+ M&A exits.
GV has 657 portfolio companies tracked on the APIs.io network, of which 192 (29%) publish APIs indexed here. The remaining 464 are tracked as profiles without a published API on the network.
Its highest-rated API providers on the network are HubSpot *, Harness, Plaid, Stripe, GitLab.
Portfolio on the Network
Portfolio companies that publish APIs indexed on APIs.io, grouped by their API Evangelist rating. Exemplar and Strong are expanded by default.
Exemplar 19 Complete, well-documented, and agent-ready
Strong 26 Solid coverage with minor gaps
Developing 52 Usable, with meaningful gaps to close
Thin 57 Limited public surface area
Emerging 35 Early or largely undocumented
Minimal 3 Almost no public developer surface
Rest of Portfolio
1 further portfolio companies that don’t yet have a provider page on the network.
Scroll for all 1
Properties
Portfolio
Where the firm publishes its investments
Firm
The firm itself
Cohort brief
Auto-generatedThe 529 portfolio companies with APIs in the catalog, backed by GV, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 26.3 | 26.5 | -0.2 | 529 |
| Operational Transparency | 12.9 | 13.2 | -0.3 | 529 |
| Discoverability | 56.1 | 58 | -1.9 | 529 |
| Contract Governance | 5 | 7 | -2 | 529 |
| Contract Quality | 14.2 | 17.7 | -3.5 | 529 |
| Developer Ergonomics | 20.2 | 23.8 | -3.6 | 529 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 15% | 15% | 0 |
| MCP server (first-party) | 14% | 13% | +1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 12% | 0 |
| Security | 98% | 98% | 0 |
| Arazzo workflows | 1% | 2% | -1 |
| Governance rules | 11% | 18% | -7 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 HubSpot
- 2 Harness
- 3 Plaid
- 4 Stripe
- 5 GitLab
- 6 Snyk
- 7 Optimizely
- 8 Bugsnag
- 9 ThousandEyes
- 10 Slack
- 1 Scope3 {"score" => 64.3, "band" => "agent-native"}
- 2 Harness {"score" => 63.2, "band" => "agent-native"}
- 3 Optimizely {"score" => 62.9, "band" => "agent-ready"}
- 4 Recorded Future {"score" => 58.8, "band" => "agent-ready"}
- 5 Stripe {"score" => 58.5, "band" => "agent-native"}
- 6 PostHog {"score" => 57.3, "band" => "agent-ready"}
- 7 Chronosphere {"score" => 55.4, "band" => "agent-native"}
- 8 ThousandEyes {"score" => 55.3, "band" => "agent-ready"}
- 9 Bugsnag {"score" => 53.1, "band" => "agent-ready"}
- 10 Roboflow {"score" => 52.8, "band" => "agent-ready"}
Coverage caveat. 478 of 529 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 2 November 2026, across 37080 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Source (apis.yml)
Work with this as data
Every firm here is available over the APIs.io API and to AI agents over MCP.