Apify Public Data & Leads

US Nonprofit and IRS Form 990 Search

us_nonprofit_search

Read-only

Find U.S. nonprofit and charity records by name or keyword. Get EIN, location, classification, revenue, and optional Form 990 financials for research and screening.

Instructions

Search US nonprofit and charity records from ProPublica Nonprofit Explorer. Returns organization identity, EIN, location, classification, and reported revenue, with optional IRS Business Master File and Form 990 financial detail.

Behavioral Transparency:

Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/us-nonprofit-search'.
Side Effects: Creates a billed Actor run and dataset on your Apify account; queries public nonprofit and IRS-derived records.
Authentication: Requires APIFY_TOKEN.
Latency & Limits: Typical runs take 10-30 seconds without details and longer with Form 990 enrichment; timeout capped at 120 seconds.

Usage Guidelines:

When to use: Use for nonprofit discovery, EIN lookup, charity research, grant-market analysis, and public Form 990 financial screening.
When NOT to use: Do not use as a tax-exemption determination, charity recommendation, or substitute for the latest IRS record.
Named alternatives: Use 'grants_gov_opportunity_search' for funding opportunities, 'us_business_entity_search' for state-registered businesses, or 'company_registry_search' for UK, French, and LEI entities.

Input Schema

TableJSON Schema

Name	Required	Description
`max_results`	No	Maximum nonprofit records returned and billed.
`search_query`	Yes	Organization name or nonprofit keyword.
`include_details`	No	Add IRS Business Master File fields and latest machine-readable Form 990 financials.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`run`	No
`error`	No
`status`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Sep 18, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing execution style, billing side effects, authentication requirements, and latency limits. The description's side-effect note does not contradict readOnlyHint=true because it describes account-level billing, not external data mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections for behavior and usage, and every sentence adds context an agent needs. It is slightly long but justified by the tool's complexity and side effects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a network-backed, billed search tool, the description covers execution model, auth, side effects, latency, usage boundaries, alternatives, and output scope. An output schema exists, so return-value details do not need to be repeated here. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the structured schema already documents all three parameters. The description adds minimal new parameter meaning, though the 'optional IRS Business Master File and Form 990 financial detail' phrasing helps map include_details to real-world data. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search US nonprofit and charity records from ProPublica Nonprofit Explorer.' It further describes the output fields, making the tool's purpose clear and distinct from siblings like us_business_entity_search and company_registry_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance, clear when-not-to-use limitations, and names three alternative sibling tools with their respective scopes. This gives an agent a complete decision framework for selecting the correct tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server