Skip to main content
Glama

Colorado New Business Leads: New SOS Filings Daily

colorado_new_business_leads
Read-only

List newly formed Colorado LLCs, corporations and nonprofits from official Secretary of State data, filtered by formation date, city, ZIP and self-agent status, to reach new business owners early.

Instructions

List newly formed Colorado LLCs, corporations and nonprofits from the official Colorado Secretary of State 'Business Entities in Colorado' open data (data.colorado.gov, updated daily), with formation date, entity type, status, principal and mailing address, registered agent and a self-agent flag (the agent is a person at the business address, usually the owner). Unlike florida_new_business_leads (Sunbiz with officers), texas_new_business_leads (Comptroller franchise taxpayers) and new_york_new_business_leads (NY DOS), this is Colorado formations. Use when banks, insurance, payroll, accountants, web agencies or suppliers want new Colorado owners in their first weeks. Do not use for other states, for emails or phones (the source has none) or for historical entity search. Parameters: daysBack (default 7) or formedFrom/formedTo set the window; cities and zipPrefixes match the principal address; entityTypes and nameContains (comma-separated words) narrow rows; onlySelfAgent keeps likely owner-filed rows; excludeAgentServices drops commercial registered-agent companies and virtual offices; onlyColoradoAddress drops out-of-state foreign entities; onlyGoodStanding (default true); maxResults caps billed businesses (hard max 10000). Runs with no matches are free. Returns per item: agentSummary, entityId, name, entityType, formationDate, status, jurisdiction, principal and mailing address fields, agentName, agentType, agent address fields, selfAgent, principalIsAgentAddress, sosUrl, sourceUrl; plus COBIZ_XLSX (with Self-agent owners sheet)/CSV.

Behavior: read-only; runs the Apify Actor pandadad0214/colorado-new-business-leads (https://apify.com/pandadad0214/colorado-new-business-leads) on your own Apify account. Price: $0.0015 per business returned. Runs that find nothing are not charged per result, and spending is capped per call by run_max_charge_usd (default $0.50). run_max_items (default 50) limits items returned and fills maxResults when you leave it unset, so it also limits what is billed; setting maxResults higher can bill more than is returned. Most calls finish in 5-15 s for a few inputs; large inputs or crawls can take minutes, so raise run_timeout_secs (max 300) or shrink the input after a timeout error. Returns JSON {actor, count, items}; long text output is trimmed to whole items, with all items in structuredContent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "colorado_new_business_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesNoCities. Principal-address city (case-insensitive), e.g. Denver, Colorado Springs, Aurora, Fort Collins, Boulder, Lakewood.
daysBackNoFormed in the last N days. Default 7. Matches the Secretary of State formation date. Use 1 or 2 on a daily schedule.
formedToNoFormed on or before. Optional YYYY-MM-DD.
formedFromNoFormed on or after. Optional YYYY-MM-DD; overrides days back.
maxResultsNoMaximum results. You pay per business returned, so this also caps the cost. Default 500; hard max 10000.
entityTypesNoEntity types. Empty = all types. Colorado LLCs are about 80% of new filings.
zipPrefixesNoZIP prefixes. Principal ZIP starts-with, e.g. 802 (Denver), 809 (Colorado Springs), 805 (Fort Collins/Boulder area).
nameContainsNoName contains. Case-insensitive; comma-separate several words to match any, e.g. roofing, construction, landscaping.
onlySelfAgentNoOnly self-agent filings (likely owner). Keep rows where the registered agent is a person at the business address, which is usually the owner.
run_max_itemsNoOptional. Most results to return from this call (default from PANDA_MAX_ITEMS, 50). Also limits how many results the Actor produces and charges for, unless you set its own max field.
onlyGoodStandingNoOnly Good Standing. Default on. Turn off to include withdrawn or dissolved entities formed in the window.
run_timeout_secsNoOptional. Seconds to wait for results (default from PANDA_TIMEOUT_SECS, 120; max 300).
run_max_charge_usdNoOptional. Hard spending cap for this call in USD (default from PANDA_MAX_CHARGE_USD, 0.50).
onlyColoradoAddressNoOnly Colorado principal address. Drop foreign entities with an out-of-state principal address.
excludeAgentServicesNoExclude agent services and virtual offices. Drop rows whose agent is a commercial registered-agent company, or whose principal address is the agent company's address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description goes further with what annotations cannot express: it runs a specific Apify Actor on the caller's account, charges $0.0015 per business returned, leaves zero-match runs free, and caps spend via run_max_charge_usd. It also discloses the non-obvious interaction that run_max_items fills maxResults when unset and therefore limits what is billed, and gives latency expectations plus timeout remediation. Return shape is enumerated, which compensates for the missing output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what it lists, where the data comes from, and how it differs from siblings, then segmented into Parameters and Behavior blocks that are easy to scan. It is long but the length is largely justified by a 15-parameter, per-result-billed actor; a few clauses (e.g. repeating the $0.50 default already stated in the schema) could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description enumerates the per-item return fields (agentSummary, entityId, formationDate, selfAgent, sosUrl, etc.), the envelope ({actor, count, items}), and the XLSX/CSV extras, so the agent knows exactly what comes back. Combined with billing, timeout and filtering guidance, nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description mostly restates defaults already present in the schema ('onlyGoodStanding (default true)', 'hard max 10000'). It does add some non-schema meaning, notably that formedFrom overrides daysBack and that maxResults caps billed businesses rather than returned rows only, but most parameter semantics are already carried by the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List newly formed Colorado LLCs, corporations and nonprofits') plus the exact source (Colorado Secretary of State open data on data.colorado.gov, updated daily) and the fields included. It explicitly contrasts itself with the Florida, Texas and New York siblings, so an agent can route between state-lead tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit positive targeting ('Use when banks, insurance, payroll, accountants, web agencies or suppliers want new Colorado owners in their first weeks') and explicit exclusions ('Do not use for other states, for emails or phones (the source has none) or for historical entity search'). Alternatives are named with their distinguishing data sources, which is exactly the when-not guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.