# Climate-Tech Funding Leads (`nexgenwatch/climatetech-funding-leads`) Actor

Qualified Climate-Tech startup funding leads from Crunchbase News + TechCrunch venture RSS: each a single funded company with round/amount, announced date, source article, and a resolved company domain. Round-ups and sector-mention-only items are rejected; one charge per qualified lead.

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

## Pricing

from $33.50 / 1,000 qualified funding leads

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/platform/actors/running/actors-in-store#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

## Climate-Tech Funding Leads

Qualified, domain-resolved **funding leads** for climate & clean energy (companies tagged clean-tech / climate / energy in the feed), built live from two public,
logged-out RSS sources: **Crunchbase News** (`https://news.crunchbase.com/feed/`) and
**TechCrunch venture** (`https://techcrunch.com/category/venture/feed/`). Both feed paths
are robots-allowed; the actor honours each source's robots.txt.

Difference from the anchor funding tracker: this returns ONE sector, qualified and domain-resolved with the funding sentence as evidence — generic companies that merely mention the sector are rejected and never bill.

### What qualifies as a lead

One `qualified_funding_lead` is emitted only when ALL of these are present — otherwise the
item is rejected and never billed:

- **company** — a single funded company (VC-fund closes, weekly round-ups, analysis pieces,
  and founder/team-subject headlines are rejected)
- **round / amount evidence** — a round type and/or a funding amount in the headline
- **announced date** — the feed publication date
- **source URL** — the article the lead came from
- **resolved company domain** — the company's website, resolved *article-authoritatively*:
  the domain the publisher itself hyperlinked, matched to the company name and verified live
  and non-parked. Domains are never guessed; if none can be resolved, the lead is dropped.
- **sector match** — the sector present in the item's own feed **categories** (the
  publisher's structured tag), not merely mentioned in prose

Each record carries the **funding sentence as evidence**, the resolved `company_domain`, the
`domain_confidence`, the round, the amount, the announced date, and the source URL.

### How it behaves

A total source outage (all feeds fail to load/parse) stops the run loudly and charges
nothing. When the feeds are reachable but no item qualifies for this sector, that is a
genuine empty result: it succeeds and bills nothing. `maxRecords` caps the count (a buyer
bound, never a block).

### Pricing

| Event | FREE | BRONZE | SILVER | GOLD+ |
|---|---|---|---|---|
| `apify-actor-start` (one-time actor start) | $0.02 | $0.02 | $0.02 | $0.02 |
| `qualified_funding_lead` (per qualified, domain-resolved lead) | $0.05 | $0.045 | $0.04 | $0.0335 |

You are charged once per qualified lead delivered. The one-time start fee is $0.02. A sector
match with no resolvable domain, a duplicate domain, a non-qualifying item, and a
genuine-empty result all bill nothing; an outage charges nothing.

# Actor input Schema

## `maxRecords` (type: `integer`):

Upper bound on qualified leads delivered this run (a buyer-requested cap). Leave empty for the built-in ceiling.

## `userAgent` (type: `string`):

Optional override for the identified contact User-Agent used for feed and verification fetches.

## Actor input object example

```json
{
  "maxRecords": 100
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/climatetech-funding-leads").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/climatetech-funding-leads").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{}' |
apify call nexgenwatch/climatetech-funding-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=nexgenwatch/climatetech-funding-leads",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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