🔔 Chicago Business Owners Register

One record per Chicago business owner/officer statutory-register row (account, DBA name, owner name parts, title) from the City's public Business Owners dataset. Official owner/officer rows are carried VERBATIM as published — no enrichment, no inference. It is a public statutory register.

Public, robots-honoured.

Output is one chicago_business_owner row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: data.cityofchicago.org.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run 6n58FJFoyN2bkOoh2 on build 0.1.4 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

account_number	doing_business_as_name	owner_first_name	owner_middle_initial	owner_last_name	owner_title
57028	A LAVA & SONS CO	LEO		APPELBAUM	PRESIDENT
458385	NANO CLASSICS, LLC	Amy	E	Runjavac-Duda	MANAGING MEMBER
362027	ENVIOS DE VALORES LA NACIONAL CORP.	Jon	C	Ness	CEO
456967	INOKO SUSHI RESTAURANT INC.	SHANSHAN		YU	SECRETARY
64406	SEADOG VENTURES, INC.	LAUREN		BARAN	TREASURER
458453	TAKAMIRO WILLIAMS	TAKAMIRO		WILLIAMS	SOLE PROPRIETOR
27102	L & P LIQUORS INC	SASHA		MILANOVICH	SECRETARY
64406	SEADOG VENTURES, INC.	KENNETH		SVENDSEN	CEO

The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. chicago_business_owner
• account_number (string/null) — e.g. 57028
• doing_business_as_name (string/null) — e.g. A LAVA & SONS CO
• owner_first_name (string/null) — e.g. LEO
• owner_middle_initial (string/null) — e.g. E
• owner_last_name (string/null) — e.g. APPELBAUM
• owner_name_suffix (string/null) — null in every sample row
• owner_name (string/null) — null in every sample row
• owner_title (string/null) — e.g. PRESIDENT
• source (string/null) — e.g. chicago-business-owners-register
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://data.cityofchicago.org/resource/ezma-pppn.json
• observed_at (string/null) — e.g. 2026-09-18T19:41:12Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row
• license (string/integer/null) — null in every sample row
• attribution (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "maxRecords": 50
}

The sample run charged exactly: 2 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.04 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
  "maxRecords": 5000
}

Up to 5000 rows (the schema default for maxRecords) — about $100.02 on the Free tier ($0.02 start + 5000 × $0.02) if the source has that many.

🧾 JSON sample record

One real record from run 6n58FJFoyN2bkOoh2, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "chicago_business_owner",
  "account_number": "57028",
  "doing_business_as_name": "A LAVA & SONS CO",
  "owner_first_name": "LEO",
  "owner_middle_initial": null,
  "owner_last_name": "APPELBAUM",
  "owner_name_suffix": null,
  "owner_name": null,
  "owner_title": "PRESIDENT",
  "source": "chicago-business-owners-register",
  "release_date": null,
  "source_url": "https://data.cityofchicago.org/resource/ezma-pppn.json",
  "observed_at": "2026-09-18T19:41:12Z"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: CRAWL_DELAY=1.0.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Rows are paged from the Chicago Business Owners Socrata resource (:id order, $limit/$offset) and count(*) reconciled. Owner name parts + title copied verbatim; nulls preserved. Crawl-Delay 1 honoured. Streaming, bounded to maxRecords.

Source

https://data.cityofchicago.org/resource/ezma-pppn.json

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Registry Record (registry_record)	$0.02	$0.02	$0.02	$0.01

Worked at the live Free-tier price:

• 8 registry records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 5000 registry records: $0.02 start + 5000 × $0.02 = $100.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by data.cityofchicago.org. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (data.cityofchicago.org) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers data.cityofchicago.org. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source (CRAWL_DELAY=1.0) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Brazil PNCP Price-Registration Minutes — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Brazil PNCP Tender Notices — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Chicago Business Licenses — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured
• CMS CLIA Laboratory Registry — One structured registryrecord per record from the CMS Provider of Services File - Clinical Laboratories dataset (data.cms.gov data-api, ~681,000 rows…
• CMS Dialysis Facilities — A clean, structured roster of Medicare-certified dialysis facilities in the United States,
• CMS Hospice Facilities — A clean, structured roster of Medicare-certified hospice facilities in the United States,
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.