# Funding Entity Lookup: cited FEC committees and candidates (`citature/funding-entity-lookup`) Actor

Look up an FEC committee or candidate by id, or prefix-search either by name. Every result carries the citature entity id alongside the FEC id and a full receipt: the exact source, when it was retrieved, coverage caveats, and guardrails.

- **URL**: https://apify.com/citature/funding-entity-lookup.md
- **Developed by:** [citature](https://apify.com/citature) (community)
- **Categories:** AI
- **Stats:** 2 total users, 0 monthly users, 88.5% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 answer serveds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Funding Entity Lookup — cited FEC committees and candidates

Look up an **FEC committee** or **candidate** by id, or **prefix-search** either by
name — returned with a full citation receipt. This is the directory the
money-family actors pivot on: every result carries citature's stable `entity_id`
next to the FEC id, so you can go from "which committee is this?" to "where did its
money come from?" on the same key.

Data comes straight from the **Federal Election Commission** — the primary,
public-domain federal record. No aggregator, no scoring.

### What you can ask

- Look up committee **C00401224** — what is it, what type, what state?
- Look up candidate **H8TX01234**.
- Search committees whose name starts with **"ACME"**.
- Search candidates whose name starts with **"SMITH"**.

Keywords: FEC committee lookup, candidate lookup, campaign committee search, PAC
directory, political committee id, candidate id, FEC entity resolution, committee
name search, campaign finance directory.

### Input

One `query` selects the operation; supply the field it needs.

| `query` | Needs | Returns |
|---|---|---|
| `committee_lookup` | `committee_id` | one committee or `null` |
| `candidate_lookup` | `candidate_id` | one candidate or `null` |
| `committee_search` | `name_prefix`, optional `limit` | ranked committees |
| `candidate_search` | `name_prefix`, optional `limit` | ranked candidates |

```json
{ "query": "committee_search", "name_prefix": "ACME", "limit": 5 }
```

### Output — an answer with a receipt

The actor returns one receipt object (also stored as the run's `OUTPUT`).

```json
{
  "answer": [
    {
      "entity_id": "cmte_9a1c…",
      "committee_id": "C00401224",
      "name": "ACME PAC",
      "committee_type": "Q",
      "designation": "U",
      "party": null,
      "state": "DC",
      "cycle": 2024
    }
  ],
  "citations": [
    {
      "source": "fec",
      "source_label": "U.S. Federal Election Commission",
      "query_url": "https://www.fec.gov/files/bulk-downloads/2024/cm24.zip",
      "retrieved_at": "2026-01-02T00:00:00.000Z",
      "as_of": null,
      "cache": "cached",
      "record_id": null
    }
  ],
  "coverage": [
    "Coverage reflects records currently in citature's dataset, not the full upstream history."
  ],
  "guardrails": [
    "Research over public-domain federal records — not legal, financial, or eligibility advice.",
    "citature reports what the record says. It never renders a compliance verdict, a screening pass/fail, or a recommendation.",
    "Entity-level records only (committees, candidates, recipients, agencies, contracts). No individual-person data."
  ],
  "matches": [],
  "schema_version": "0.1.0"
}
```

A lookup that finds nothing returns `answer: null` with a citation — an honest
empty, never a fabricated record.

### Guardrails

- Research over public-domain federal records — **not** legal, financial, or
  eligibility advice.
- citature reports what the record says. It never renders a compliance verdict, a
  screening pass/fail, or a recommendation.
- Entity-level records only. No individual-person data is ever returned.

### Pricing

Pay per successful answer. You are charged only when an answer is served; a
rejected or failed request is never billed.

# Actor input Schema

## `query` (type: `string`):

What to do: look up one committee or candidate by id, or prefix-search committees or candidates by name.

## `committee_id` (type: `string`):

Required for committee lookup, e.g. C00401224.

## `candidate_id` (type: `string`):

Required for candidate lookup, e.g. H8TX01234.

## `name_prefix` (type: `string`):

Narrows a search to names starting with this, case-insensitively (e.g. 'ACME'). Omit to browse in name order. Ignored by the lookup operations.

## `limit` (type: `integer`):

Maximum number of search results to return (1 to 500).

## Actor input object example

```json
{
  "query": "committee_search",
  "name_prefix": "NATIONAL",
  "limit": 50
}
```

# Actor output Schema

## `receipts` (type: `string`):

No description

## `receipt` (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 = {
    "name_prefix": "NATIONAL"
};

// Run the Actor and wait for it to finish
const run = await client.actor("citature/funding-entity-lookup").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 = { "name_prefix": "NATIONAL" }

# Run the Actor and wait for it to finish
run = client.actor("citature/funding-entity-lookup").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 '{
  "name_prefix": "NATIONAL"
}' |
apify call citature/funding-entity-lookup --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ACLkO7JMMZwgqPhF0/builds/1EIHTefdScg01X2kR/openapi.json