Facio
Facio Industry Classification API

Business classification,answered by API.

Turn a free-text business description into ranked U.S. SIC and NAICS codes—with complete hierarchy, calibrated confidence, alternatives, and source metadata in structured JSON.

Classify business activities—not just keywords.

Classification console
Illustrative API response

Do not enter confidential or personal information in this public demo.

This preview demonstrates the response structure; it is not connected to the production classifier.

CLASSIFIED312 ms · accurate mode

SIC 1987

6411

Insurance Agents, Brokers, and Service

NAICS 2022

524210

Insurance Agencies and Brokerages

Confidence

High · 0.97

Auto accept
View full hierarchy

H · Finance, Insurance, and Real Estate

64 · Insurance Agents, Brokers, and Service

52 · Finance and Insurance

5242 · Agencies, Brokerages, and Other Insurance Related Activities

REST + JSONU.S. SIC 1987NAICS 2022Confidence + alternativesBuilt for insurance

The input problem

Free text is messy. Your workflow does not have to be.

Applicants and brokers describe the same business in completely different ways. Facio interprets the activity behind the words, compares it with versioned taxonomies, and returns structured data your workflow can use immediately.

01

Inconsistent input

“Consulting,” “software services,” and “IT solutions” can describe very different establishments. Keyword matching is not enough.

02

Legacy mappings

SIC and NAICS are different systems with versioned, often many-to-many relationships. Facio preserves the distinction.

03

Unclear decisions

A single code hides ambiguity. Confidence and alternatives show what can automate—and what needs review.

Structured intelligence

Turn a business description into SIC and NAICS codes.

Use one REST endpoint to transform unstructured business activity into normalized industry data, complete hierarchy, confidence, and traceable source versions.

Natural-language classification

Send the language your customer already uses. Facio identifies the primary activity, business model, products, services, and qualifiers.

Complete hierarchy

Receive the selected code and every parent level—from SIC division to industry and from NAICS sector to national industry.

Ranked alternatives

When more than one classification is plausible, see the leading candidates and the distinction between them.

Calibrated confidence

Use confidence bands and review reason codes to govern straight-through processing and referrals.

Versioned and auditable

Every response records the taxonomy, crosswalk, classifier, and configuration versions that produced it.

No invented codes

Facio selects from governed taxonomy records and asks for more context when the description is insufficient.

How it works

From applicant language to governed industry data.

01

Understand the activity

Separate the primary business activity from products, customer type, business model, and secondary activities.

02

Retrieve official candidates

Search versioned SIC and NAICS records using lexical and semantic evidence, then compare the strongest candidates.

03

Return a governed decision

Return the best match, hierarchy, alternatives, confidence, warnings, and sources—or an explicit request for context.

Response anatomy

More than a code.

A classification is only useful when your system understands why it was selected, where it sits in the hierarchy, and how certain the result is.

All codes are returned as strings, preserving leading zeroes and official formatting.

response.fields

primary.sic.code6411
primary.sic.hierarchy4 levels
primary.naics.code524210
primary.naics.hierarchy5 levels
primary.confidence0.97 · high
primary.relationshipmany_to_one
alternatives[]
review.requiredfalse
warnings[]
versionstaxonomy + classifier

Insurance workflows

A SIC code API built for underwriting.

Move from unstructured intake to consistent data without losing the original description, uncertainty, or audit trail.

01

Quote intake

Normalize the applicant’s own description before the risk reaches an underwriter.

02

Appetite & routing

Trigger questions, route submissions, or apply appetite rules with confidence thresholds.

03

CRM & bordereaux

Standardize legacy free-text records for consistent reporting and integrations.

04

KYB & onboarding

Enrich onboarding data while preserving source text and classification provenance.

05

Renewal cleanup

Reclassify historical descriptions through a reproducible, versioned process.

06

Portfolio analytics

Aggregate exposure by SIC division, NAICS sector, or leaf industry.

Governed automation

Automate when the evidence is strong. Review when it is not.

Facio does not force every input into a code. It distinguishes activity from occupation, exposes one-to-many relationships, and returns an explicit review state when evidence is incomplete.

  • Versioned source data
  • Candidate-constrained classification
  • Calibrated confidence bands
  • Alternatives and reason codes
  • Crosswalk provenance
  • Versions in every response
Review required

“Project manager”

An occupation is not enough to classify an establishment. What products or services does the business provide?

Developer experience

One request. A complete classification response.

A predictable REST interface with JSON schemas, idempotent requests, versioned endpoints, and operational metadata.

REST + JSON

Predictable request and response contracts for modern application stacks.

Schema-first docs

OpenAPI definitions, typed examples, and clear error responses.

Auth & controls

API keys or OAuth, tenant quotas, and rate-limit headers.

Versioned results

Reproduce a result with the returned taxonomy and classifier versions.

{
  "status": "classified",
  "primary": {
    "sic": {
      "code": "6411",
      "title": "Insurance Agents, Brokers, and Service"
    },
    "naics": {
      "code": "524210",
      "title": "Insurance Agencies and Brokerages"
    },
    "confidence": {
      "score": 0.97,
      "band": "high",
      "decision": "auto_accept"
    },
    "relationship": "many_to_one"
  },
  "review": { "required": false },
  "alternatives": [],
  "versions": {
    "classifier": "classifier_1.0.0",
    "US_SIC_1987": "sic_1987_facio_2026_08_001",
    "US_NAICS_2022": "naics_2022_facio_2026_08_001"
  }
}

Taxonomy clarity

SIC and NAICS are related—not interchangeable.

U.S. SIC remains common in insurance, finance, and legacy datasets. NAICS is the current North American statistical standard. Facio classifies both systems independently and returns relationship provenance.

SystemSICNAICS
Facio taxonomy IDUS_SIC_1987US_NAICS_2022
Leaf code4 digits6 digits
Top levelDivisionSector
Typical roleLegacy and industry workflowsCurrent U.S. statistical classification
RelationshipOften one-to-many or many-to-manyOften one-to-many or many-to-many
Taxonomy versions and crosswalks

FAQ

Questions, classified.

01What does the SIC & NAICS Classification API do?

It converts a free-text description of business activity into ranked U.S. SIC and NAICS classifications, including hierarchy, confidence, alternatives, review status, and version metadata.

02Can I find a SIC code from a business description?

Yes. Send the description your applicant, broker, or customer already uses. The API interprets the primary activity and compares it with governed SIC records instead of requiring an exact manual keyword.

03Can the API convert a business category to a SIC code?

Yes, when the category describes what the establishment primarily does. Details such as products, services, and customer type can improve the result.

04Does the API return NAICS as well as SIC?

Yes. Facio can return both U.S. SIC 1987 and U.S. NAICS 2022, including their separate hierarchies and relationship provenance.

05Is SIC-to-NAICS mapping one-to-one?

Not necessarily. The systems were designed differently, and relationships can be one-to-many or many-to-many. Facio preserves that ambiguity.

06What happens when a description is ambiguous?

The API can return ranked alternatives, lower the confidence band, request more context, or mark the result for human review.

07Does the model invent SIC or NAICS codes?

No. The workflow selects from versioned taxonomy records and validates identifiers before returning them.

08Is the API designed for insurance underwriting?

Yes. Response fields support intake normalization, appetite routing, referral rules, portfolio reporting, and human review.

09Which input languages are supported?

The initial release is designed for English and Hebrew input. Additional languages can be introduced as versioned capabilities after evaluation.

Turn business language into underwriting-ready data.

Add governed SIC and NAICS classification to intake, underwriting, onboarding, and portfolio workflows through one API.

Tell us about your workflow, expected volume, and the taxonomies you need.