nonprofit.screen

Look up US 501(c) nonprofits and screen each result against the OFAC sanctions list in one call. Pass q (organization name) or ein; each matched organization returns its registry record (EIN, name, location, NTEE code, subsection) plus a sanctions block — flagged status, match count, and the matching SDN entries with confidence scores. Grant-making due diligence, donation compliance, and charity-fraud triage. Components also standalone: /api/nonprofit/search (registry only) and /api/law/sanctions-check (screen any name). Same composition family as /api/business/entity-screen.

price
$0.0050 USDC per call
method
GET/api/nonprofit/screen
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The screen API is a pay-per-call nonprofit endpoint built for AI agents and autonomous software. Look up US 501(c) nonprofits and screen each result against the OFAC sanctions list in one call.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in screen data source for an agent tool-use loop, an MCP host, or a backend that needs nonprofit data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
qstringOrganization name. Provide q or ein, not both.
min 2 chars · max 120 chars
einstring
match ^\d{9}$
limitinteger
min 1 · max 10

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/nonprofit/screen?q=xx&ein=12345&limit=5'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/nonprofit/screen?q=xx&ein=12345&limit=5' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/nonprofit/screen?q=xx&ein=12345&limit=5'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.nonprofit.screen({
  "q": "xx",
  "ein": "12345",
  "limit": 5
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.nonprofit.screen(q="xx", ein="12345", limit=5)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "nonprofit.screen",
    "arguments": {
      "q": "xx",
      "ein": "12345",
      "limit": 5
    }
  }
}

Response

FieldTypeDescription
querystring
countnumber
organizationsarray
sourcesarray
Example response datajson
{
  "query": "example",
  "count": 1,
  "organizations": [
    {
      "org": {},
      "sanctions": {
        "found": false,
        "error": "example",
        "flagged": false,
        "matchCount": 1,
        "matches": [
          {}
        ]
      }
    }
  ],
  "sources": [
    {
      "provider": "example",
      "url": "example",
      "license": "example"
    }
  ]
}

FAQ

Do I need an API key to use the screen API?
No. nonprofit.screen is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the screen API cost?
$0.00504 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the screen API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call nonprofit.screen from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: screen api · nonprofit screen api · screen api for ai agents · x402 nonprofit api · screen api no api key · pay per call screen api · nonprofit api