Check any US nonprofit's IRS standing in seconds — one plain-English trust card with a green / amber / red verdict. An answer engine, not a database: verdict up front, evidence expandable, every field citing its source and "as of" date.
Your recent checks are kept on this device only. A cookieless analytics tool counts how the checker is used — never which organizations you look up.
Vetting a grantee list? Paste up to 50 organization names or EINs — one per line, or a CSV — and get every verdict at once, sorted worst-first so problems surface immediately. Where a name matches several organizations, you pick; it never guesses for you.
Every state has its own page with the same checker plus a live snapshot of that state's nonprofit landscape from the current IRS release — how many organizations are registered there, how many are recognised 501(c)(3)s, how many currently have their exemption revoked, and which categories are largest.
These pages cover federal IRS status. Registering with the IRS and registering to solicit donations in a state are different requirements — state charitable registration still isn't evaluated anywhere on this site.
A diligence tool earns trust by saying "I didn't look" — never by implying "nothing there."
Spec first: a full v1 build document with the correctness traps named before any code — group-ruling subordinates that look non-deductible, revoked-then-reinstated orgs that look revoked, churches that look like non-filers. Each trap is a test that fails the build, not the user.
Data comes from IRS.gov directly (Business Master File, Publication 78, the auto-revocation list, the 990 e-file index) — never from a re-publisher's API. Cards are precomputed monthly and served read-only, so there are no third-party calls at request time and no live database to corrupt: the warehouse builds a baked artifact, and the API serves it.
Built with AI in the loop, end to end — the same operating model I bring to organizations: spec → schema → verified 2M-row ingest in a working day, with human judgment on every gate that matters.
If your team verifies grantees by hand every cycle — someone working a portfolio against a deadline, re-keying results into a grants system, and re-doing it all next quarter — that is a workflow problem, not a lookup problem. Designing and building that workflow is what I do for foundations and grantmakers.
Tell me what your process looks like now — or if you want the API behind this page, ask for that instead.