person.cross-registry

Sweep a person's name across five US public registries in one call: FINRA securities brokers, federal-court attorneys (CourtListener), federal inmates (BOP), Texas trade licenses (TDLR), and Texas real-estate licenses (TREC). Returns one block per registry with found/error status, match count, and the matching records — name-matched CANDIDATES, deliberately not merged into one identity (same name does not mean same person; verify with each registry's identifier before acting). Due-diligence, KYC screening triage, and background-research staple. Each registry is also a standalone endpoint (/api/license/broker, /api/law/attorney-lookup, /api/gov/inmate-locator, /api/license/trades, /api/license/real-estate) for follow-up by identifier.

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

Overview

The cross registry API is a pay-per-call person endpoint built for AI agents and autonomous software. Sweep a person's name across five US public registries in one call: FINRA securities brokers, federal-court attorneys (CourtListener), federal inmates (BOP), Texas trade licenses (TDLR), and Texas real-estate licenses (TREC).

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

Use cases

Parameters

NameTypeDescription
namerequiredstringPerson full name. "First Last" works best (the inmate registry needs split names).
min 3 chars · max 120 chars · match ^[\p{L}][\p{L} .,'-]+$
limitinteger
min 1 · max 10

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/person/cross-registry?name=xxx&limit=5'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/person/cross-registry?name=xxx&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/person/cross-registry?name=xxx&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.person.crossRegistry({
  "name": "xxx",
  "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.person.cross_registry(name="xxx", 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": "person.cross-registry",
    "arguments": {
      "name": "xxx",
      "limit": 5
    }
  }
}

Response

FieldTypeDescription
namestring
notestringIdentity-resolution disclaimer — matches are candidates, not confirmed identities.
brokersobject
attorneysobject
inmatesobject
txTradesobject
txRealEstateobject
sourcesarray
Example response datajson
{
  "name": "example",
  "note": "example",
  "brokers": {
    "found": false,
    "error": "example",
    "count": 1,
    "matches": [
      {}
    ]
  },
  "attorneys": {
    "found": false,
    "error": "example",
    "count": 1,
    "matches": [
      {}
    ]
  },
  "inmates": {
    "found": false,
    "error": "example",
    "count": 1,
    "matches": [
      {}
    ]
  },
  "txTrades": {
    "found": false,
    "error": "example",
    "count": 1,
    "matches": [
      {}
    ]
  },
  "txRealEstate": {
    "found": false,
    "error": "example",
    "count": 1,
    "matches": [
      {}
    ]
  },
  "sources": [
    {
      "provider": "example",
      "url": "example",
      "license": "example"
    }
  ]
}

FAQ

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