ATS Hiring-Intent Lead Finder 📈

Turn a list of companies into ranked, hiring-intent sales & recruiting leads.

For each company you provide, this Actor pulls the current open roles straight from the company's official, keyless public ATS API — Greenhouse, Lever, or Ashby — then computes a hiring-intent score and plain-English buying signals from the role mix (e.g. "79 Sales roles open — active GTM / revenue expansion"). Add a domain and it also enriches the hiring company with verified business contacts (MX/DNS-validated emails, phones, socials, tech stack) so each result is a ready-to-use lead.

• ✅ No API keys, no login, no residential proxy — these are the ATS platforms' own public JSON endpoints, so there's no anti-bot fight and no upstream scraping cost.
• ✅ Three ATS providers, auto-detected: Greenhouse, Lever, Ashby.
• ✅ Hiring-intent scoring (0–100 + A–D grade) with human-readable buying signals.
• ✅ Optional verified-contact enrichment of the hiring company (reuses our verified-email engine).
• ✅ Clean, normalized, deduped output. Charged per successful company (one that actually returns open roles).

---

What you give it

A companies array. Each item can be any of:

Form	Example
provider:slug string	"lever:spotify", "ashby:ramp"
Careers-board URL	"https://jobs.lever.co/spotify"
Bare slug (all providers tried)	"stripe"
Object (recommended — enables contact enrichment)	{"provider":"greenhouse","slug":"stripe","domain":"stripe.com"}

Finding a company's ATS slug: it's in their careers-page URL — e.g. boards.greenhouse.io/stripe, jobs.lever.co/spotify, jobs.ashbyhq.com/ramp.

Optional inputs

• functionFilter — only return roles in these functions (e.g. ["Sales","Marketing"]).
• enrichContacts (default true) — fetch verified contacts when a domain is given.
• verifyEmails (default true) — MX/DNS-validate the best email.
• concurrency (1–10, default 5).

---

Real-run sample (verified live, 2026-07-10)

Input:

{ "companies": [
  { "provider": "greenhouse", "slug": "stripe", "domain": "stripe.com" }
] }

Output (one record per company):

{
  "company": "stripe",
  "atsProvider": "greenhouse",
  "domain": "stripe.com",
  "totalOpenRoles": 509,
  "openRolesByFunction": {
    "Engineering": 118, "Sales": 79, "Data/AI": 18,
    "Marketing": 37, "Customer Success": 44, "Other": 96, "...": "..."
  },
  "hiringIntentScore": 100,
  "hiringIntentGrade": "A",
  "signals": [
    "79 Sales roles open — active GTM / revenue expansion",
    "37 Marketing roles open — demand-gen investment",
    "136 Engineering/Data roles open — scaling product & headcount",
    "509 total openings — high-growth / well-funded signal"
  ],
  "leadGrade": "A",
  "contacts": {
    "emails": ["press@stripe.com"],
    "emailVerified": true,
    "phones": [],
    "socials": { "twitter": "https://twitter.com/stripe", "linkedin": "https://linkedin.com/company/stripe" },
    "techStack": ["Cloudflare", "React", "Google Analytics"]
  },
  "openRoles": [
    { "provider": "greenhouse", "companySlug": "stripe", "jobId": "7954688",
      "title": "Account Executive, AI Sales (Grower)", "department": "Sales",
      "function": "Sales", "location": "San Francisco, CA", "remote": false,
      "url": "https://stripe.com/jobs/search?gh_jid=7954688",
      "updatedAt": "2026-06-26T17:05:44-04:00" }
  ]
}

The contacts block is illustrative of the enrichment shape; exact values depend on what each company publishes on its own site at run time. The ATS role data (counts, titles, functions, signals) is pulled live from the official board.

Also verified live the same day: lever:spotify → 103 open roles, intent A; ashby:ramp → 126 open roles, intent A. All three providers returned clean, non-empty data.

---

Output schema (per company)

Field	Type	Meaning
company	string	ATS slug you supplied
atsProvider	string	greenhouse | lever | ashby (auto-detected)
domain	string | null	domain you supplied (for enrichment)
totalOpenRoles	int	number of currently open, listed roles
openRolesByFunction	object	role counts by business function
hiringIntentScore	int (0–100)	volume + weighted GTM/eng expansion signals
hiringIntentGrade	A–D	banded intent
signals	string[]	plain-English buying signals
contacts	object | null	verified emails, phones, socials, tech stack
leadGrade	A–D	intent blended with contact reachability
openRoles	object[]	normalized roles (title, department, function, location, remote, url, updatedAt)

Only companies that return at least one open role are pushed and billed.

---

Pricing

Pay per result — you're charged only for companies that actually return hiring data.

Event	Price	When
Hiring-Intent Lead (primary)	$0.008	once per company with ≥1 open role + intent score
Contact-Enriched Lead	$0.004	when the company is also enriched with ≥1 verified email
Actor start	$0.0001	one-time per run

No upstream scraping/compose cost — direct calls to official public ATS APIs, so the primary event sits comfortably above per-run compute.

---

Why this beats the alternatives

Existing "multi-ATS job scraper" actors are tiny and unrated, and they stop at a raw job feed. This Actor is the only one that turns those postings into a scored, contact-enriched lead — hiring-intent signals + verified contacts of the hiring company, clean and deduped, at one transparent per-success price. MCP-ready for agent workflows ("who's hiring for Sales right now, with a way to reach them").

Troubleshooting

Symptom	Cause / fix
No open roles found for X	Wrong slug or the company isn't on that ATS. Check their careers URL for the exact slug, or pass provider:slug. Some companies migrate between ATS platforms.
Empty contacts	No domain supplied, or the site blocked a plain fetch. Contacts are best-effort and never block the lead.
Fewer roles than the careers page shows	We return listed, public roles only (Ashby isListed, Lever public postings).
Lever returns "Document not found"	That company isn't on Lever (or changed slug); try a bare slug to auto-detect the provider.

Data source & compliance

Data comes exclusively from the ATS providers' own official public job-board APIs (Greenhouse boards-api, Lever postings API, Ashby posting-api) — the same endpoints that power the companies' public careers pages. No login, no scraping of gated content.