agdata

LinkedIn jobs API / Research workflow

See the roles.
Keep the evidence.

Give your agent a job title, location, and posting window. Use public LinkedIn job listings to build a hiring brief with links back to the source.

Build an unpaid requestRead the reference ↗
REST + MCPQuote before paymentNo service API key

A hiring signal you can inspect.

A job posting is evidence of an advertised role. It is not proof that a company is growing, that the vacancy is still open, or that a hire happened.

  1. Define the question

    Search by role, skill, or company. Narrow the location and posting window before requesting a quote.

  2. Review, then authorize

    Inspect the live quote. A compatible client signs only after the wallet owner approves the task and spending limit.

  3. Build the brief

    Group delivered listings by company or role. Keep source URLs; label missing fields and uncertain conclusions.

Start without a payment

Preview your first request.

This local builder only prepares an unsigned command. Running it yourself asks for a live quote. It does not sign, fund a wallet, or purchase data.

The live request schema allows up to 50 listings. Availability is not guaranteed.

UNSIGNED CURL / NO PAYMENT HEADER

A quote is not a completed purchase.

A valid unpaid request returns HTTP 402 with x402 and MPP payment challenges. Use an offered rail and a compatible signing client. A funded wallet and owner-approved limits are still required; no service account does not mean no setup.

After payment, inspect the result and receipt. If the paid response is uncertain, reconcile it before authorizing another payment.

What your agent could produce.

A compact research note, not an untraceable verdict.

  • Role and company grouping, with source links
  • Location and posting time where supplied
  • Missing fields and stale-listing caveats
  • Optional company context from a separate, quoted linkedin-company call

Use this for company and job-market research, not automated employment eligibility decisions or unsolicited candidate outreach.

Fictional downstream brief / Not an API response

Example Company A
Data-platform hiring research

Observation to support
Several advertised roles relate to data infrastructure.
Evidence to retain
Each job's URL, title, location, and source date when available.
What not to infer
Headcount growth, accepted offers, or a completed hire.

Illustrative copy only. No company or job data was fetched for this example.

Know the boundary.

One search is one quoted taskChanging the body changes the task. Company enrichment is a separate request and quote.

No usable resultsThe documented no-result policy is not to settle the lookup. A lost paid response still requires reconciliation.

A bounded sample, not the whole marketListing availability and returned fields can vary. Do not present a limited search as complete coverage.

REST or MCPUse the same task through the live API or MCP tool schema. A normal MCP connection alone does not supply a funded payment path.

Start with one useful question.

Get the request right before connecting a wallet.

Review the request