One job posting, in full
company_jobs is a $0.20 GET request on the Wuthering AI API. Read a single job listing, including its salary band where one is posted. It answers complete JSON, and a call that fails is not charged.
Endpoint
GET /v1/company_jobs
Price per successful call
$0.20
Failed calls
Not charged
curl 'https://wutheringai.com/v1/company_jobs?url=…&token=YOUR_TOKEN'
What does company_jobs return, and when should you call it?
Return one job listing with its title, location, seniority, employment type, full description, and posted salary where the employer published one.
Hiring is a company telling you where it is spending next, months before the product ships. A cluster of roles around one function is a roadmap leak; a posted salary is a hard number for what solving that problem is worth, which makes it a pricing anchor.
This reads ONE listing and takes that listing's own URL, of the form linkedin.com/jobs/view/<id>. There is no way to list a company's openings from its page, so find them first with your own web search (site:linkedin.com/jobs/view "Acme"), or with wuthering_web_search if you have none, and read the ones that matter. A company page URL is rejected outright.
Returns: job_title, location, seniority, employment_type, description, salary, posted date.
Use to infer strategy from behaviour rather than announcements. Don't use to size a company, which is wuthering_company_profile, and don't expect a list of every opening.
What parameters does company_jobs take?
company_jobs accepts 1 parameter, of which 1 is required. Array values are comma-separated on the query string.
| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | yes | URL of the job listing itself, of the form linkedin.com/jobs/view/<id>. Find it with your OWN web search first: `site:linkedin.com/jobs/view "Acme"` returns it directly. wuthering_web_search is the fallback if you have no search of your own, and is billed. Never construct a URL — a wrong one returns a dead page, not an error. |
Which playbooks call company_jobs?
7 of the research playbooks name company_jobs in their method. Each is free to read and says where in the sequence the call belongs.
- Is there real demand for this?Test an idea against the cheapest evidence that could kill it — search demand, sustained ad spend, posted salaries, and the words buyers use — and return a verdict with the number that decides it.
- Where is the unoccupied position in this category?Map the category around one domain as an idea maze — the forks it has already run, who took each branch, which walls are still walls and which have moved — then return the one open position with the offer that takes it: buyer, bundle, price metric and message, decided together.
- Who are we really up against?Work April Dunford's positioning sequence from public evidence: the alternatives a prospect would actually use, what only you do, the value that follows, who cares most, and the category that makes all of it obvious.
- What do we charge, and does the money work?Anchor price against what competitors actually charge and meter on, size willingness to pay from what the problem costs today, then run CAC, LTV and payback across three scenarios.
- Where do the next 1,000 customers come from?Score every plausible channel against the product's own characteristics, measure the reachable demand and the cost of entry for each, and commit to one with its CAC and its ceiling stated.
- Is this company actually growing?Read one company's trajectory from public evidence: branded demand year over year, the acquisition engine underneath it, whether that demand was earned or bought, and what payroll says ships next — then name the questions only a data room can close.
- What would prove us wrong?Turn a belief the plan depends on into an explanation that cannot be bent to fit any result, name the rival explanations that would produce the same evidence, and pay only for the observations that would come out differently under each.
Reference for company_jobs · last updated · published by Wuthering AI