# NEA Portfolio Report — Filtered VC Target Book (`nexgenwatch/nea-portfolio-report`) Actor

Filtered, normalized target book of New Enterprise Associates' portfolio, with coverage stated and a source link per company.

- **URL**: https://apify.com/nexgenwatch/nea-portfolio-report.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 portfolio company records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## NEA Portfolio Report

Build a **filtered, normalized target book of New Enterprise Associates' portfolio**, with a
link to NEA's own page behind every single company.

Built for deal sourcing, competitive mapping and BD teams who need a workable list instead of
a wall of logos.

### Coverage is the headline, not the footnote

This actor sells a filtered book, so the worst thing it can do is hand you a short list that
reads like a complete one. Every report states, in the record **and** on the first line of the
brief:

```
universe_total       914     companies NEA publishes
companies_examined   150     companies this run actually read
coverage_complete    false
coverage_caveat      "maxCompanies=150 bounded the sweep to the first 150 of 914
                      companies in sitemap order"
```

**A company missing from a partial book has not been ruled out — it was never read.** Raise
`maxCompanies` toward 914 for a complete book; budget about a minute per 120 companies.

Honouring your page budget perfectly still does not count as coverage. Coverage is measured
against NEA's portfolio, not against the run's own limit.

### Two things measured live that a naive read gets wrong

#### 1. `nea.com/portfolio` is not the portfolio

The page the phrase "scrape the portfolio" points at is a **30-logo featured carousel**. It
carries no company name in text, no sector, no stage and no status — nothing to filter on.

The universe comes from **the site's own declared sitemap**: 914 `/portfolio/` URLs out of
1,333, measured 2026-07-31. Each company's detail page carries the fields that make a target
book: sectors, first-invested year, stage, company status and NEA's own one-line description.

#### 2. Values must be sliced between labels, never by token offset

The detail page renders as a flat label/value stream:

```
Sectors | Technology | Enterprise | First Invested | 2014 | Early
| Company Status | Private | Associated Team | ... | Theme | ... | Website
```

Two traps, both measured on real pages and both closed:

- **A current holding has no status detail.** The token after the status is the *next label*.
  An offset parser reports every live company as `status_detail = "Associated Team"`.
- **An exited company's block is the last one on the page.** `/portfolio/polyserve` has no
  team, theme or website section, so slicing "to the next label" ran the status detail into
  the site footer: *"Acquired by Hewlett Packard © NEA, 2026 Follow us on social media…"* —
  boilerplate glued onto a real field, on exactly the exited companies a buyer cares most
  about.

Both are asserted against **verbatim excerpts of the live pages** in the test suite.

### Nothing is inferred

`status` and `stage` are carried **verbatim** from NEA's page. This actor never decides that a
company exited, failed, or is still held, and it never scores or ranks anyone. It reports what
NEA publishes and links to it.

NEA's published portfolio is the whole of this report. It is not a complete record of NEA's
investments — a firm publishes what it chooses to. This is not investment advice.

### Filters

| filter | what it does |
|---|---|
| `sectors` | keep companies tagged with any of these, e.g. Healthcare, Technology |
| `themes` | keep companies tagged with any of these, e.g. AI, Infrastructure |
| `stages` | stage at first investment, e.g. Seed, Early, Growth |
| `statuses` | company status as NEA publishes it, e.g. Private, Acquired |
| `firstInvestedFrom` / `firstInvestedTo` | year range of NEA's first investment |
| `nameContains` | free text across company name and NEA's description |
| `maxCompanies` | how much of the 914 to read — **default 150, a partial sweep** |

Filtering runs here, over parsed fields, because the source offers no server-side filter at
all. Every parameter therefore provably changes the result set, proven control-vs-test in the
suite — none of them can be quietly discarded by the site.

Each report also returns `vocabularies_in_examined_set`: the sectors, stages and statuses
**counted from the companies this run actually read**, not from a hard-coded list.

### Output

- one `portfolio_company` record per match — name, description, sectors, themes, first
  invested year, stage, status, status detail, and the NEA URL it came from
- one `portfolio_report` record — the filter, the coverage numbers, the vocabularies
- one `source_receipt` — terminal, HTTP statuses, request counts, pacing
- a rendered markdown brief in the key-value store

### Reading policy

`nea.com/robots.txt` reads `User-agent: * / Allow: /` with no crawl-delay. This actor paces
itself at **2 requests/second** anyway, with a contact User-Agent. **The rate is not an input**
— a buyer cannot dial it up.

### Pricing

| Event | FREE | BRONZE | SILVER | GOLD+ |
|---|---|---|---|---|
| Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 |
| Portfolio company record (`portfolio-company-record`) | $0.05 | $0.045 | $0.04 | $0.0335 |

Prices are the filed pay-per-event amounts per plan tier (PLATINUM/DIAMOND match GOLD). Blocked and refused runs do not intentionally charge value events.

# Actor input Schema

## `sectors` (type: `array`):

Keep only companies NEA tags with at least one of these sectors, e.g. Healthcare, Technology, Enterprise, Consumer, Life Sciences. Matching is case-insensitive. Leave empty for every sector. The exact vocabulary the run actually saw is reported back in vocabularies\_in\_examined\_set.

## `themes` (type: `array`):

Keep only companies NEA tags with at least one of these themes, e.g. AI, Infrastructure. Leave empty for every theme.

## `stages` (type: `array`):

Keep only these stages, e.g. Seed, Early, Growth, Public/PIPES. Leave empty for every stage.

## `statuses` (type: `array`):

Keep only these statuses as NEA publishes them, e.g. Private, Acquired, IPO/Acquired. Carried verbatim from NEA's page — this actor never decides that a company exited or failed. Leave empty for every status.

## `nameContains` (type: `string`):

Free text kept only if it appears in the company name or NEA's own one-line description.

## `firstInvestedFrom` (type: `integer`):

Earliest year of NEA's first investment, inclusive. Companies with no published year are excluded when this is set.

## `firstInvestedTo` (type: `integer`):

Latest year of NEA's first investment, inclusive. Companies with no published year are excluded when this is set.

## `maxCompanies` (type: `integer`):

The sweep reads this many companies from NEA's sitemap, in sitemap order, at 2 requests/second. NEA published 914 companies when this build was measured, so the default of 150 is a PARTIAL sweep and the report says so on its first line. Raise it toward 914 for a complete book — expect roughly one minute per 120 companies.

## Actor input object example

```json
{
  "sectors": [
    "Healthcare"
  ],
  "maxCompanies": 25
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "sectors": [
        "Healthcare"
    ],
    "maxCompanies": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/nea-portfolio-report").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "sectors": ["Healthcare"],
    "maxCompanies": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/nea-portfolio-report").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "sectors": [
    "Healthcare"
  ],
  "maxCompanies": 25
}' |
apify call nexgenwatch/nea-portfolio-report --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/nea-portfolio-report"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/l2bqtLkRNaJdfQ9gy/builds/k9nEaXq4fYK1wn7AR/openapi.json