🔎 Connecticut Business Status Check

A per-identity check: submit identifiers, get one official answer each. Billed per completed official resolution — a not-found, ambiguous, or unavailable outcome is returned but never charged.

Output is one ct_business_status_answer row per result; billing is pay-per-event, the value event being one business status check (a $0.02 start fee per run, then $0.05 per business status check). Source: data.ct.gov.

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 Tiv4BAgDFfxtmBv1O on build 0.1.5 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

input	query_mode	business_id	status	outcome	outcome_reason
2873007	id	2873007	Expired Reservation	answer	status carried verbatim; standing/annual-report not in the keyless reg
C3 PARTNERS LLC	name			ambiguous	exact name matches more than one entity — resolve by account number

The run finished with the status message: NORMAL: 1 billable answer(s), 1 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 2 | business-status-check billable=1 | business-status-check charged=1

✅ 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/null) — e.g. ct_business_status_answer
• input (string/null) — e.g. 2873007
• query_mode (string/null) — e.g. id
• business_id (string/null) — e.g. 2873007
• name (string/null) — e.g. C3 Partners LLC
• status (string/null) — e.g. Expired Reservation
• standing (string/null) — null in every sample row
• annual_report_recency (string/null) — null in every sample row
• date_registration (string/null) — null in every sample row
• woman_owned (boolean/null) — e.g. False
• veteran_owned (boolean/null) — e.g. False
• minority_owned (boolean/null) — e.g. False
• disability_owned (boolean/null) — e.g. False
• lgbtqi_owned (boolean/null) — e.g. False
• outcome (string/null) — e.g. answer
• outcome_reason (string/null) — e.g. status carried verbatim; standing/annual-report not in the keyless register (hon
• source (string/null) — e.g. https://data.ct.gov/resource/n7gp-d28j.json

What you get

One record per submitted identity. A resolved identity carries the official fields verbatim; fields the source withholds are honest null with a reason. Not-found, ambiguous, and service-unavailable outcomes are distinguished in the outcome field and are not billed. A run that gets no definitive result at all fails loud and charges nothing.

⚙️ Sample inputs

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

{
  "entities": [
    "2873007",
    "C3 PARTNERS LLC"
  ]
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.05 business-status-check = $0.07 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "entities": [
    "2873007",
    "C3 PARTNERS LLC"
  ]
}

A bounded run for checking the field shape before scheduling.

3. A full-size run

{
  "entities": [
    "2873007",
    "C3 PARTNERS LLC"
  ]
}

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

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

{
  "record_type": "ct_business_status_answer",
  "input": "2873007",
  "query_mode": "id",
  "business_id": "2873007",
  "name": "C3 Partners LLC",
  "status": "Expired Reservation",
  "standing": null,
  "annual_report_recency": null,
  "date_registration": null,
  "woman_owned": false,
  "veteran_owned": false,
  "minority_owned": false,
  "disability_owned": false,
  "lgbtqi_owned": false,
  "outcome": "answer",
  "outcome_reason": "status carried verbatim; standing/annual-report not in the keyless register (honest null)",
  "source": "https://data.ct.gov/resource/n7gp-d28j.json"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each business status check is charged at the moment it is pushed (business-status-check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Each identity is resolved against the official Connecticut business registry (data.ct.gov n7gp-d28j). A business account number resolves to at most one entity; an exact name matching more than one returns an ambiguity (resolve by account number) and is not billed. A resolved entity returns its registry status verbatim plus registration date and the published diversity-ownership certifications. The keyless register does not expose a separate standing or annual-report recency field, so those are honest null with a reason. Unknown identities are not-found and not billed. Per-entity status twin of the connecticut-business-registry-master roster.

Billing

Event	FREE	BRONZE	SILVER	GOLD+
apify-actor-start (one-time actor start)	$0.02	$0.02	$0.02	$0.02
business-status-check (per completed resolution)	$0.05	$0.045	$0.04	$0.0335

Charged once per completed official resolution. Not-found, ambiguous, and service-fault outcomes are emitted but never charged. Start fee $0.02.

Source

https://data.ct.gov/resource/n7gp-d28j.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
Business Status Check (business-status-check)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price:

• 2 business status checks: $0.02 start + 2 × $0.05 = $0.12
• 25 business status checks: $0.02 start + 25 × $0.05 = $1.27
• 100 business status checks: $0.02 start + 100 × $0.05 = $5.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 1024 MB.

Yield on the sample run: NORMAL: 1 billable answer(s), 1 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 2 | business-status-check billable=1 | business-status-check charged=1.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by data.ct.gov. It collects only what the source publishes to any visitor, 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.ct.gov) 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 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 company registry checks actors?
A: Same output shape and billing model; this one covers data.ct.gov. 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; 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.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• 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

• CQC Provider Verification Check — Verify UK care providers and locations against the official CQC weekly directory — one present/absent verdict per identifier. Billed per PRESENT verd…
• EU EORI Customs Registration Check — Validates EORI numbers against the European Commission's official EORI service — one definitive registered / not-registered answer per identifier wit…
• EU VAT Validator — VIES per-answer check — Validate EU VAT numbers against the official EU VIES service — one verdict per number with the registered name and date. No API key; pay per complete…
• Finland PRH Business Filing Lookup — Look up Finnish companies by Business ID on the official PRH open-data trade register — name, company form, trade-register status, registration date,…
• 🏢 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.