US Business Entity Search

Apify Actor that queries the SIP Public Data Gateway over HTTPS—no browser, no scraping of Secretary of State sites. You provide search terms (and optional state filters); the Actor calls SIP’s unified APIs and returns normalized business entity rows plus optional OFAC / SEC / IRS nonprofit matches.

What it does

• Search 10+ US state corporate registries exposed through SIP (group us_business_registry), or restrict to specific two-letter state codes.
• When all registry states are selected (or ALL), the Actor uses one group request:
  GET /api/v1/data/groups/us_business_registry/search
  (fewer round-trips than per-state calls).
• Optional add-ons: OFAC sanctions (us_ofac_sanctions), SEC (us_sec_edgar), IRS exempt organizations (us_irs_nonprofits).

Use cases

KYB / compliance checks, B2B lead enrichment, diligence, and competitive research—using official registry-style fields already normalized by SIP.

Data sources (SIP products)

Scope	product_id examples
State registries	us_business_ny, us_business_tx, us_business_co, us_business_ct, us_business_ia, us_business_pa, us_business_or, us_business_ak, us_business_nj_corps
Sanctions	us_ofac_sanctions
Public companies	us_sec_edgar
Nonprofits	us_irs_nonprofits

Exact coverage depends on which products are public and active in your SIP deployment.

Input

Field	Description
searchTerms	Required. List of strings to search (e.g. ["Google", "Acme LLC"]).
states	Optional. ["ALL"] (default) or any of NY, TX, CO, CT, IA, PA, OR, AK, NJ. Subsets use per-state product calls; full set uses group search.
includeCompliance	If true, also query OFAC + SEC for each term.
includeNonprofits	If true, also query IRS nonprofits.
maxResultsPerState	Cap per SIP request (SIP currently allows 1–200; values above 200 are clamped).

Output (dataset items)

Each row is a SIP search hit, with extra Actor fields:

• Business fields (examples): business_name, license_id, license_type, status, city, state, address, zip_code, issue_date, source_jurisdiction (when present in the product schema).
• Actor metadata: _product_id, _source (state code like NY, or US_REGISTRY_GROUP, or federal_ofac / federal_sec / federal_irs), _search_term, _collected_at.

Example record (shape)

{
  "license_id": "4809335",
  "business_name": "GOOGLE ACCESS LLC",
  "issue_date": "2015-08-24T00:00:00.000",
  "city": "Albany",
  "state": "NY",
  "license_type": "FOREIGN LIMITED LIABILITY COMPANY",
  "address": "80 STATE STREET",
  "zip_code": "12207",
  "_product_id": "us_business_ny",
  "_source": "NY",
  "_search_term": "google",
  "_collected_at": "2026-04-04T12:00:00Z"
}

Configuration (secrets)

Set the SIP gateway key in the Apify Actor environment (recommended name):

Variable	Description
SIP_API_KEY	SIP X-API-Key value (mark as secret in Apify).

Optional:

Variable	Description
SIP_API_BASE	Override gateway root, e.g. https://your-sip-host/api/v1/data. Default: https://sip.myskillstore.dev/api/v1/data.

For local testing only, you may pass sipApiKey in input; prefer environment variables on Apify so keys are not stored in run input.

Create the key in SIP (SQL / admin) per your ops process—do not commit keys to git.

Pricing (reference)

Target positioning from the product brief: a small per-run start fee plus per-result pricing (on the order of ~$2 per 1,000 results combined). Configure exact USD amounts in the Apify Actor Pricing tab; this README does not lock prices.

Local development

cd "/Users/kane/Projects/Apify Actors/sip-us-business-entity-scraper"
python3.13 -m venv .venv
.venv/bin/pip install -r requirements.txt
export SIP_API_KEY="your-key"
echo '{"searchTerms":["google"],"states":["NY","TX"],"maxResultsPerState":5}' > storage/key_value_stores/default/INPUT.json
apify run

Or:

$SIP_API_KEY=... python -m src

(with INPUT.json under storage/... when using Apify CLI conventions).

Deploy

apify login
apify push

Use APIFY_TOKEN or CLI login—never commit tokens.

Legal

You must comply with SIP terms of use, Apify terms, and applicable data protection laws. This Actor is an API client to your own gateway; you are responsible for lawful use of downstream registry data.