business.entity-screen

KYC in one call: look up a business in a US state registry (NY, CO, CT) AND screen it against the OFAC sanctions list. Give a state and a name (or exact entityId). Returns the matched registered entities (id, type, status, jurisdiction, address, registered agent) and, for each, a sanctions screen of the entity name AND its registered agent against OFAC SDN — with fuzzy-match confidence and a flagged boolean. Counterparty due-diligence, vendor onboarding, AML. Composition of /api/business/sos-search + /api/law/sanctions-check (each section reports found/error independently). Note: sanctions screening is name-based and probabilistic — review flagged matches manually.

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

Overview

The entity screen API is a pay-per-call business endpoint built for AI agents and autonomous software. KYC in one call: look up a business in a US state registry (NY, CO, CT) AND screen it against the OFAC sanctions list.

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 entity screen data source for an agent tool-use loop, an MCP host, or a backend that needs business data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
staterequiredstring
one of: NY | CO | CT
namestring
min 2 chars · max 120 chars
entityIdstring
min 2 chars · max 30 chars
thresholdnumber
min 0.1 · max 1
limitinteger
min 1 · max 10

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/business/entity-screen?state=NY&name=xx&entityId=xx&threshold=0.5&limit=5'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/business/entity-screen?state=NY&name=xx&entityId=xx&threshold=0.5&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/business/entity-screen?state=NY&name=xx&entityId=xx&threshold=0.5&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.business.entityScreen({
  "state": "NY",
  "name": "xx",
  "entityId": "xx",
  "threshold": 0.5,
  "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.business.entity_screen(state="NY", name="xx", entityId="xx", threshold=0.5, 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": "business.entity-screen",
    "arguments": {
      "state": "NY",
      "name": "xx",
      "entityId": "xx",
      "threshold": 0.5,
      "limit": 5
    }
  }
}

Response

FieldTypeDescription
statestring
countnumber
entitiesarray
sourcesarray
Example response datajson
{
  "state": "example",
  "count": 1,
  "entities": [
    {
      "entity": {},
      "sanctions": {
        "found": false,
        "error": "example",
        "flagged": false,
        "entityMatchCount": 1,
        "agentMatchCount": 1,
        "matches": [
          {}
        ]
      }
    }
  ],
  "sources": [
    {}
  ]
}

FAQ

Do I need an API key to use the entity screen API?
No. business.entity-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 entity screen API cost?
$0.00576 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 entity 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 business.entity-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: entity screen api · business entity screen api · entity screen api for ai agents · x402 business api · entity screen api no api key · pay per call entity screen api · business api