# JobPosting JSON-LD Normalizer (`ajver-lab/jobposting-jsonld-normalizer`) Actor

Normalize public job-posting URLs with Schema.org JobPosting JSON-LD into consistent, deduplicated structured data for recruiting pipelines, agent workflows, and market research. Public URLs only; no login bypass or private-data access.

- **URL**: https://apify.com/ajver-lab/jobposting-jsonld-normalizer.md
- **Developed by:** [Anthony](https://apify.com/ajver-lab) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

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

## JobPosting JSON-LD Normalizer

Normalize public job pages that expose Schema.org JobPosting JSON-LD into consistent dataset rows.

### Output

Source URL/domain, identifier, title, company, dates, employment type, remote/location fields, locations, salary, cleaned description, and a deterministic dedupe key.

Pages without JobPosting JSON-LD return status `no_jobposting_jsonld`; fetch failures return `error`.

### Uses

Job-board aggregation, recruiting pipelines, autonomous job-search agents, deduplication, and structured market research.

### Monetization

Designed for pay-per-event pricing: one event per normalized page result. No external AI API required.

### Scope

Public URLs only. No login bypass, hidden/private data access, or access-control circumvention.

# Actor input Schema

## `startUrls` (type: `array`):

Public job pages to normalize.

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

Maximum number of URLs to process in one run.

## `includeRawJsonLd` (type: `boolean`):

Include the original JobPosting JSON-LD object in each successful output row.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://example.com/job"
    }
  ],
  "maxItems": 100,
  "includeRawJsonLd": false
}
```

# Actor output Schema

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

Default dataset containing one normalized row per processed public job page.

# 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 = {
    "startUrls": [
        {
            "url": "https://example.com/job"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ajver-lab/jobposting-jsonld-normalizer").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 = { "startUrls": [{ "url": "https://example.com/job" }] }

# Run the Actor and wait for it to finish
run = client.actor("ajver-lab/jobposting-jsonld-normalizer").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 '{
  "startUrls": [
    {
      "url": "https://example.com/job"
    }
  ]
}' |
apify call ajver-lab/jobposting-jsonld-normalizer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ajver-lab/jobposting-jsonld-normalizer"
        }
    }
}
```

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/Ue1ZYLb0sPx2Ocibd/builds/coljIuHiLEzTzrxm6/openapi.json