Reverse who's-hiring-for {role, geo}: companies with active reqs matching q (posting title) / geo (country) / since (first-seen lower bound), deduped by company, each with its full hiring pulse and the specific reqs that matched. LinkedIn-excluded: ATS tenants plus public job boards and aggregators; each matched req's boards names its source. since and each req's first_seen are our first observation of the req, not the employer's posting date. Freshness-floored on the free tier only (by when a req was first seen), keyset-paginated via next_cursor (the last page's highest company_id).

q is a full-text query over the raw posting title, not an id: type the role the way a posting would spell it (staff engineer), every word must match -- plurals and other inflections included, so staff engineers is the same search -- and a title that matches nothing comes back as an empty page rather than an error. role is its deprecated former name, still accepted until its Sunset date. The two filters are deliberately asymmetric -- an unresolvable geo IS rejected with 422, because a country either is or is not in the stored vocabulary, whereas an unmatched title is an honest zero result.

geo, industry, industry_terms and headcount_band can each be repeated: repeat a parameter to OR its values; different parameters AND. Every other parameter takes one value, and repeating it is rejected with 422. industry, industry_terms and headcount_band cut the corpus down to your ICP's companies. They are filters only -- no company facet is added to the response by passing one -- and a company whose fact we do not hold is never matched, so a cut is honestly narrow rather than quietly padded.

limit is bounded: this endpoint meters the billed source_row atom off its own serialized rows, so an unbounded page is an unbounded invoice. An out-of-range limit is rejected with 422 rather than silently truncated; page through the full set with next_cursor. The shared public demo key gets a tighter page instead -- it bills nothing, so no ledger-derived gate can bound it, and a full-size page would make a world-readable credential a bulk-export window onto the fresh index.

Requires the read scope.