Business registration data from the secretary of state, in one schema
Business registration data is the cleanest public signal that a company exists. Every entity — LLC, corporation, LP, nonprofit — files with a secretary of state or an equivalent registry before it does anything else, and that filing stays on the record as it grows, renews, changes agents, or dissolves. Sales teams, compliance teams, and analysts all want the same thing from it: current, structured, and comparable across states.
That last part is the work. State registries disagree on entity types, status vocabularies, what officer information gets published, and how often filings post. Recordpipe collects secretary of state business data from the states you specify and normalizes it to one schema: entity name, type, jurisdiction, filing number, formation date, status, registered agent, and principal address as published. The state's own wording is kept next to the normalized value, so nothing is lost in translation.
Delivery is by file, API, webhook, or dashboard, one-time or on a daily or weekly cadence. The $500 scoping confirms what your target states publish and returns a sample within 5 business days.
New business filings and newly registered businesses, delivered daily
New business filings are where the commercial value concentrates. A newly registered business needs a bank account, insurance, payroll, a point of sale, a lease, and an accountant — and it needs them in the first weeks, when nobody else has called. A feed of newly registered businesses, delivered every morning, is the earliest legitimate signal a sales team can get.
Recordpipe delivers new filings as events: entity formed, foreign entity registered, DBA or assumed name filed where the state publishes it. Each row carries the formation date and a first-seen timestamp so you can measure the lag between filing and delivery yourself. The AI analysis layer filters shells and serial filers where you ask it to, dedupes the same entity across name variations, and ranks by the criteria you define — entity type, county, stated purpose, or registered agent category.
Contact points come as published in public filings: registered agent name and address, principal office address, and officer names where the state lists them. No scraped private contact data. Enrichment is your call, and its compliance is yours.
Corporate registry data: registered agent lists, officers, and status changes
Corporate registry data is not just formations. The record keeps changing after day one — annual reports, agent changes, mergers, name changes, administrative dissolutions, reinstatements — and each change is a signal for someone. A lender wants to know when a borrower's entity goes delinquent. A registered agent firm wants a registered agent list to see where appointments are moving. A KYB team wants to know the moment an entity's status flips.
Recordpipe tracks the entity, not the filing. One record per entity with a history of events and a current status, so your systems see a company's registry life in order rather than as a pile of disconnected rows. Officers and directors as published are versioned; when a state posts a new annual report, the previous slate is retained with dates.
Where you need it, the pipeline joins registry data to other public records Recordpipe already runs — professional licenses, UCC filings, liquor licenses, permits — keyed on the entity. That is what business entity data looks like when it is built for a workflow instead of a download.
A company registry API — or a file, a webhook, or a dashboard
A company registry API is the delivery format most engineering teams ask for first: query by name, filing number, or jurisdiction and get back the current record with its history. Recordpipe runs that as a managed service on your behalf — the pipelines, the normalization, the monitoring, and the API in front of it, all fixed-price. Teams that do not want to integrate get the same business filings data as a scheduled file drop, a webhook per event, or a dashboard their analysts can filter directly.
Uses that touch eligibility deserve a clear line. Registry data is raw public data, not a consumer report, and Recordpipe is not a CRA. Business verification, KYB, vendor onboarding, and underwriting workflows are common and usually straightforward, but any use case that affects a person's eligibility for credit, employment, housing, or insurance gets compliance review at intake.
Engagements are fixed-price from $5,000 to $3 million. Intake is a free form. Scoping is $500, credited to the contract. We reply to every inquiry within 2 business days.
What a delivery looks like
| Field | Description |
|---|---|
| entity_name | Legal name as registered, with prior names retained as history. |
| entity_type | LLC, corporation, LP, LLP, nonprofit, or DBA — normalized, with the state's own label kept alongside. |
| jurisdiction | State of formation or registration, and whether the entity is domestic or foreign there. |
| filing_number | The registry's own identifier — your verification path back to the source. |
| formation_date | Date of formation or first registration in that jurisdiction. |
| status | Active, delinquent, dissolved, revoked, or reinstated, normalized across states. |
| registered_agent | Agent name and address as published in the filing, with the principal office address delivered alongside. |
| officers_as_published | Officers, directors, members, or managers where the state lists them, versioned by report date. |
| event_type | What changed on this row: formed, annual report, agent change, name change, dissolution, reinstatement. |
| first_seen_at | When the filing or change entered your feed. |