@pipeworx/ats-boards

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/ats-boards’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

Public job-board postings across eight applicant-tracking systems (Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee, BambooHR, Workday, Workable) — detect which ATS a company publishes its careers page on, then read any company’s open roles without a key. This is NOT the greenhouse/ashby packs, which read the caller’s OWN private hiring data with their own API key; this pack reads the same public board any browser can see, for any company.

Tools

• ats_detect(domain | careers_url) — find which ATS a company uses and its board token, by scraping the careers page for an ATS link and, failing that, slug-probing the domain name against each board API. Persists the discovery so a repeat lookup for the same domain is instant.
• ats_jobs(ats, board_token, filters?) — normalized job postings for a board you already have ats + board_token for. Distinguishes an unknown board (found:false, reason:"board_not_found") from a real board with zero current postings (found:true, jobs:[]) for every ATS except SmartRecruiters, which cannot tell them apart (see below) — that case is marked ambiguous:true instead of guessing.
• ats_company_jobs(domain, filters?) — ats_detect + ats_jobs in one call.
• ats_new_postings(ats, board_token, since?) — diffs current postings against the last snapshot taken for that board. The first call for a board has no prior snapshot, so it returns every current posting as new (snapshot_bootstrap:true) instead of a misleadingly empty diff.

Auth

Keyless. Every endpoint below is the same public board data a browser sees on a company’s own careers page — no account, token or registration on any of the eight ATS vendors.

The one exception is Workable: its public widget is currently blocked by Cloudflare from this platform’s edge (see “Data sources” below) — not an auth wall, a transport failure. ats_jobs/ats_company_jobs throw a loud error naming the HTTP 429 and Cloudflare’s block when asked for ats:"workable", rather than returning an empty result.

Data sources

• https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=true — Greenhouse’s public board API.
• https://api.lever.co/v0/postings/{board_token}?mode=json (https://api.eu.lever.co/... for filters.region:"eu") — Lever’s public postings API.
• https://api.ashbyhq.com/posting-api/job-board/{board_token}?includeCompensation=true — Ashby’s public job-board API (officially documented, includes comp bands where the employer publishes them).
• https://api.smartrecruiters.com/v1/companies/{board_token}/postings — SmartRecruiters’ public postings API.
• https://{board_token}.recruitee.com/api/offers/ — Recruitee’s public offers API.
• https://{board_token}.bamboohr.com/careers/list — BambooHR’s public careers-widget endpoint.
• https://{tenant}.wd{N}.myworkdayjobs.com/wday/cxs/{tenant}/{site}/jobs (POST) — Workday’s public CXS jobs search. board_token encodes all three path parts as "{tenant}.wd{N}/{site}", e.g. "workday.wd5/Workday" (read the tenant/wd-number/site straight off the company’s own myworkdayjobs.com careers URL).
• https://apply.workable.com/api/v1/widget/accounts/{board_token} — Workable’s public widget API. Currently unreachable from this platform’s edge, confirmed live via a throwaway wrangler dev --remote Worker on Pipeworx’s production Cloudflare account: every one of 5+ attempts (two endpoint shapes — the v1 widget and the v3 /api/v3/accounts/{account}/jobs, with and without an Accept header, against several real account names, several minutes apart) returned HTTP 429 with Content-Type: text/plain and body error code: 1015 — Cloudflare’s OWN bot-mitigation, not a Workable application response. That reads as apply.workable.com’s Cloudflare WAF specifically rate-limiting Cloudflare-Worker-to-Cloudflare traffic. The adapter is implemented per Workable’s documented widget shape and is ready the moment this changes; until then every live call throws loud, naming the 429, rather than returning an empty board.

The silent-zero shape, per ATS (each measured live, not assumed from docs)

Each ATS answers “no such board” differently, and three don’t distinguish it from “real board, zero jobs right now” at all:

Treating any non-200 as “zero jobs,” or SmartRecruiters’ totalFound:0 as a confirmed empty board, is the exact silent-zero failure this pack exists to avoid — see the header comment in src/index.ts for the full edge-probe evidence (status/length/first-400-bytes) behind every row above.

Persistence (KV, not module scope)

The gateway injects its shared KV namespace as _cacheKv (injectCacheKv in pack-manifest.json), used for three things, each dated and each degrading cleanly to a live fetch if the binding is absent:

1. A whole-board job-list cache, ~3h TTL — “poll each board no more than every few hours.”
2. The domain -> {ats, board_token} discovery index ats_detect writes — “the index grows with use.”
3. The job-key snapshot ats_new_postings diffs against.

Tools

• ats_detect — Detect which applicant-tracking system (ATS) a company publishes its public job board on, and its board token. Reads the company’s careers page (or a given careers_url) for a Greenhouse/Lever/Ashby/Sm
• ats_jobs — Fetch normalized job postings from a PUBLIC ATS board you already have the ats + board_token for (use ats_detect or ats_company_jobs if you only have a domain). Returns {found:false, reason:“board_not
• ats_company_jobs — Detect a company’s public ATS board from its domain, then fetch its postings in one call — ats_detect + ats_jobs combined. Returns the same {found:false, reason:“no_ats_detected”} shape as ats_detect
• ats_new_postings — Diff a board’s current postings against the last time this tool was called for the same ats+board_token (snapshot kept in KV, dated). The FIRST call for a board has no prior snapshot, so it returns ev