Agent workflow guide
Company hiring signals: recent job openings with evidence
A job posting can help an account-research agent choose its next investigation. It does not establish a hiring spike, a company's budget or actual buying intent. Use dates and source coverage before treating an opening as a current signal.
Choose the company hiring question you can answer
The Company Hiring Signals & Job Openings API checks one supplied company website for recently posted jobs with verifiable dates. It returns structured job evidence, source URLs, check times and coverage. Start with a company you already know; this service does not discover every hiring company in a country or industry.
For recruiting research, ask which supported openings were recently posted. For account qualification, preserve the job description evidence before drawing a separate inference about a department's needs. To measure change, save reports over time and compare equivalent sources and scopes. One snapshot cannot prove hiring acceleration.
Careers pages, ATS APIs or a structured hiring report?
| Approach | Useful when | Work still needed |
|---|---|---|
| Company careers page | You need to inspect one primary source manually. | Extract fields, distinguish dates, identify linked ATS sources and record evidence. |
| Direct ATS source | You know the provider and its company board identifier. | Handle provider-specific fields, date meanings, duplicates, errors and changing schemas. |
| Verified Hiring Signals report | Your agent needs one normalized report with evidence and explicit coverage. | Supply a company, authorize spending, validate the returned status and respect scope limits. |
Supported source handling includes linked Ashby, Greenhouse and Lever evidence where available. Support for a provider does not imply complete coverage for every company. See source and request limits before purchase. Browser-only, inaccessible, undated or unsupported sources can prevent a definitive answer.
Read job dates and coverage before acting
- Validate the report against the report JSON schema and confirm that the requested company matches.
- Inspect each job's date meaning and evidence URL. A page update date is not automatically its original publication date.
- Check coverage. A partial positive establishes the observed jobs, not a complete list of openings.
- Treat a complete negative as source-scoped. It is not proof that the company has no openings anywhere.
- Keep unknown separate from negative. Missing dates, blocked sources or timeouts must not silently become “not hiring.”
The recorded company example is an owner-funded release test with its original observation time. It demonstrates the output format; it is not a fresh check, an independent customer purchase or a current hiring claim.
Authorize a bounded report cost
The checked configuration charges $0.03 per eligible report, at most one event per run. Eligible outcomes include verified positives, partial positives and complete source-scoped negatives. Unknown and invalid results produce no report event. Platform usage is included under the checked configuration; recheck the Apify Actor's current price before execution.
One authorized company call can be capped at $0.03. Ten separately authorized company reports have an event ceiling of $0.30 at that price. This is a cost illustration, not a discount or an offer guaranteeing ten useful results. Do not retry run creation automatically after a network timeout: recover the existing run ID first.
Connect the report to your agent workflow
{
"company_website": "https://linear.app",
"lookback_days": 30,
"max_jobs": 5
}Use the copy-paste API and MCP instructions to inspect metadata, authorize one call, retrieve its report and validate the output. The Hiring API Markdown documentation contains the exact Actor name, price, status meanings and call arguments.
If the next task is finding a public business contact route for that same company, use the Website Contact Finder API as a separate bounded step. For another question, use the business intelligence capability selector. Each service needs its own spending authorization; none automatically performs outreach.