# O\*NET Occupation Skills & Software — Workforce Taxonomy Data (`nexgensignal/onet-skill-software-records`) Actor

Official O\*NET links between occupations and the skills and software they use — the taxonomy layer for skills graphs, job-matching and reskilling models.

- **URL**: https://apify.com/nexgensignal/onet-skill-software-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Jobs, Business
- **Stats:** 1 total users, 1 monthly users, 94.4% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 association records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## O\*NET Skill & Software Records — Occupation Associations

**Official source. No API key. Pay per record.**

### Who this is for and the decision it supports

HR-tech, workforce-planning, skills-taxonomy and job-matching teams who need the official O\*NET links between occupations and the skills and software they use.

One record answers: which skill or software tool is associated with an occupation, and how strongly — a building block for skills graphs, job-to-skill mapping, and reskilling models.

### What one record is

Each record is one occupation-to-element association: O\*NET-SOC code and title, the skill or software element, its class, scale/value, and hot-technology / in-demand flags.

### Your first run

Paste this input and run it:

```json
{
  "onetSocCodePrefix": "15-1252",
  "associationType": "software",
  "maxRecords": 10
}
```

Filter by an occupation code prefix and association type and get clean association rows immediately. Here is a real record from that exact input:

```json
{
  "record_id": "15-1252.00:software:2.E.4.d",
  "association_type": "software",
  "onet_soc_code": "15-1252.00",
  "occupation_title": "Software Developers",
  "skill_class": null,
  "element_id": "2.E.4.d",
  "element_name": "Word processing software",
  "scale_id": null,
  "data_value": null,
  "software_example": "3M Post-it App",
  "hot_technology": false,
  "in_demand": false
}
```

**What the sample costs:** $0.05 per record. The sample above delivers 10 records, so it costs at most **$0.50**.

### Pulling in bulk

Drop the filters and raise Maximum records to pull the whole occupation-skill-software matrix. A buyer pulls thousands of records to load the full occupation-to-skill/software matrix into a taxonomy or matching engine.

To expand from the sample: raise **Maximum records**, and widen any filters shown in the input. You are billed only for records actually delivered, so a sample stays cheap and a full pull is predictable.

### When to run it again

O\*NET republishes its database on a scheduled release; re-run after a new release to refresh the matrix.

**Update schedule:** O*NET publishes database updates on a regular release schedule (multiple updates per year in recent cycles). Verified live: association rows return with current O*NET element identifiers and hot-technology flags.

### How this is different

Occupation-to-skill/software associations from O\*NET specifically — distinct from job-posting feeds; this is the authoritative taxonomy layer, not live vacancies.

### Limitations (source coverage vs product coverage)

- This is the O\*NET taxonomy (occupation to skill/software), not live job postings or salaries.
- Coverage is US O\*NET-SOC occupations.
- Software examples are O\*NET's named examples, not an exhaustive tool inventory. Each software row is individually addressable: the record identity now includes the specific tool (Workplace Example), so different tools under one technology category are distinct records and exact duplicates are removed before delivery and billing.

### FAQ

**Is this job postings?**

No. It is the O\*NET occupation-to-skill/software taxonomy. For live vacancies use a job-postings feed.

**What is a Hot Technology?**

O\*NET's flag for software/technology in high employer demand; filter with hotTechnologyOnly.

**What does an empty run mean?**

No association matched your filters — widen the occupation prefix or association type.

### Related actors

- world-bank-project-records — development-sector programs
- eu-business-demography-records — firm demography for labour-market context
- company-data-enrichment-api — resolve employers to legal entities

### Source, licence and how it is built

Source and licence are carried on every record (`source`, `licence`, `attribution`, `observed_at`). The actor reads only the official public endpoint, honours the source's robots and licence terms, and emits values unmodified with full provenance. Records are keyed on a stable id so re-runs upsert cleanly into a table you keep. Row delivery and billing are exactly equal: you are charged once per record delivered (push-then-charge), so an empty run costs nothing.

Part of NexGen Signal — official-source data products.

# Actor input Schema

## `onetSocCodePrefix` (type: `string`):

Optional. Keep only occupations whose O\*NET-SOC code starts with these digits (e.g. 15 for computer/math, 15-1252, 29-1141.00).

## `associationType` (type: `string`):

Which associations to return.

## `elementContains` (type: `string`):

Optional. Keep only associations whose skill or software element name contains this text (e.g. Python, welding, negotiation).

## `hotTechnologyOnly` (type: `boolean`):

Software only: keep only technologies O\*NET flags as a Hot Technology.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "associationType": "all",
  "hotTechnologyOnly": false,
  "maxRecords": 10
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxRecords": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/onet-skill-software-records").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "maxRecords": 10 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/onet-skill-software-records").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxRecords": 10
}' |
apify call nexgensignal/onet-skill-software-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/onet-skill-software-records"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/klsVibJwjGjueGqu7/builds/wT5nMCtSVhcx9d0Zu/openapi.json