# US Grants.gov Federal Funding Opportunity Change Watch (`nexgenwatch/us-grants-opportunity-change-watch`) Actor

Changes to federal opportunities on the official Grants.gov feed — new, updated and closing, with the fields changed. No API key; pay per change.

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

## Pricing

from $67.00 / 1,000 source checks

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

## US Grants.gov Federal Funding Opportunity Change Watch

```
    Federal funding opportunities on Grants.gov as they move: new postings, a forecast turning into a live posting, deadline amendments, changes to the award ceiling / floor / estimated funding / number of awards, eligibility changes, cancellations and withdrawals, agency or CFDA programme changes, and changes to the attached documents. Each delta is typed, and you choose which types you want. Keyed on the Grants.gov opportunity id.

    ## Source
    Grants.gov public Search2 and FetchOpportunity APIs (public, logged-out)
    - https://api.grants.gov/v1/api/search2
```

- https://api.grants.gov/v1/api/fetchOpportunity

  ```
    Public, logged-out only — no API key, login, cookie or CAPTCHA.

    ## The eight delta types
    | value | fires when |
    |---|---|
    | `new-opportunity` | an opportunity appears in the watched set |
    | `forecast-to-posted` | status moves `forecasted` → `posted` |
    | `deadline-amendment` | the close date or synopsis response date moves |
    | `funding-range-change` | award ceiling, floor, estimated funding, number of awards or cost sharing changes |
    | `eligibility-change` | the set of eligible applicant types changes |
    | `opportunity-cancellation` | status moves into closed/archived/withdrawn, or the record is delisted |
    | `agency-program` | the agency, agency code or CFDA programme list changes |
    | `opportunity-document-change` | the attached document set changes |

    Leave `delta_types` empty for all eight. Every emitted delta carries `delta_kinds`
    naming which ones it satisfied.

    The last three need a per-opportunity detail read. Selecting any of them narrows
    the watched set to `max_detail_reads` opportunities, newest first, and uses a
    separate baseline — so a list-mode baseline is never diffed against a detail-mode
    read.

    ## Pricing (staging state)
    | Event | Price (FREE tier) |
    |---|---|
    | Actor start (`apify-actor-start`) | $0.02 one-time |
    | Source check (`source-check`) | $0.10 |

    `source-check` ladder, GOLD-floored: **$0.10 / $0.09 / $0.08 / $0.067**.
    Charged once per run after the source enumeration terminates — seed runs and
    genuine-zero runs included. It is **not** charged when the source refused the read.

    The per-delta value event (`grant-opportunity-delta`) is **not priced yet**. Deltas are
    emitted unbilled until the ratified sheet is filed, and nothing is published first.

    ## Snapshot mode is a PREVIEW
    `watch_mode: false` returns at most **25 records**, hard-capped in code, labeled
    `output_mode: "preview"`. This actor sells change detection, not bulk export.

    ## Watch semantics
    The first watch run stores a private baseline and emits **zero** deltas. Billed
    deltas are capped at 500 per run; the overflow is a named PARTIAL withholding,
    never billed, and re-detected next run. When a read is truncated, `REMOVED` is
    suppressed rather than reported as a cancellation.

    ## Terminal states
    `NORMAL` · `SUCCEEDED-0: GENUINE_EMPTY` · `SUCCEEDED-0` (no change) · `PARTIAL` · `BLOCKED`.
    A zero with no evidence FAILS loud rather than exiting 0 quietly.
  ```

### Pricing

| Event | FREE | BRONZE | SILVER | GOLD+ |
|---|---|---|---|---|
| Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 |
| Source check (`source-check`) | $0.10 | $0.09 | $0.08 | $0.067 |

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

## `delta_types` (type: `array`):

Which changes to report. Leave empty for all eight. Values: new-opportunity, forecast-to-posted, deadline-amendment, funding-range-change, eligibility-change, opportunity-cancellation, agency-program, opportunity-document-change. The last three of those need per-opportunity detail reads, which narrows the watched set to the newest N.

## `opp_statuses` (type: `string`):

Pipe-separated Grants.gov statuses. Keeping forecasted and posted together is what makes a forecast-to-posted transition visible as a change rather than a disappearance.

## `keyword` (type: `string`):

Optional free-text term passed to the Grants.gov search.

## `agency_code` (type: `string`):

Optional agency filter, e.g. HHS-NIH, DOI-NPS, USDA-NIFA.

## `max_items` (type: `integer`):

Hard cap on opportunities watched (bounds runtime).

## `max_detail_reads` (type: `integer`):

Only used when a detail-backed delta type is selected. Caps the per-opportunity detail requests, and the watched set is narrowed to exactly that many so every baselined record carries the same fields.

## `watch_mode` (type: `boolean`):

First run seeds a private baseline and emits ZERO deltas.

## `baseline_id` (type: `string`):

Names the private baseline so several watches can run side by side.

## Actor input object example

```json
{
  "delta_types": [
    "new-opportunity",
    "deadline-amendment"
  ],
  "opp_statuses": "forecasted|posted",
  "keyword": "",
  "agency_code": "",
  "max_items": 50,
  "max_detail_reads": 20,
  "watch_mode": true,
  "baseline_id": "default"
}
```

# 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 = {
    "delta_types": [
        "new-opportunity",
        "deadline-amendment"
    ],
    "opp_statuses": "forecasted|posted",
    "keyword": "",
    "agency_code": "",
    "max_items": 50,
    "max_detail_reads": 20,
    "watch_mode": false,
    "baseline_id": "default"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/us-grants-opportunity-change-watch").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 = {
    "delta_types": [
        "new-opportunity",
        "deadline-amendment",
    ],
    "opp_statuses": "forecasted|posted",
    "keyword": "",
    "agency_code": "",
    "max_items": 50,
    "max_detail_reads": 20,
    "watch_mode": False,
    "baseline_id": "default",
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/us-grants-opportunity-change-watch").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 '{
  "delta_types": [
    "new-opportunity",
    "deadline-amendment"
  ],
  "opp_statuses": "forecasted|posted",
  "keyword": "",
  "agency_code": "",
  "max_items": 50,
  "max_detail_reads": 20,
  "watch_mode": false,
  "baseline_id": "default"
}' |
apify call nexgenwatch/us-grants-opportunity-change-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/us-grants-opportunity-change-watch"
        }
    }
}

```

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/CG6ByhrTBS6n4uqhi/builds/Ibcyyqr4SarCkvYwm/openapi.json