# Jev Job Posting Taxonomy — Classify Job Listings (`alaudinburki/jev-job-taxonomy`) Actor

Normalize supplied job postings into function, seniority, and remote-policy fields with TypeSafe Jev.

- **URL**: https://apify.com/alaudinburki/jev-job-taxonomy.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** AI, Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Jev Job Taxonomy

Normalise supplied job postings into a consistent function, seniority and remote-policy shape, so roles from different boards can be compared as one dataset.

It is part of the Jev family: **narrow, typed judgements on records you supply**, with the code
owning everything deterministic and the model owning only the judgement. Bring a TypeSafe API key
as a secret input for live judgements.

### What it does

- Assigns each posting a function.
- Infers seniority.
- Determines the remote policy.
- Keeps your `sourceId` on every row.

### What it does not do

Scoping this honestly is the point of the family, so it is stated plainly:

- It does not scrape job boards — you supply the postings.
- It does not apply to jobs.
- It does not contact anyone.

### Output fields

| Field | Description |
|---|---|
| `index` | Position of this row within the run. |
| `sourceId` | Your identifier for the posting. |
| `description` | The posting text that was judged. |
| `function` | The job function assigned. |
| `seniority` | The seniority level inferred. |
| `remotePolicy` | The remote policy described. |
| `judgments` | The full structured judgement. |
| `model` | Identifier of the model used. |

### Sample output

```json
{
  "index": 1,
  "sourceId": "job_9012",
  "description": "Senior Backend Engineer, remote (EU)",
  "function": "engineering",
  "seniority": "senior",
  "remotePolicy": "remote",
  "judgments": {
    "function": {
      "choice": "engineering"
    }
  },
  "model": "jev-latest"
}
```

### How it works

Each supplied record is turned into a question set and sent to the TypeSafe Jev model, which
answers with a choice, a score, or a probability. Those answers are mapped onto fixed output
fields, and every row carries the confidence of the judgements behind it.

`status` reports the outcome per row. When the minimum confidence falls below your threshold, or
the model's own uncertainty is high, the row is flagged for **review** rather than presented as a
settled answer. `minConfidence` records the weakest judgement that produced the row, so you can
see how close it was.

**Safe mode.** With no TypeSafe key the Actor sends nothing upstream and returns a single row with
`status: "no_api_key"` — a successful run that tells you exactly what to add, never a failed one.

### Pricing

Pay per event: you are charged per result written to the dataset, plus the near-zero start event.
In safe mode no judgements are produced, so the run is effectively free. Bring your own TypeSafe
key; you pay TypeSafe separately for the model calls.

### FAQ

**Does it need a TypeSafe key?**
For real judgements, yes — add it as a secret input. Without one it runs in safe mode and returns
`no_api_key` instead of guessing.

**Does it call any other service?**
No. It reads your supplied records and calls the Jev model. It does not fetch, scrape, crawl or
contact anything.

**What does `review` mean?**
The judgement was not confident enough to stand on its own. Treat those rows as needing a human,
not as answers.

**Can I tune the threshold?**
Yes. Raise the confidence threshold to get fewer, more certain results; lower it to see more rows
with more of them flagged for review.

**Is the output deterministic?**
The mapping and the fields are fixed. The model's judgement is probabilistic, which is why every
row carries a confidence and why low-confidence rows are flagged rather than hidden.

### Use cases

- Normalising multi-board job data into one shape.
- Comparing seniority mix across companies.
- Building filters that survive inconsistent posting formats.

### Related Actors

- **Job Change Monitor**
- **ATS Job Scraper**

### What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in
an answer or a comparison.

- Jev Job Posting Taxonomy declares all 8 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of Jev Job Posting Taxonomy include index, sourceId, description, function, seniority and remotePolicy.
- Jev Job Posting Taxonomy needs no API key, login or account of any kind before its first run.
- Every one of Jev Job Posting Taxonomy's 3 inputs is optional, so it runs with no configuration at all.
- Jev Job Posting Taxonomy documents `sourceId` as: Identifier of the input record this row came from.
- Every number published about Jev Job Posting Taxonomy is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- Jev Job Posting Taxonomy is filed under ai and jobs so that it is found by the people looking for that job, not by its internal name.

### Limitations

- Jev Job Posting Taxonomy reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
- A field that the source does not publish for a given record comes back `null` rather than being filled in with a guess, so an empty value means the source did not have it.
- Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
- This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.

# Actor input Schema

## `records` (type: `array`):

Rows containing a job description.

## `typesafeApiKey` (type: `string`):

Secret key used only for this run.

## `maxItems` (type: `integer`):

Hard cap on enriched rows.

## Actor input object example

```json
{
  "records": [
    {
      "description": "Senior backend engineer, remote in Europe."
    }
  ],
  "maxItems": 100
}
```

# Actor output Schema

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

One record per supplied job description, including typed Jev judgments.

# 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 = {
    "records": [
        {
            "description": "Senior backend engineer, remote in Europe."
        }
    ],
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/jev-job-taxonomy").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 = {
    "records": [{ "description": "Senior backend engineer, remote in Europe." }],
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/jev-job-taxonomy").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 '{
  "records": [
    {
      "description": "Senior backend engineer, remote in Europe."
    }
  ],
  "maxItems": 100
}' |
apify call alaudinburki/jev-job-taxonomy --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/jev-job-taxonomy"
        }
    }
}
```

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/MB6knmdWMbQfcW0jG/builds/lhfWutM39eiVW1llO/openapi.json