Colorado Business Entities Master avatar

Colorado Business Entities Master

Pricing

from $13.40 / 1,000 registry records

Go to Apify Store
Colorado Business Entities Master

Colorado Business Entities Master

One master record per Colorado business entity (id, name, status, type, formation jurisdiction, formation date, principal + mailing address, registered-agent name + address) from the keyless CO Socrata resource.

Pricing

from $13.40 / 1,000 registry records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

πŸ”” Colorado Business Entities Master

One master record per Colorado business entity (id, name, status, type, formation jurisdiction, formation date, principal + mailing address, registered-agent name + address) from the keyless CO Socrata resource. Agent role fields are carried as published; nulls preserved.

Public, robots-honoured.

Output is one co_business_entity 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.colorado.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

Colorado Business Entities Master sample output β€” a table of real registry record rows (entity_id, entity_name, entity_status, entity_form_date) from run IdpeOaAWPYKL0Rabd on build 0.1.4

Real rows from run IdpeOaAWPYKL0Rabd 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):

entity_identity_nameentity_statusentity_form_dateprincipal_addressagent_address
20251665680KYLDERON MIST VALLEY LLCNoncompliant2025-06-16T00:00:00.000660 Willow Wood Ln660 Willow Wood Ln
19871342214SOUTHWEST CONTRACTING, LLC, Delinquent May 1, 2016Delinquent1978-02-28T00:00:00.00022989 COUNTY RD F22989 COUNTY RD F
20241953223Clean-Out to Closing, LLCGood Standing2024-09-10T00:00:00.00012215 Pine Post Dr12215 Pine Post Dr
20241953233OGB BEEF LLCGood Standing2024-09-10T00:00:00.000601 S WASHINGTON ST19751 E MAINSTREET STE 340
20241962808504B Granite, LLCGood Standing2024-09-13T00:00:00.0002038 Buchanan Pt2038 Buchanan Pt
20241962812STYLISHHIDEXX LLCDelinquent2024-09-13T00:00:00.0002795 N SPEER BLVD2795 N SPEER BLVD
20241962816LW Family Consulting LLCGood Standing2024-09-13T00:00:00.000983 S Vine St983 S Vine St
20241962820Jole Contracting LLCGood Standing2024-09-13T00:00:00.0001365 Ballard Ave1365 Ballard Ave

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. co_business_entity
  • entity_id (string/null) β€” e.g. 20251665680
  • entity_name (string/null) β€” e.g. KYLDERON MIST VALLEY LLC
  • entity_status (string/null) β€” e.g. Noncompliant
  • entity_type (string/null) β€” e.g. DLLC
  • jurisdiction_of_formation (string/null) β€” e.g. CO
  • entity_form_date (string/null) β€” e.g. 2025-06-16T00:00:00.000
  • principal_address (string/null) β€” e.g. 660 Willow Wood Ln
  • principal_city (string/null) β€” e.g. Delta
  • principal_state (string/null) β€” e.g. CO
  • principal_zip (string/null) β€” e.g. 81416
  • mailing_address (string/null) β€” e.g. PO BOX 719
  • mailing_city (string/null) β€” e.g. CORTEZ
  • mailing_state (string/null) β€” e.g. CO
  • mailing_zip (string/null) β€” e.g. 81321
  • agent_first_name (string/null) β€” e.g. KEQIANG
  • agent_middle_name (string/null) β€” e.g. G
  • agent_last_name (string/null) β€” e.g. DENG
  • agent_suffix (string/null) β€” null in every sample row
  • agent_organization_name (string/null) β€” e.g. Paul M Zimmerman Law, LLC
  • agent_address (string/null) β€” e.g. 660 Willow Wood Ln
  • agent_city (string/null) β€” e.g. Delta
  • agent_state (string/null) β€” e.g. CO
  • agent_zip (string/null) β€” e.g. 81416
  • source (string/null) β€” e.g. colorado-business-entities-master
  • release_date (string/null) β€” null in every sample row
  • source_url (string/null) β€” e.g. https://data.colorado.gov/resource/4ykn-tg5h.json
  • observed_at (string/null) β€” e.g. 2026-09-18T19:37:55Z
  • 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 IdpeOaAWPYKL0Rabd, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "co_business_entity",
"entity_id": "20251665680",
"entity_name": "KYLDERON MIST VALLEY LLC",
"entity_status": "Noncompliant",
"entity_type": "DLLC",
"jurisdiction_of_formation": "CO",
"entity_form_date": "2025-06-16T00:00:00.000",
"principal_address": "660 Willow Wood Ln",
"principal_city": "Delta",
"principal_state": "CO",
"principal_zip": "81416",
"mailing_address": null,
"mailing_city": null,
"mailing_state": null,
"mailing_zip": null,
"agent_first_name": "KEQIANG",
"agent_middle_name": null,
"agent_last_name": "DENG",
"agent_suffix": null,
"agent_organization_name": null,
"agent_address": "660 Willow Wood Ln",
"agent_city": "Delta",
"agent_state": "CO",
"agent_zip": "81416",
"source": "colorado-business-entities-master",
"release_date": null,
"source_url": "https://data.colorado.gov/resource/4ykn-tg5h.json",
"observed_at": "2026-09-18T19:37:55Z"
}

πŸ”§ 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 CO Socrata resource (:id order, $limit/$offset), an optional statusFilter narrows the published status, and count(*) is reconciled. Crawl-Delay 1 honoured. Streaming, bounded to maxRecords β€” never a full-file self-charged pull; full-scope enumeration is :id-ordered with row memory bounded.

Source

https://data.colorado.gov/resource/4ykn-tg5h.json

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

πŸ’° Pricing example

EventFreeBronzeSilverGold
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.

This actor reads public, logged-out pages and feeds published by data.colorado.gov. 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.colorado.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 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.colorado.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 (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.
  • 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,
  • Czech ARES Company Registry β€” One structured registryrecord per record from the keyless ares.gov.cz REST economic-subjects API, logged-out. Public, logged-out, robots-honoured
  • Estonia Company Registry (bulk) β€” One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
  • Ireland CRO Company Records β€” One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured
  • 🏒 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.