onet-match

io.github.Benjamin-V-ChanPublished by GitHub account Benjamin-V-Chanv0.3.5Updated Nov 1, 2026

Occupation classifier: free text to ranked O*NET-SOC codes with tasks, skills and RIASEC. Local.

The publisher's own server: match.bot

Overview

AI-generated overview

Local MCP server that maps free-text job titles, resumes or skill lists to ranked O*NET-SOC occupations with tasks, skills and RIASEC interests.

What you can do
  • Match occupations: turn free text about work into ranked O*NET-SOC codes with calibrated confidence
  • Look up occupations: fetch details for a given SOC code, including tasks, skills, knowledge and RIASEC interests
  • Return enriched profiles: each match carries major group, job zone, description and confidence-weighted skill and interest aggregates
When to use it
Useful when an assistant needs to normalize messy job titles or postings, code resume bullets and skill lists to standard occupations, or ground career-exploration and workforce-planning answers in O*NET data instead of free generation.
Requirements
Runs locally over stdio, typically launched with uvx from the onet-match package (or pip install with the mcp extra). No API key or account is needed for matching. The first call downloads a model bundle of about 0.5 GB from the Hugging Face Hub and caches it, so network access is needed once.
Before you install
The first run downloads a large model bundle from the Hugging Face Hub. Matching is statistical: the served model ranks the right occupation first about half the time on O*NET text, so results should be reviewed rather than treated as authoritative. The MCP tools are read-only; the separate O*NET Web Services search needs a free O*NET account.

Installation

In SourceWeft

  1. Open onet-match in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

onet-match

[PyPI] [DOI] [MCP Registry] [Demo]

Occupation classification and job-title normalization against the O*NET-SOC taxonomy. onet-match turns messy, unstructured text about work (job titles, resume bullets, job postings, project descriptions, interest statements, skill lists) into standardized SOC codes with a fine-tuned retrieve-and-rerank transformer pipeline. On held-out O*NET text it ranks the right occupation first 51% of the time, against 21% for a TF-IDF baseline, and 65% vs 17% on messy, human-style inputs. Each result is enriched with O*NET tasks, skills, knowledge and RIASEC interests, and comes with a calibrated confidence. Use it from Python, the command line, a REST API or any MCP-compatible agent, with no API keys.

  • Try it in your browser: no install, and the model runs on your device.
  • Open source (MIT) and runs locally. No API key or account needed to match.
  • Fine-tuned bge-base bi-encoder + cross-encoder reranker over all 923 O*NET 31.0 occupations. About 47 ms per query on a laptop.
  • Python API, CLI, REST API (FastAPI), MCP server for AI assistants, and Docker.
  • Also includes the O*NET data pipeline it's built on: bulk database download, a Web Services client and analysis tools.
use caseinputtop match (confidence)
Career explorationdesigned our robot in CAD and wired its circuits for my high school robotics teamRobotics Engineers, 17-2199.08 (0.38); #2 Robotics Technicians
Career explorationI love weather, maps and tracking stormsAtmospheric and Space Scientists, 19-2021.00 (0.87)
Skills-based hiringMust know survival analysis, R, SAS and clinical trial dataBiostatisticians, 15-2041.01 (0.60)
Skills-based hiringMust know Solidity, smart contracts and EthereumBlockchain Engineers, 15-1299.07 (0.81)
Resume parsingLed a team of 12 nurses on a cardiac ICU night shiftCritical Care Nurses, 29-1141.03 (0.42); #2 Acute Care Nurses
Resume parsingExcel, QuickBooks, payroll, AP/ARPayroll and Timekeeping Clerks, 43-3051.00 (0.49)
Career counselingskills: Python, SQL, Tableau; interests: sports statisticsStatisticians, 15-2041.00 (0.59)
Job-posting normalization{"title": "Wind Turbine Tech", "requirements": ["climbing", "hydraulics", "electrical troubleshooting"]}Wind Turbine Service Technicians, 49-9081.00 (0.81)

Real outputs of the served model, saved in outputs/examples/readme_examples.json.

Quickstart

bash
pip install "onet-match[matching]"
python
from onet_match import match
result = match("Must know survival analysis, R, SAS and clinical trial data", top_k=5)for m in result.matches:    print(m.soc, m.title, m.confidence)print(result.profile["riasec_code"])      # aggregate interest code, e.g. "ICS"

The package imports as onet_match and provides the onet-match command. The first call downloads the pretrained model bundle (about 0.5 GB) from the Hugging Face Hub (BenjaminChan12/onet-match) and caches it.

bash
onet-match match "Excel, QuickBooks, payroll, AP/AR"          # CLI (add --json for JSON)pip install "onet-match[matching,serve]"onet-match serve --port 8000                                   # REST APIcurl -s localhost:8000/match -H 'content-type: application/json' \     -d '{"text": "I love weather, maps and tracking storms", "top_k": 3}'

REST routes: POST /match, POST /match/batch, GET /occupation/{soc} and GET /health. The full request and response contract and the Docker setup are in docs/API.md.

Use from AI assistants (MCP)

onet-match mcp runs a Model Context Protocol server with two read-only tools: match_occupations(text, top_k) and get_occupation(soc). Add it to any MCP client (Claude Desktop, Cursor, VS Code and others):

json
{  "mcpServers": {    "onet-match": {      "command": "uvx",      "args": ["--from", "onet-match[mcp]", "onet-match", "mcp"]    }  }}

Without uv, run pip install "onet-match[mcp]" and use "command": "onet-match", "args": ["mcp"]. For a remote server, use onet-match mcp --transport streamable-http --port 8001.

What each match contains

soc, title, confidence (calibrated, 0–1), score, major_group and its title, job_zone, riasec_code, description, top_tasks, top_skills and top_knowledge (with O*NET importance and level). Each result also carries a profile that aggregates skills, knowledge and all six RIASEC interests across the matches, weighted by confidence.

Use cases

  • Career exploration (EdTech). Map what students say they did or enjoy to occupations and skills.
  • Resume and profile parsing. Code experience bullets and skill lists to SOC codes.
  • Skills-based hiring and workforce planning. Turn a list of required skills into the roles that use them, to scope a job or find adjacent talent.
  • Job-posting normalization. Turn informal titles and descriptions into standard occupations.
  • Workforce and labor-market analytics. Batch-code large text collections.
  • Career counseling tools. Show the tasks and skills behind a suggestion.
  • LLM agents. Ground occupation questions in O*NET instead of free generation (see llms.txt).

Worked example: onet-match-job-postings codes 3,000 LinkedIn job postings and compares pay by occupation group.

Details and integration patterns: docs/APPLICATIONS.md.

Accuracy

All models are evaluated on the same held-out splits. Every number traces to a saved run in outputs/runs/.

modelO*NET test top-1O*NET test top-5messy-text test top-1messy-text test top-5p50 latency
TF-IDF baseline20.5%40.5%17.4%39.2%0.5 ms
BM2520.7%40.1%24.1%45.2%0.2 ms
bge-base-en-v1.5, off the shelf36.1%64.3%45.4%77.6%6.9 ms
fine-tuned bge-base50.2%78.2%65.2%92.6%6.8 ms
fine-tuned bge-base + reranker (served)51.1%79.1%65.4%92.9%46.7 ms
  • O*NET test: 6,792 held-out titles, task statements, work activities and descriptions.
  • Messy-text test: 4,703 informal snippets written by a different LLM than the one that wrote the training text.
  • Confidence: temperature-calibrated, ECE 0.037.
  • Full results: per-input-type tables, calibration, ablations, learning curves and error analysis are in docs/RESULTS.md.

How it works

mermaid
flowchart LR    B["O*NET 31.0 database<br/>(bulk download)"] --> C["Occupation catalog<br/>923 occupations"]    C --> P["Labeled pairs<br/>titles · tasks · activities"]    C --> S["LLM-written messy text<br/>train: model A · test: model B"]    P --> T["Fine-tune bi-encoder<br/>+ cross-encoder reranker"]    S --> T    T --> BU["Model bundle<br/>(Hugging Face Hub)"]    BU --> API["match() · onet-match CLI · REST API"]
  1. A fine-tuned bi-encoder (bge-base) embeds the input and retrieves the 20 nearest occupations.
  2. A fine-tuned cross-encoder rescores those 20.
  3. The two scores are blended with a weight chosen on validation data.
  4. A temperature-scaled softmax turns the blended scores into calibrated confidence.

The validation and test tasks are removed from the occupation documents the models search, so no test text leaks into retrieval. Synthetic training and test text come from different LLMs.

In-browser demo

The demo Space runs the same pipeline client-side with transformers.js: both models are exported to ONNX and quantized to int8 (about 130 MB, cached after the first visit). demo/build.py builds it from a bundle. Quantization and the browser runtime shift results slightly: on 800 test queries the browser picks the same top match as the Python package 95% of the time, with top-1 accuracy 61.5% vs 62.6% (outputs/demo/browser_parity.json). Use the Python package for anything that matters.

O*NET data pipeline

The onet_data_collector package (onet-collect) downloads and verifies O*NET database releases, which needs no credentials. It also wraps O*NET Web Services: keyword search, occupation details and flattened profiles. See docs/COLLECTOR.md.

bash
onet-collect bulk download                         # download + verify the latest O*NET databaseonet-match collect "healthcare" "technology"       # Web Services search (free O*NET account, see .env.example)onet-match eda | keywords | cluster                # classic analysis: coverage, keyword attribution, TF-IDF clusters

Train your own

bash
git clone https://github.com/Benjamin-V-Chan/onet-match && cd onet-matchpip install -e ".[dev]"onet-match matching build-data          # O*NET catalog, labeled pairs, splitsscripts/matching/reproduce.sh           # every model, ablation and the results reportonet-match matching bundle "<spec>" --run <run>   # package a model for serving
  • Synthetic text: WITH_SYNTH=1 TRAIN_LLM=<model> EVAL_PROVIDER=<provider> EVAL_LLM=<model> scripts/matching/reproduce.sh also generates the messy training and test text, using a different LLM for each. It needs LLM API keys in environment variables.
  • Training time: bge-base took 58 minutes for one epoch on a laptop GPU (Apple Silicon, MPS). The exact scripts behind every saved run are in scripts/matching/.
  • Tests: pytest runs fully offline, using tiny local models and a mocked LLM.

Set ONET_MATCH_BUNDLE=/path/to/bundle to serve your own model, or ONET_MATCH_HF_REPO=owner/repo to load one from the Hub.

Background

This project was originally built in 2024 as an open-source edtech tool for analyzing O*NET occupational data at scale, and as part of my capstone project for an engineering course. Its analytics pipeline (EDA, occupation clustering, and keyword attribution) was later integrated into production products at Project Leo, and has inspired related work at other companies and projects.

In 2026 it was rebuilt around semantic occupation matching, and the former ONET-Data-Collector repository was merged in.

Citation

bibtex
@software{chan_onet_match,  author = {Chan, Benjamin},  title  = {onet-match: mapping free text to O*NET occupations},  url    = {https://github.com/Benjamin-V-Chan/onet-match},  doi    = {10.5281/zenodo.23824326},  year   = {2026}}

License and data attribution

The code is MIT-licensed; see LICENSE.

This product includes information from the O*NET 31.0 Database by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), used under the CC BY 4.0 license. O*NET® is a trademark of USDOL/ETA. USDOL/ETA has not approved, endorsed or tested this product.

Source: README.md at commit c635b7a

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

3
  1. v0.3.5LatestNov 1, 2026
  2. v0.3.4Nov 1, 2026
  3. v0.3.2Oct 30, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Match integrations