# Policy & Funding Radar: Bills, Rules & Grants (`m_ctim/policy-funding-radar`) Actor

Search one keyword across Congress bills, new federal regulations, and open federal grant opportunities in one combined report. For government-affairs, lobbying, and grant-seeking teams checking three portals at once.

- **URL**: https://apify.com/m\_ctim/policy-funding-radar.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** Business, News
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

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

## Policy & Funding Radar: Bills, Rules & Grants by Keyword

Give it a keyword. Get back one combined report: matching U.S. Congress
bills, new Federal Register regulations, and open Grants.gov funding
opportunities: three government portals, one search.

### Who this is for

- **Government-affairs and lobbying teams** tracking legislative and regulatory activity on an issue.
- **Nonprofits, universities, and research orgs** scanning for both policy developments and funding opportunities on the same topic.
- **Policy researchers and journalists** who currently check congress.gov, federalregister.gov, and grants.gov separately for the same story.

### Input

| Field | Type | Description |
|---|---|---|
| `keywords` | array | One search per keyword, e.g. `["data centers", "broadband"]`. |
| `daysBack` | integer (default `30`) | How far back to search across all three sources. |
| `maxResultsPerSource` | integer (default `10`) | Cap on results per source, per keyword. |

```json
{
  "keywords": ["data centers"],
  "daysBack": 30
}
```

### Output

One record per keyword:

```json
{
  "keyword": "data centers",
  "daysBack": 30,
  "congressBills": [
    { "billNumber": "H.R. 1234", "title": "...", "status": "Introduced", "sponsorName": "...", "link": "..." }
  ],
  "federalRegisterDocuments": [
    { "documentNumber": "2026-12345", "title": "...", "type": "Rule", "agencies": ["Department of Energy"], "publicationDate": "2026-09-10", "htmlUrl": "..." }
  ],
  "grantOpportunities": [
    { "opportunityNumber": "...", "title": "...", "agency": "...", "openDate": "09/01/2026", "closeDate": "11/01/2026", "opportunityUrl": "..." }
  ],
  "totalItems": 7,
  "sourceErrors": [],
  "checkedAt": "2026-09-19T12:00:00.000Z"
}
```

If one source fails (a portal outage, for example) the other two still
return normally: `sourceErrors` lists which source(s) failed and why,
rather than failing the whole keyword.

### How it works

Three official, direct API calls per keyword, no scraping, no proxy:

- **GovTrack.us** for Congress bills (same source as [Congress Bill Tracker](https://github.com/timmKal01/congress-bill-tracker))
- **Federal Register API** for new rules, proposed rules, and notices (same source as [Federal Register Tracker](https://github.com/timmKal01/federal-register-tracker))
- **Grants.gov API** for open funding opportunities (same source as [Grant Opportunity Tracker](https://github.com/timmKal01/grant-opportunity-tracker))

### Pricing note

Billed per **keyword searched**, not per item returned: one charge covers the
combined lookup across Congress bills, federal regulations, and grant
opportunities for that keyword, whether it turns up zero results or dozens
across all three sources.

### Related products

- [Congress Bill Tracker](https://github.com/timmKal01/congress-bill-tracker): bill search with more filters (status, sponsor state, specific Congress), not bundled with regulations or grants
- [Federal Register Tracker](https://github.com/timmKal01/federal-register-tracker): regulation search with agency/document-type filters
- [Grant Opportunity Tracker](https://github.com/timmKal01/grant-opportunity-tracker): grant search with agency filters
- [Federal Grant Award Tracker](https://github.com/timmKal01/federal-grant-award-tracker): grants already *awarded*, for tracking who got funded rather than what's open

# Actor input Schema

## `keywords` (type: `array`):

One search per keyword, e.g. "data centers", "broadband", "PFAS". Each keyword is searched across Congress bills, Federal Register documents, and Grants.gov opportunities.

## `daysBack` (type: `integer`):

How many days back to search across all three sources.

## `maxResultsPerSource` (type: `integer`):

Cap on results returned from each of the three sources, per keyword.

## Actor input object example

```json
{
  "keywords": [
    "data centers"
  ],
  "daysBack": 30,
  "maxResultsPerSource": 10
}
```

# 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 = {
    "keywords": [
        "data centers"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("m_ctim/policy-funding-radar").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 = { "keywords": ["data centers"] }

# Run the Actor and wait for it to finish
run = client.actor("m_ctim/policy-funding-radar").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 '{
  "keywords": [
    "data centers"
  ]
}' |
apify call m_ctim/policy-funding-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/policy-funding-radar"
        }
    }
}
```

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/j2HqywJWHg6V9eMYH/builds/P5pyQApeMnFjkZUy7/openapi.json