Let candidates' AI assistants read the postings in your own hiring system

A one-page note for employers. Free, read-only, ten minutes. Nobody can buy ranking.

What this is

OpenHire is an open-source job-search tool (an MCP server). Candidates add it to AI assistants such as ChatGPT, Claude, Doubao, DeepSeek (through an MCP-capable client), Cursor or Tencent WorkBuddy, and the assistant reads postings straight from the public API of the employer's own hiring system (Greenhouse, Lever, Ashby, Beisen, Moka, Workable, SmartRecruiters, Rippling or Personio), not from a job board. A candidate's résumé travels only between their own computer and your apply page; it never passes through us.

Every posting in the index carries the original posting date recorded in your system, how long it has been up, and a link straight to your apply page. You can check the numbers yourself: numbers.json (with how each is counted and when it was measured).

What your company gets, and what it can never get

Are your postings already in the index?

Employers on Greenhouse, Lever, Ashby, Beisen, Moka, Workable, SmartRecruiters, Rippling or Personio are most likely in already; claim your company in the employers section of the repository.

Employers on Feishu Hire, posting only on BOSS Zhipin, or on a self-built careers page are not in the index today. That is not our choice; we cannot read them: Feishu's postings API requires signed requests, which we treat as access control and do not work around; a job board is not your own system, so we do not read it; most self-built pages carry no machine-readable posting data. Any of the three ways below works: read-only, free, ten minutes.

Three ways in, the simplest first

1. Fill in a spreadsheet and send it from your company email (no IT needed, two minutes). Download the postings sheet (Excel), one posting per row, six columns: job title, city, posting date, apply link or apply email, salary range (optional), job description. Send the file from your company email domain to gdchenhao@qq.com with the subject "Postings sheet + company name", and include your careers page address in the body. A company email is the first step, not the whole check: we also check the business registration and ICP filing, the domain's age and site history, and call back the phone number published on your website. Fill these in on the sheet's "Company" tab and we do the checking (see section 6). No business licence needed. Live within 3 working days.
   Three rules up front: every posting carries an "employer self-reported" label, and days open count from the date you entered; every posting comes down automatically after 90 days, so send the sheet again if you are still hiring; apply links are accepted only on https pages of your own website; otherwise we send candidates to your careers page and show the apply email in the posting.
2. Feishu Hire: grant two read-only scopes (ten minutes). In the Feishu Open Platform, grant our app hire:site:readonly and hire:site_job_post:readonly. They expose only the careers site and postings you already publish, touch no candidate data, and can be revoked in one click. Postings that come this way carry the real posting date from your system and need no renewal.
3. If you have a web developer: put machine-readable posting data on your site. Add schema.org JobPosting JSON-LD to your careers page (the same standard Google for Jobs uses), or publish a static JSON file, and send us the address. We provide the template and field notes on request; the advantage is that updates need no new sheet: we read the page regularly.

Employers on Greenhouse, Lever, Ashby, Beisen, Moka, Workable, SmartRecruiters, Rippling or Personio do not need any of these three; you are most likely in the index already. Claim your company in the employers section of the repository.

How to reach us, and how fast we reply

• Simplest: send the postings sheet (both tabs filled in) from your company email to gdchenhao@qq.com, subject "Postings sheet + company name";
• GitHub form: Employer claim. It asks where your postings are published today; pick one and we reply along that path;
• No GitHub account: email gdchenhao@qq.com with the subject "Employer claim + company name"; sending it from your company domain is itself the identity check;
• A decision within 3 working days. Identity material is used only for the check: not published, not kept, not used for anything else.

How we verify, and what we need from you

A company email proves only that the sender controls the domain, and a domain costs very little, so it is only the first step. We check evidence an applicant cannot produce themselves, stacked together, plus a human decision:

All you do is complete the "Company" tab: full registered name, unified social credit code (overseas companies give registration number and place), website domain, ICP filing number, the page and number of the phone published on your website, two industry footprint links, and the contact's job title. We do the checking, mostly automatically; what remains is two government sites and one phone call.

To be clear about what we check: the company exists and is in our three sectors. We do not vouch for your company; every posting candidates see carries the "employer self-reported" label, and on any report we take it down first and ask afterwards.

Limits, stated up front

• We can measure how long a posting has been up; we cannot measure whether you want to fill it. Claiming lets you explain the first in your own words;
• We never name a company as "unreadable" in any copy to push employers to open up. Whether to take any of these paths is your decision;
• You can ask at any time to have your company removed from the index; we do it, no argument.