Wyoming SOS Business Registry — Filing & Agent Lookup

Search the Wyoming Secretary of State business filing registry (wyobiz.wyo.gov) by company name or exact filing ID. Returns the official filing record: entity type, current status and standing (tax / registered agent / other), formation jurisdiction, registered-agent name and address, principal/mailing addresses, and — when on file — officer/director records.

Typical use: verify a Wyoming-registered company's filing status and standing before doing business with it, find its registered agent for service of process, or build a list of active filings matching a name pattern.

Input

Field	Type	Default	Description
searchNames	string[]	["Grand Teton"]	Company/entity names to search. Each name is one search.
searchIds	string[]	[]	Exact Wyoming SOS filing IDs (format YYYY-NNNNNNNNN, e.g. 1980-000149890). Faster and unambiguous — use when you already know the ID.
searchMode	string	"contains"	"contains" = substring match anywhere in the name. "startsWith" = name must begin with the search text (fewer false positives).
maxResultsPerSearch	integer	20	Cap on matching filings returned per search term (a broad name can match hundreds of filings).
fetchDetails	boolean	true	Fetch each match's detail page for registered agent, addresses, and officers. If false, only the search-result summary fields are returned (one fewer request per filing).
maxItems	integer	100	Overall cap across all searches combined. 0 = unlimited.
proxyConfiguration	object	Apify Proxy, RESIDENTIAL, US	Standard Apify Proxy input. The actor works out of the box — no proxy key or credentials of your own are required.

At least one of searchNames / searchIds must be non-empty.

Output fields

One record per matched filing. Fields marked "detail" only populate when fetchDetails is true (default) and the detail-page fetch succeeds.

Field	Source	Description
search_query	input	The name/ID that produced this record
search_type	input	name or filingId
filing_id	search+detail	Wyoming SOS filing ID
entity_name	search	Official registered filing name
entity_type_code	search	Short type code (CORP, LLC, LP, LLP, TN, TM, …)
filing_type_full	detail	Full type description (e.g. "Limited Liability Company - Foreign")
sub_type	detail	Filing sub-type, when declared
status	search+detail	Current filing status (Active, Inactive - Withdrawal, …)
sub_status	detail	Current / Archived
standing_tax	search+detail	Annual license tax standing (Good/Delinquent)
standing_ra	search+detail	Registered-agent-on-file standing (Good/Delinquent)
standing_other	detail	Any other administrative-action standing
initial_filing_date	search+detail	Original filing date
effective_date	detail	Effective date, if different from filing date
inactive_date	detail	Date the entity became inactive, if applicable
duration	detail	Term of duration, if not perpetual
formed_in	detail	Jurisdiction of formation (Wyoming for domestic entities)
fictitious_name	detail	DBA name on file, if any
principal_office_address	detail	Principal office address
mailing_address	detail	Mailing address
registered_agent_name	detail	Registered agent name — see PII note below
registered_agent_address	detail	Registered agent address
officers	detail	Array of {name, title, address} — see coverage note below
officer_count	detail	Number of officer records found
latest_ar_number_year	detail	Latest annual report number / year
ar_exempt	detail	Annual-report exemption flag
license_tax_paid	detail	Most recent license tax amount paid
filing_detail_url	derived	Direct link to the filing's page on wyobiz.wyo.gov
efnum	search	Internal registry token for the filing (opaque, used to build filing_detail_url)
parse_confidence	derived	high / medium / low — see below

parse_confidence is high when the core search fields (name, filing ID) are present and the detail page enriched the record with a registered agent; medium when core fields are present but detail enrichment is missing or thin (e.g. fetchDetails: false); low if even the core search-row fields are missing (an unrecognized page shape).

PII disclosure

The registered agent field is a mandatory public disclosure under Wyoming law for every business entity on file — it exists precisely so the public and courts can identify who to contact or serve process on. For filings that use a registered-agent service company, this field is a business name. For filings where the owner serves as their own registered agent, this field is a natural person's name and address — the same public-disclosure pattern already present on this fleet's cslb-contractor-licenses actor (US state licensing-board registries). This is standard, already-public US Secretary-of-State data, not personal data collected from a private source.

Officer/director records (officers), when present, are also standard public SOS filings for domestic corporations. Wyoming does not require LLC member or manager disclosure (a well-known reason Wyoming is popular for privacy-conscious LLC formation) — so officers is structurally empty for the large majority of LLC filings, and populated mainly for domestic corporations. This is a registry-structure fact, not a parser gap: don't expect officer_count > 0 on an LLC record even when the detail fetch succeeds cleanly.

Charge event

This actor bills per matched filing record delivered:

• filing-record — charged once per record pushed to the dataset (whether or not officers populated for that record — the registered agent, status, and standing fields are the JTBD-critical payload on every record regardless of entity type).

Notes

• Search results are ordered as the registry returns them; pagination beyond the first page of a broad name search is not currently followed — narrow broad names with searchMode: "startsWith" or a tighter maxResultsPerSearch if you need a long tail.
• A filing-ID search (searchIds) is exact-match and unambiguous — prefer it whenever the filing ID is already known.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.