Find companies by NAICS code

Filter on naics, then count the people you can reach. Sizing is free.

naics takes the code your list is already in. It goes from code to companies. It does not look up the code for one company you name.

The filter

Test the code before you build on it. In our runs on 2026-10-01, 4-digit codes such as 5411, 2362 and 7225 returned a count. 6-digit codes (541511, 541512, 722511, 621111) returned no number, only unsupported_filters.

Coverage is partial. Only companies with a NAICS code on file can match, so counts are far below an industry count. 5415 matched mostly one industry (Human Resources Services), not computer systems design. Read the industry facets in the count result before you export.

How many you can reach

Three live counts from leadocean_count_leads, run on 2026-10-01. They use industry, not naics, because naics counts are only partly supported by the counting tool. Each count is mailable people: verified, catch_all_valid or catch_all email, the tool's default. They spent no records.

These are people at matching companies, not a company count. They size the same markets that NAICS 5411, 2362 and 7225 describe, but the industry field is matched by name, not by code.

Need volume? Use industry instead. It reads a field most companies carry. See find companies by industry.

Run it from an AI agent

Connect the MCP server at https://api.leadocean.io/mcp (OAuth sign-in, no key pasted), then ask in plain words. The same steps work from VS Code.

Find owners and C-level people at US law firms with NAICS code 5411. Size it first, then show me 25.

The agent counts first with the free tool, then calls leadocean_search_leads with this:

{
  "naics": ["5411"],
  "jobLevel": ["C-Team"],
  "country": ["US"],
  "limit": 25
}

The search costs 1 record per person returned. Use leadocean_search_companies when you want companies, not people. It costs 1 record per company.

Run it with the API

One flat JSON body to POST /v1/people/search. Filters are arrays of strings.

curl -X POST "https://api.leadocean.io/v1/people/search" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "naics": ["5411"],
    "jobLevel": ["C-Team"],
    "country": ["US"],
    "limit": 25
  }'

For the free sizing call, put count=true in the URL (not the body) and set limit to 1.

curl -X POST "https://api.leadocean.io/v1/people/search?count=true" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "naics": ["5411"],
    "jobLevel": ["C-Team"],
    "country": ["US"],
    "emailStatus": ["verified", "catch_all_valid", "catch_all"],
    "limit": 1
  }'

data comes back empty and meta.countOnly is true. meta.total stops at 100,000 on the REST API. POST /v1/companies/search takes naics too.

Export the list

POST /v1/exports takes the same filters inside a filters object. One export is up to 50,000 rows, and an account can export 500,000 rows a day.

curl -X POST "https://api.leadocean.io/v1/exports" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "naics-5411-us-owners",
    "filters": {
      "naics": ["5411"],
      "jobLevel": ["C-Team"],
      "country": ["US"]
    },
    "limit": 1000,
    "preset": "search"
  }'

Poll GET /v1/exports/{id}, then download. Prefer clicking? The Exports page in the app at app.leadocean.io has the filter builder, a column picker, the record price before you start, and a CSV download.

Combine it

• Add jobFunction and jobLevel to reach one buyer, for example Finance & Accounting at ["Director"].
• Add employeeRange (for example ["11-50"]) to pick a company size. The second count above does this.
• Add industry next to naics to sanity-check a code. If the facets show an industry you did not expect, tighten the code or switch to industry.

More ways to build a company list are on the find companies hub.

FAQ