Skip to main content

Discovery catalogue

The Discovery catalogue is Carta's shared, read-only market data on GPs, funds, LPs and LP commitments. It is the same for every organization and is not your organization's own records. Use it to find managers, compare funds and see which LPs back them.

The catalogue endpoints need LP Discovery to be enabled for your organization and an API key with the lp_discovery:read scope. Without LP Discovery every catalogue endpoint answers 404; without the scope it answers 403. The two endpoints that add an LP to your own records also need the matching module enabled and its write scope, listed below. The same data is available to AI tools as the Discovery catalogue tools.

Endpoints​

GP Discovery​

  • GET /v1/gp-discovery — Search GPs by name, strategy, region and size.
  • GET /v1/gp-discovery/fields — List the fields you can group, filter or measure.
  • POST /v1/gp-discovery/aggregate — Count GPs grouped by a field.
  • GET /v1/gp-discovery/{id} — Get one GP with its funds and the LPs backing it.
  • GET /v1/gp-discovery/{id}/peers — List the GPs most similar to one GP. Requires Discovery Phase 4.

Fund Discovery​

  • GET /v1/fund-discovery — Search funds by name, GP, vintage, strategy and returns.
  • GET /v1/fund-discovery/benchmarks — Get IRR percentiles by vintage year.
  • GET /v1/fund-discovery/fields — List the fields you can group, filter or measure.
  • POST /v1/fund-discovery/aggregate — Count funds grouped by a field.
  • GET /v1/fund-discovery/{id} — Get one fund with its managing GP and the LP-reported data points behind its figures.

LP Discovery​

  • GET /v1/lp-discovery — Search LPs by name, type, region, headquarters country and assets under management.
  • GET /v1/lp-discovery/facets — List the LP types, regions and headquarters countries in the catalogue, with counts.
  • GET /v1/lp-discovery/{id} — Get one LP profile.
  • GET /v1/lp-discovery/explorer/capital-map — See where institutional LP capital is concentrated, by LP type and region.
  • GET /v1/lp-discovery/fields — List the fields you can group, filter or measure.
  • POST /v1/lp-discovery/aggregate — Count LPs grouped by a field.
  • GET /v1/lp-discovery/{id}/allocations — List the GPs one LP invests with, or its commitments to one GP.
  • GET /v1/lp-discovery/commitments/fields — List the fields of LP commitments to funds.
  • POST /v1/lp-discovery/commitments/aggregate — Total LP commitments grouped by a field.

These two copy a catalogue LP into your own records, so they also need a module and a write scope:

  • POST /v1/lp-discovery/{id}/add-to-investors — Add the LP to your Investors. Also needs the Investors module and investors:write.
  • POST /v1/lp-discovery/{id}/add-to-fundraising — Add the LP to your Fundraising pipeline at the first stage. Also needs the Fundraising module and fundraising:write.

Fields and aggregates​

Each catalogue pairs a fields endpoint with an aggregate endpoint. Call fields first: it returns every field's id, type and description. Pass those ids to aggregate as group_by, in filters and as the metric. The fields endpoint lists fields, not their values. To see the values a field takes, aggregate with that field as group_by.

Things to know​

  • AUM can be estimated or missing. A GP's assets under management is flagged when it is an estimate, and some GPs have none. Totals and averages over it are approximate.
  • IRR and TVPI are medians of LP-reported data. A fund's figures are the median of the data points LPs reported for it, and benchmarks are percentiles over those medians. They are not official fund figures or industry benchmarks.
  • Commitment totals are partial. They cover only the commitments the catalogue tracks, so they are not a market total.