Build on Kindora

270,000+ funders and 9.5M+ grant records from public filings — as agent tools over MCP, or licensed to run inside your own product.

Two ways to build on it

The same corpus, reached two different ways. Most people arrive wanting one of these and bounce off documentation written for the other, so pick your side first.

For agents

Tools your assistant can call

Kindora as an MCP server. Your agent searches, reads profiles and — with an account — scores fit and writes to a pipeline.

  • Works with Claude, Claude Code, or any MCP client
  • Free public tools need no account and no key
  • Conversational volumes; results shaped for a model to read
Connect an MCP client ↓

For platforms & partners

Put Kindora inside your product

Kindora as a licensed component. Your users get funder search that works, you get the search you don't have to build, and we stay the source of record.

  • A licensed right to display Kindora results to your users
  • Reverse lookup: give us a nonprofit, get the funders behind it
  • Public-filing provenance, so redistribution is ours to license
See coverage and access ↓

What's actually in it

Every number here is counted from the live database — the corpus aggregates nightly, the headline counts on a daily refresh cycle — none of them typed in by hand. They move when the corpus moves, including down.

Funders

US grantmakers from IRS 990 and 990-PF filings, plus national charity registers

270,000+
US grantmakers

Private foundations and public-charity grantmakers — classified apart from the operating nonprofits that file the same forms

214,000+
Non-US funders

Canada, UK, Australia, and across Europe

56,000+
Grant records, US

Individual grants itemised from IRS 990 and 990-PF filings — private-foundation and public-charity grantmakers alike

9.5M+
Grant records, international

360Giving (UK), T3010 (Canada) and ACRI (Italy) registers

1.1M+
Recipients resolved to an EIN

The expensive half of the work, and the reason to license rather than parse filings yourself

6.8M+ (71%)
Grant dollars represented
$1.0T+
Grantmakers with outbound grants

Distinct funders we hold at least one grant for — fewer than the filer count, because many filers granted nothing

178,000+
Filing years covered
2023–2026
Funder programs
355,000+
Open right now

Deadlines and eligibility read from funders' own sites, refreshed weekly

56,000+
US government grant portals

State and district portals with live opportunities, plus the federal grants portal — each source connected individually

41
Countries represented
121

Recounted November 19, 2026 — the timestamp is live too, so you can tell if this page ever stops tracking.

Where it comes from, and what that means for you

The spine is public: IRS Form 990 and 990-PF filings, national charity registers, and government grant portals — federal and state alike. On top of that we read funders' own websites for what filings can't tell you — which programs are open, who's eligible, when they close, and who to talk to. And we search the open web for what's being reported about a funder elsewhere — leadership changes, new initiatives, coverage that never appears on their own site — verify it, and structure it into the profile. We ingest all of it ourselves rather than reselling a third party's compilation, which is why the terms of use are ours to negotiate rather than someone else's to restrict.

Read the full source breakdown, including where it falls short →

What we build on top of the filings

A raw 990 is a tax form: a name, an address, financial totals, and grant lines whose recipients are free-typed text with no ID and no location. Nothing in it answers the questions that matter — who funds work like mine, can I approach them, what would they give. The structured layer is where those answers come from:

Recipient resolution

Every grant line is matched from free text to a real organization with a real EIN, so grants connect to actual entities instead of strings. It's the foundation under peer analysis and reverse lookup — without it, millions of grants are just text.

Funder classification

Deterministic rules plus AI label every funder — independent foundation, community foundation, DAF sponsor, operating nonprofit, corporate, government — so search returns real grantmakers, and pass-through vehicles are labelled honestly instead of ranked as prospects.

Giving behaviour, measured

Typical grant size, giving trends, what share of each year's grantees are first-time recipients, and subject and geographic concentration — computed from what a funder actually does, which the filing never states. Plenty of funders headquartered in one state fund only another; behaviour is the truth, the address is not.

Names people actually use

Funders file under legal names nobody searches for. We extract the brand and DBA names, so looking a funder up by the name you know it by actually works.

The web layer

Filings rarely carry a usable website. We find and validate one, then read the program and application pages — because whether and how you can approach a funder lives on the web, not in the filing.

People and governance

Officers, trustees, and compensation, extracted and structured, so board-network and relationship analysis has real data to work with.

Meaning-based search

AI-written summaries of what each funder actually funds, plus semantic embeddings — so a search for the work you do finds the right funders even when no filing ever used your words.

This derived layer — the matching, classification, and analysis, not the public records underneath — is what the Data Use Policy licenses. The underlying facts stay public, as they should; the structure is the product.

How current it is

Filings land as the IRS publishes them. Funder websites are re-crawled weekly, with new URLs discovered monthly. Public filings are structurally 18–24 months behind the year they describe — that's a property of the source, not of us, and the website layer exists precisely because of it.

The agent path: two tiers, one MCP server

Start free with public funder and grant search — no account, no key. Connect a Kindora account to add authenticated, credit-metered tools: fit scoring, intel briefs, and pipeline reads and writes for teams that run their fundraising in Kindora.

Free

Public tier

No signup. Anonymous access to IRS-grade funder and grant data at interactive volumes. Batch integrations: send your service key to meter instead (see pricing).

  • Search 270,000+ funders by name, cause, or location
  • Find open grant opportunities and philanthropy jobs
  • Profiles, 990 summaries, grant histories, and NTEE codes

Pro

Authenticated tier

Connect your account for the authenticated tools that work against your pipeline and Kindora's enriched intelligence, plus the full public search catalog on the same authenticated endpoint. Most need a paid plan.

  • Funder-fit evaluations and deep-dive intel briefs
  • Donor CRM queries, segments, and warm-intro paths
  • Prospecting pipeline reads and writes
Get an API key

Free — no auth

Start free in 60 seconds

No account, no key, nothing to install. Point your MCP client at the public endpoint and your agent is searching live funder data right away — pick whichever path fits your setup:

Claude (web or desktop)

In Claude, click Customize in the sidebar, open the Connectors tab, then + Add → Add custom connector, and paste the endpoint URL:

https://mcp.kindora.co/mcp

Claude Code

Run one command in your terminal:

claude mcp add --transport http kindora https://mcp.kindora.co/mcp

Any other MCP client

Add this to your client's config file (for Claude Desktop: claude_desktop_config.json):

{
  "mcpServers": {
    "kindora": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote@latest",
        "https://mcp.kindora.co/mcp",
        "--transport", "http-only"
      ]
    }
  }
}

Building your own app or agent? Tell us which one it is

If your code calls Kindora (a script, an agent, a backend, a hosted function), send one request header naming it. The free tier stays free and needs no key; the name lets us recognize your app, tell it apart from abuse, and warn you before we change something you depend on. It is not a credential and it never raises a limit by itself. An app that calls without it will now and then see a short note in a tool result asking for it, written so your agent can pass it on to you.

X-Kindora-Client: acme-grants-bot

Python (official MCP SDK)

import asyncio

import httpx
from mcp import ClientSession
from mcp.client.streamable_http import streamable_http_client


async def main() -> None:
    async with httpx.AsyncClient(
        headers={"X-Kindora-Client": "acme-grants-bot"},
        timeout=httpx.Timeout(30, read=300),
    ) as http:
        async with streamable_http_client("https://mcp.kindora.co/mcp", http_client=http) as (read, write, _):
            async with ClientSession(read, write) as session:
                await session.initialize()
                print(await session.list_tools())


asyncio.run(main())

TypeScript (official MCP SDK)

import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"

const transport = new StreamableHTTPClientTransport(new URL("https://mcp.kindora.co/mcp"), {
  requestInit: { headers: { "X-Kindora-Client": "acme-grants-bot" } },
})

Any other client that lets you set request headers works the same way: LangChain's MultiServerMCPClient and the OpenAI Agents SDK take a headers map next to the URL, and mcp-remote takes --header "X-Kindora-Client: your-app-name". Use letters, digits and ._/@:+- (64 characters at most).

Want us to be able to reach you? Email support@kindora.co with the name you chose, and we will use it to tell you about changes that affect your app.

Full free-tier docs & tool reference →

Get a key in three steps

1

Create your account

Sign up for Kindora (free). Your account is the home for your keys, credits, and pipeline.

2

Generate a service key

In Settings → Developers, generate a scoped key (kdra_…). Choose read-only, or add write and spend scopes. The key is shown once.

3

Connect your client

Add the Pro endpoint to your MCP client with the key as a bearer token. You're live.

Already have a Kindora account? Generate a key →

Credit-based pricing

Interactive use of the public tools is free, and so are Pro pipeline reads, quotes and cached results. Fresh AI work, donor and warm-path queries, and batch data volume charge, always from the same credit balance.

Pro pipeline reads, quotes & cache hits
Free
Funder-fit evaluation
1 credit
Donor & warm-path queries
1 credit
Deep-dive intel brief
25 credits
Batch data lookups (public tools + your key)
3 lookups / credit

Credit packs

  • Starter — 100 credits$10
  • Power — 500 credits$45
  • Pro — 2,000 credits$160
  • Bulk — 10,000 credits$650

Plans include monthly credits: Starter 250 · Growth 500 · Pro 2,000 · Consultant Team 4,000. Buy more anytime.

Three ways in, and what each one permits

Two of these are self-serve and cover research — yours, or your clients'. The third is the only one that lets you show Kindora results to your own users. They are different rights, not different sizes of the same right, which is why volume alone never converts one into another.

AccessLimitsWhat it permits
Free public tier100 requests / hour per IP · hosted apps 60 / hour and 200 / day per project · no account, no keyResearch and AI-assistant use for your own organization or a named client engagement.
Metered, with a service key3 lookups / credit · 2,000 / hour · 12,000 / dayThe same permitted uses, at working volume. Capacity for your own research — not a licence to redistribute, embed, resell, or build a database from.
Embedded distribution licenceFrom $12,000 / year · allowance included, overage meteredThe right to display Kindora results inside your own product, to your own users, with attribution.

Both ceilings are real and enforced: 2,000 lookups an hour and 12,000 a day, per organization. They are set where they are because the metered lane is sized for research, not for serving another product's traffic.

Send your kdra_ service key as a Bearer token to the public MCP endpoint. On a paid plan these lookups are included. On the free plan they meter at 3 per credit — roughly $21.67–$33.33 per 1,000 lookups, depending on pack size. Metered capacity covers the permitted uses above; it does not confer embedding or redistribution rights at any volume.

Free-tier limits in detail

The free tier is sized for a person or an assistant doing research, and for an integrator trying the tools before registering. Every ceiling below is enforced by the server itself; this table was checked against it on 6 October 2026.

How your calls arrivePer rolling hourOver a day or monthAlso
From a fixed IP address — your laptop, a server, a CI runner100 requests per IP1,500 per IP per calendar monthSemantic searches (open grants, funder jobs, peer funders, free-text funder search) 30 / hour each. Browsing open grants or jobs with no query 15 / hour each. The funder-detail tools (profile, 990 summary, grants made, giving stats) 40 / hour and 500 / month.
From a platform that rotates its egress IP — Supabase Edge Functions today60 per project200 per project per UTC dayEach project also sits inside shared pools: 150 / hour and 1,000 / day for all unlabeled apps on the platform together, and 1,500 / day for the whole platform. Funder-detail tools: 150 / hour and 500 / day platform-wide. This is a taste of the tools, not a production allowance — take a service key before you ship.
From Claude — claude.ai, Claude Desktop or Claude Code, through Anthropic's networkIts own pooled tierNo monthly capOne Anthropic address carries many people's conversations, so the pool is sized for all of them. A single conversation is unlikely to reach it.

When a ceiling is reached the tool returns a JSON result, not an HTTP error. Every refusal carries error, retry_after in seconds and limit. A refusal by a monthly, daily, per-project or pool ceiling also names it in scope (for example platform_project_hourly_volume) and, where a service key lifts it, an upgrade_url; a refusal without scope is one of the rolling-hour tool windows. Wait out retry_after — retrying sooner is refused again and does not shorten the wait.

The X-Kindora-Client header identifies your app in our analytics so we can reach you before changing behavior you depend on. It never raises a limit and is never a credential. On a rotating-egress platform a labeled app is not counted against the pool shared by unlabeled apps, but its project quota and the platform-wide day still apply.

To go past any of these, send a service key: your calls leave every shared pool and run in your organization's own lane at 2,000 lookups an hour and 12,000 a day.

What needs a written agreement

Our Data Use Policy is the same for everyone, and no credit balance is a substitute for it. Each of the following needs an agreement, at any volume: redistributing Kindora data; embedding it in your product, platform or service; reselling or sublicensing it; bulk or systematic extraction, including building or improving a database, directory or search index; and using it to train models or build retrieval indexes. That last one survives termination.

Read the Data Use Policy →

Attribution

Wherever Kindora data is shown to anyone beyond your own organization or client engagement, the surface must credit "Data from Kindora (kindora.co)" with a working link, and chat or voice surfaces must name Kindora in the answer itself. Licensed integrations carry their own attribution, set in the agreement — usually "Powered by Kindora".

REST API

1,000 requests / hour per key

The REST surface is small on purpose today — public match rationale only. Funder-profile and grant-history endpoints are specified but not yet shipped, so for anything broader use the MCP endpoint, which exposes the full public toolset.

API licence

If your users should see funder search inside your product, this is the lane. You get Kindora's full public toolset — natural-language funder and grant search, classified profiles, 990 summaries, grant histories — as generally available, improving as it improves. Kindora maintains the tools and the data; your team builds and maintains the connection in your product.

From$12,000 / year

Prepaid. One year includes 60,000 lookups, or start with a 90-day pilot: $3,000 with 30,000 lookups. Overage is $30 per 1,000 lookups, fixed for the term. Neither renews automatically.

What's included

  • The public toolset as generally available — when public search improves, your embed improves
  • Production access with service keys and a usage page in your account
  • A link that attributes your users' Kindora sign-ups to you
  • Connecting organizations' own Kindora accounts to your app, with each organization's approval

What sits outside it

The authenticated intelligence layer — fit scoring, intel briefs, drafting, donor and prospect research, pipeline actions — stays behind a Kindora account and credits, exactly as it does everywhere else. Result cards may show that a fit score exists without unlocking it.

Buy a licence

Endpoints

Free — no auth

https://mcp.kindora.co/mcp

Pro — sign-in or service key

https://mcp.kindora.co/mcp/premium

Sign in with your Kindora account: on claude.ai, add the Pro URL under Customize → Connectors → Add custom connector. Headless agents and clients that can send a header use a kdra_ service key (Authorization: Bearer …).

Sign-in for platforms

If your app works for many organizations, each one signs in with its own Kindora account rather than sharing a key. Point your MCP client at the Pro endpoint. The first request returns 401, and the server publishes its sign-in details at the address below. Your client registers itself, sends the person to Kindora's consent page, and retries with the token. Tokens last an hour and refresh automatically.

https://mcp.kindora.co/.well-known/oauth-protected-resource/mcp/premium
  • The organization comes from the signed-in person's Kindora account, not from the token. If they belong to more than one organization, pass organization_id on each call.
  • Use sign-in, not a service key, when your app suggests profile updates. Those tools need a signed-in person and refuse a service key.
  • What each organization can use depends on its plan. Personalized matches and other paid tools need a paid plan.
  • Sign-in has been tested with Claude's clients. If yours cannot connect, send the error to support@kindora.co.

Building and testing with your own account needs nothing more. Serving other organizations through your app needs the API licence. How partners get the licence →

Pro — connect with your service key

Add Kindora to your MCP client config, passing your kdra_ service key as a bearer token:

{
  "mcpServers": {
    "kindora-pro": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote@latest",
        "https://mcp.kindora.co/mcp/premium",
        "--transport", "http-only",
        "--header", "Authorization: Bearer ${KINDORA_MCP_KEY}"
      ],
      "env": { "KINDORA_MCP_KEY": "kdra_org_..." }
    }
  }
}

Ready to build?

Point a client at the free endpoint and you're querying live data in a minute. If Kindora belongs inside your own product, write to us and describe what your users need to see.