Project A Portfolio Companies avatar

Project A Portfolio Companies

Pricing

from $33.50 / 1,000 portfolio company records

Go to Apify Store
Project A Portfolio Companies

Project A Portfolio Companies

One structured record per company in the Project A portfolio, read from the fund's own portfolio page (https://www.project-a.com/portfolio). Public, logged-out, robots-honoured.

Pricing

from $33.50 / 1,000 portfolio company records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

🏢 Project A Portfolio Companies

One structured record per company in the Project A portfolio, read from the fund's own portfolio page (https://www.project-a.com/portfolio). Public, logged-out, robots-honoured.

Difference: each record carries Project A's one-line description, investment stage, and status (Active/Exited) per company — not a bare name list.

Output is one portfolio_company row per result; billing is pay-per-event, the value event being one portfolio company record (a $0.02 start fee per run, then $0.05 per portfolio company record). Source: www.project-a.com.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out.

📊 Sample Output

Project A Portfolio Companies sample output — a table of real portfolio company record rows (name, description, stage, status) from run AQWI7ZdgQiQ2GBqHh on build 0.1.8

Real rows from run AQWI7ZdgQiQ2GBqHh on build 0.1.8 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

namedescriptionstagestatus
11xShaping the AI-first future of workPre-SeedActive
42mattersEuropean pioneer in mobile targeting dataSeedExited
ARX RoboticsUnmanned autonomous dual-use ground systemsPre-SeedActive
AlvinOperational data lineage platformSeries AActive
Amann GirrbachConnecting the dental worldActive
AmbossMedical knowledge you can rely onActive
AndercoreAI-powered industrial trade platformPre-SeedActive
AnylineDefining the future of mobile data captureSeries AActive

The run finished with the status message: CAPPED: delivered 10 of at least 113 unique companies (maxRecords=10) — a buyer bound, not an outage. portfolio_company billable=10

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • name (string/null) — e.g. 11x
  • canonical_url (string/null) — null in every sample row
  • company_website (string/null) — null in every sample row
  • description (string/null) — e.g. Shaping the AI-first future of work
  • stage (string/null) — e.g. Pre-Seed
  • status (string/null) — e.g. Active
  • source_url (string/null) — e.g. https://www.project-a.com/portfolio
  • record_type (string) — e.g. portfolio_company
  • source (string/null) — e.g. projecta-portfolio
  • observed_at (string/null) — e.g. 2026-09-17T17:45:03Z
  • sectors (array/null) — null in every sample row
  • sector (string/null) — null in every sample row
  • invested_year (string/null) — null in every sample row
  • region (string/null) — null in every sample row
  • country (string/null) — null in every sample row
  • hq_country (string/null) — null in every sample row
  • city (string/null) — null in every sample row
  • is_unicorn (boolean/null) — null in every sample row
  • terminal (string/null) — null in every sample row
  • pages_read (integer/null) — null in every sample row
  • raw_seen (integer/null) — null in every sample row
  • duplicates (integer/null) — null in every sample row
  • unique_found (integer/null) — null in every sample row
  • delivered (integer/null) — null in every sample row
  • leadership (string/null) — null in every sample row

What you get

One portfolio_company record per company, deduplicated, carrying the fund-specific dimensions the source publishes. Fields the source does not publish are honest null.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"pageUrls": [
"https://www.project-a.com/portfolio"
],
"maxRecords": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 10 × $0.05 portfolio_company_record = $0.52 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
"pageUrls": [
"https://www.project-a.com/portfolio"
],
"maxRecords": 5
}

Caps the run at 5 rows — about $0.27 on the Free tier ($0.02 start + 5 × $0.05).

3. A full-size run

{
"pageUrls": [
"https://www.project-a.com/portfolio"
],
"maxRecords": 2000
}

Up to 2000 rows (the schema default for maxRecords) — about $100.02 on the Free tier ($0.02 start + 2000 × $0.05) if the source has that many.

🧾 JSON sample record

One real record from run AQWI7ZdgQiQ2GBqHh, exactly as it lands in the dataset (emails masked, long text shortened):

{
"name": "11x",
"canonical_url": null,
"company_website": null,
"description": "Shaping the AI-first future of work",
"stage": "Pre-Seed",
"status": "Active",
"source_url": "https://www.project-a.com/portfolio",
"record_type": "portfolio_company",
"source": "projecta-portfolio",
"observed_at": "2026-09-17T17:45:03Z"
}

🔧 How it works

Source. The actor reads www.project-a.com — endpoints: https://www.project-a.com/portfolio. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each portfolio company record is charged at the moment it is pushed (portfolio_company_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Fetched only if robots allows. Outage/wall/redesign (zero cards on page 1) stops loudly, charges nothing. maxRecords caps the count.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Portfolio Company Record (portfolio_company_record)$0.05$0.04$0.04$0.03

Worked at the live Free-tier price:

  • 8 portfolio company records: $0.02 start + 8 × $0.05 = $0.42
  • 25 portfolio company records: $0.02 start + 25 × $0.05 = $1.27
  • 2000 portfolio company records: $0.02 start + 2000 × $0.05 = $100.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: CAPPED: delivered 10 of at least 113 unique companies (maxRecords=10) — a buyer bound, not an outage. portfolio_company billable=10. maxRecords is a hard ceiling on what is delivered and billed, never a target.

This actor reads public, logged-out pages and feeds published by www.project-a.com. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.project-a.com) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 2000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other VC portfolio company lists actors?
A: Same output shape and billing model; this one covers www.project-a.com. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.