# NIH Research Funding Lead Monitor (`maydit/nih-research-funding-lead-monitor`) Actor

Find NIH-funded research by topic, organization and fiscal year. Export public institutional funding signals and track award or project changes without an API key.

- **URL**: https://apify.com/maydit/nih-research-funding-lead-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 saved observations

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

![NIH Research Funding Lead Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/nih-research-funding-lead-monitor-96797ad672fe.png)

## NIH Research Funding Lead Monitor

Find NIH-funded research by topic, organization and fiscal year. Export public institutional funding signals and track award or project changes without an API key.

Tie research topics and institution identity to properly labeled award amounts, then track exact application IDs without inventing buying intent.

### Start in under a minute

1. Run the prefilled three-record discovery example. No login or API key is needed.
2. Open the Dataset for source-linked records and RUN_REPORT for coverage and billing limits.
3. Reuse exact source IDs for a stable watchlist. Turn on comparison and keep the same snapshot name and inputs.

### Useful workflows

#### 1. Discover funded AI research

Find the first three public NIH projects with artificial intelligence in their titles.

```json
{
  "keyword": "artificial intelligence",
  "excludeSubprojects": true,
  "maxResults": 3
}
```

#### 2. Watch two research awards

Read two known application IDs with fiscal-year awards, project dates and institutional identity.

```json
{
  "applicationIds": [
    "11284471",
    "11331634"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "research-awards"
}
```

#### 3. Inspect one award before qualification

Export one exact public application without confusing its fiscal-year award with lifetime funding.

```json
{
  "applicationIds": [
    "11284471"
  ],
  "maxResults": 1,
  "comparePrevious": false
}
```

### What the output means

`applicationId` is the source application ID. `projectNumber` and `coreProjectNumber` retain grant context. `isSubproject` and `subprojectId` prevent a component award from silently looking like an independent parent budget. `awardAmountUsd`, `directCostUsd` and `indirectCostUsd` stay separate; missing values remain null. `isActive` is the source flag. Dates are source calendar dates, not guaranteed payment or buying dates. `abstractText` is limited to 4,000 characters. No award totals are calculated. `awardAmountUsdChange` is calculated only between the same application and fiscal year.

Each saved row includes a stable record ID, source link, observedAt, contentHash, comparisonStatus and changedFields. First comparison records are new. A later observation can be changed or unchanged. onlyChanges=true skips unchanged output and its result charge. All output is evidence to review; no predicted purchases, revenue or accuracy guarantees are made.

### Coverage and saved history

Search reads one source-ordered window of maxResults (1–100). selectedWindowComplete describes this requested window; sourceUniverseComplete separately states whether it happened to include all current matches. A complete three-record window can have sourceUniverseComplete=false. Source ordering is not promised to be newest-first. There is no removal inference: a record absent from a later window is not treated as deleted, closed, cancelled or unfunded. Search window size and filters separate saved history. Explicit IDs take precedence over all discovery filters.

Comparison history advances only after all requested source observations and intended outputs finish without a source error, time limit, result truncation, billing cap or concurrent writer. An undersized maxResults in ID mode produces partial coverage and preserves the prior baseline. Missing IDs are not deletion evidence. One snapshot should run sequentially. New/changed results are observations since your retained baseline, not source change notifications.

### Costs and limits

Price: $0.002 per saved result, plus the $0.00005 Actor Start event. For example, 20 saved records cost $0.04005 in Actor events, plus applicable Apify platform charges. No result fee is emitted for SUMMARY, RUN_REPORT, empty searches or skipped unchanged observations. A row is charged once when saved; a spending cap prevents unaffordable rows and stops history updates.

The default is three records and a 60-second budget; maximum 100 saved records and 120 seconds. Explicit watchlists support up to 20 IDs. Fixed official hosts only, no redirects, no login, no proxies and no access bypass. One documented API request per run; schedule repeated runs at least one second apart, and avoid parallel runs against NIH. HTTP 401/403/429 stop access attempts. Errors remain visible; no fallback records are invented.

### Good fit and limitations

Research suppliers, grant analysts, institutional business development teams and AI research assistants qualifying public institutional funding signals.

- NIH RePORTER project records are funding evidence, not procurement solicitations, contacts or a sales-intent score.
- The default is one bounded search window, not a census or guarantee of newest awards. RePORTER determines source ordering.
- Award amounts are source fiscal-year/award amounts, not lifetime budgets. No totals or parent/subproject sums are produced.
- No API key is required. One source request per run; no parallel crawling, access bypass or error retries.

### Sources and attribution

[NIH RePORTER API](https://api.reporter.nih.gov/) supplies the public records. Public institutional fields are exported; investigator names, emails and phone numbers are deliberately excluded.

### Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

#### [ClinicalTrials.gov Monitor - Studies, Status, Phases](https://apify.com/maydit/clinicaltrials-gov-monitor)

Add registered trial context when reviewing a funded clinical research topic or institution.

1. Use the institution or research topic to define a separate ClinicalTrials.gov search in that Actor.
2. Review sponsor, study identifiers and dates before relating a registered trial to a funded project.

A funding record is not a trial registration, procurement request or evidence of treatment efficacy. Topic or organization similarity alone does not prove a project-to-trial relationship.

#### [Europe PMC Literature Monitor - Papers & Citation Changes](https://apify.com/maydit/europe-pmc-literature-monitor)

Find publication evidence relevant to a funded research topic before qualifying a research partnership or supplier opportunity.

1. Search the topic, project reference or institution separately in Europe PMC.
2. Retain DOI/PMID identifiers and publication dates; review grant acknowledgments in the original work before asserting a funding connection.

A funded project can have no matching publication in this source. Publication presence does not establish current purchasing intent or unspent budget.

### Connect and automate

Export JSON or CSV from Apify, save a Task, and schedule only the frequency the source and your workflow need. Existing Tasks can feed a spreadsheet, CRM, webhook or your AI agent. Check SUMMARY before accepting a run as complete. Use source IDs to deduplicate; always retain sourceUrl and dates.

[Browse Mayd It data tools](https://mayd-it.com/data-tools/) · [Workflow guides](https://mayd-it.com/data-tools/workflows/) · [Quality dashboard](https://mayd-it.com/data-tools/quality/)

Need a source field clarified? Open an issue on this Actor with your non-sensitive input and run ID.

# Actor input Schema

## `applicationIds` (type: `array`):

Optional exact application IDs (up to 20). When present, discovery filters—including excludeSubprojects—are ignored; each ID is explicitly labeled if it is a subproject.

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

NIH advanced title search using the AND operator. Up to 160 characters; not a claim that the project is purchasing anything.

## `fiscalYears` (type: `array`):

Optional source fiscal years, e.g. 2026. Source fiscal year is not a lifetime project budget.

## `organizationNames` (type: `array`):

Optional official institutional names. Literal exact matching; no investigator or personal contact enrichment.

## `states` (type: `array`):

Optional two-letter US state codes, e.g. CA.

## `activityCodes` (type: `array`):

Optional source award activity codes, e.g. R01 or R21.

## `excludeSubprojects` (type: `boolean`):

Prevents parent/subproject rows from being mixed in normal search results. Explicit ID mode retains exactly the requested public records; never sum parent and subproject amounts.

## `maxResults` (type: `integer`):

Search selects its first window of this size. Explicit-ID mode reads requested IDs; a smaller output limit makes that watchlist incomplete and prevents history updates.

## `maxRunSeconds` (type: `integer`):

Includes source requests, parsing, billing and history. The platform timeout can end the run earlier.

## `comparePrevious` (type: `boolean`):

Save a baseline only after a complete selected scope and successful output. Run a snapshot sequentially.

## `onlyChanges` (type: `boolean`):

Implies comparison. A repeated unchanged snapshot can correctly return zero records with zero result charges.

## `snapshotName` (type: `string`):

1–80 letters, digits, underscores or hyphens. Filters and selected window also separate history. No removed-record inference.

## Actor input object example

```json
{
  "applicationIds": [],
  "keyword": "artificial intelligence",
  "fiscalYears": [],
  "organizationNames": [],
  "states": [],
  "activityCodes": [],
  "excludeSubprojects": true,
  "maxResults": 3,
  "maxRunSeconds": 60,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `report` (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 = {
    "keyword": "artificial intelligence",
    "excludeSubprojects": true,
    "maxResults": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/nih-research-funding-lead-monitor").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 = {
    "keyword": "artificial intelligence",
    "excludeSubprojects": True,
    "maxResults": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("maydit/nih-research-funding-lead-monitor").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 '{
  "keyword": "artificial intelligence",
  "excludeSubprojects": true,
  "maxResults": 3
}' |
apify call maydit/nih-research-funding-lead-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maydit/nih-research-funding-lead-monitor"
        }
    }
}
```

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/qyHRtASqiSJYQCi1k/builds/jnPQQ1oRa1utDtimk/openapi.json
