Start with one role and one location

The public sample searches for contract software engineering work in the United States and saves one evidence-backed result. Inspect the source text before increasing the limit or changing the query.

{
  "queries": [
    "contract software engineer"
  ],
  "locations": [
    "United States"
  ],
  "datePosted": "",
  "maxResultsPerQuery": 1
}

Check the evidence, not just the label

Open the Dataset and compare classification, evidenceField, and evidenceText with the public source URL. Confirm that the job identity, company, location, date, and contract wording match the posting before exporting or automating it.

Billing boundaryComplete evidence-backed Dataset rows are billable. Unsupported matches, empty searches, failed or incomplete fetches, duplicates, and the free RUN_SUMMARY diagnostic are not billed.

Use the narrowest workflow for your question

Your questionBest starting point
Which jobs explicitly offer contract or freelance work?Use Contract Jobs Intelligence and inspect the direct evidence.
Which public jobs match a broad role and location?Use LinkedIn Jobs Search Scraper.
I already have exact job URLs or IDs.Use LinkedIn Job Details Scraper for complete records.
I need marketplace projects, budgets, or bid competition.Review the separately labelled freelance marketplace collection.

Automate only after the evidence holds

Save the tested input as an Apify Task, schedule a recurring run, send the Dataset to a webhook, or call the Actor through the API. Deduplicate on jobId between runs and keep source URLs with downstream records.

Hosted MCP endpoint: https://mcp.apify.com/?tools=neuton/linkedin-contract-jobs-intelligence

ChatGPT, Claude, n8n, Make, Zapier, Clay, and other clients can invoke the Actor through Apify after you set a bounded input and spending limit.

Frequently asked questions

Does it require a LinkedIn account?

No. It processes public job-posting surfaces without LinkedIn login credentials or cookies.

Does it guess whether a role is contract work?

No. A row is returned only when a public title, criterion, location, compensation field, or description directly supports the classification.

Can it find temporary and fixed-term roles?

Yes, when the public posting explicitly discloses temporary or fixed-term work. Unsupported classifications are excluded.

What should I run first?

Open the one-result contract software jobs Task, inspect its evidence and source URL, then edit the role, location, and limit.

Inspect one contract-job result

Start with the public Task and validate the exact evidence behind the classification.