Skip to main content
Glama

Florida New Business Leads: New LLCs & Corporations Daily

florida_new_business_leads
Read-only

Find newly filed Florida LLCs, corporations, and nonprofits from Sunbiz daily data with addresses, officers, and industry guess. Target new owners or monitor competitors by city, ZIP, or industry.

Instructions

List newly filed Florida LLCs, corporations and nonprofits from the official Sunbiz (Division of Corporations) daily data files, with principal and mailing address, officers/managers, registered agent, FEI/EIN when filed and an industry guess from the name. Unlike texas_new_business_leads (Texas Comptroller franchise taxpayers) and local_business_leads (established shops on OpenStreetMap), this is brand-new Florida formations. Use when you sell to new business owners (bookkeeping, insurance, banking, web design, signage) or monitor new competitors in a Florida city or ZIP. Do not use for other states, for historical entity search or for annual-report status checks. Parameters: daysBack (work days only; max 62 days per run) or dateFrom/dateTo; cities and zipPrefixes match principal or mailing address; industries and nameKeywords match words in the name, excludeKeywords removes holding companies; newFormationsOnly (default true) skips reinstatements and old foreign entities; personAgentOnly keeps filings without an agent company (often owner-filed); maxResults caps billed businesses. Runs with no matches are free. Returns per item: agentSummary, documentNumber, name, filingType, filingTypeLabel, status, formedDate, filedOn, principalAddress, principalCity, principalZip, mailingAddress, mailingCity, mailingState, mailingZip, feiNumber, registeredAgent, registeredAgentType, officers, officerNames, industryGuess, sunbizUrl; plus BUSINESSES_XLSX (with Officers sheet)/CSV.

Behavior: read-only; runs the Apify Actor pandadad0214/florida-new-business-leads (https://apify.com/pandadad0214/florida-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": "florida_new_business_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesNoCities. Principal or mailing city, e.g. Miami, Orlando, Tampa, Jacksonville.
dateToNoFiled on or before. Optional YYYY-MM-DD.
dateFromNoFiled on or after. Optional YYYY-MM-DD; overrides days back. Up to 62 days per run.
daysBackNoFiled in the last N days. Default 7. Files exist for work days only. Use 1 on a daily schedule.
industriesNoIndustry guess. Guessed from words in the business name (e.g. ROOFING, REALTY, TRUCKING).
maxResultsNoMaximum results. You pay per business returned, so this also caps the cost. Default 1000.
filingTypesNoEntity types. Empty = all types.
zipPrefixesNoZIP prefixes. e.g. 331 (Miami), 328 (Orlando), 336 (Tampa), 33401.
nameKeywordsNoName contains (any). Comma-separated, e.g. roofing, cleaning, med spa.
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.
requireOfficerNoOnly with an officer or manager listed. Skip filings with no named officer, manager or member.
excludeKeywordsNoName excludes. Comma-separated, e.g. holdings, investments.
personAgentOnlyNoOnly when the registered agent is a person. Skips filings that use a registered-agent company, which usually means the owner filed directly.
run_timeout_secsNoOptional. Seconds to wait for results (default from PANDA_TIMEOUT_SECS, 120; max 300).
newFormationsOnlyNoOnly new formations. Skip filings for entities formed more than 45 days before the file date (e.g. reinstatements and old foreign entities). Future effective dates are kept.
run_max_charge_usdNoOptional. Hard spending cap for this call in USD (default from PANDA_MAX_CHARGE_USD, 0.50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the read-only/open-world annotations: per-business pricing ($0.0015), free runs on zero matches, a hard spend cap, item/timeout knobs, the interaction between run_max_items and maxResults on billing, and expected latency (5-15 s vs. minutes). This is exactly the operational context an agent needs to set parameters safely.

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 and organized as purpose, differentiation, usage, exclusions, parameters, behavior, return shape. It is dense and repeats a few schema facts, but nearly every clause carries information an agent would otherwise have to guess.

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?

For a 16-parameter, no-output-schema tool, the description enumerates the returned fields and the XLSX/CSV artifacts, plus the {actor, count, items} envelope and truncation behavior. Nothing material is left for the agent to discover at call time.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds real meaning by explaining that daysBack counts work days only with a 62-day ceiling, that excludeKeywords is meant to strip holding companies, and that raising maxResults above run_max_items can bill for more than is returned. A couple of items (dateFrom overrides daysBack) merely restate 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?

Opens with a specific verb and resource: 'List newly filed Florida LLCs, corporations and nonprofits from the official Sunbiz (Division of Corporations) daily data files,' and names the two most confusable siblings with their differing scope. An agent can route on this 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 concrete use cases (selling to new owners in bookkeeping, insurance, signage; monitoring new competitors by city/ZIP) and explicit exclusions ('Do not use for other states, for historical entity search or for annual-report status checks'). Alternatives are named alongside why they differ.

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