Greenhouse Job Board API vs Remote OK API for AI agents
Greenhouse Job Board API is a public JSON view of one company's offices, departments and published jobs on Greenhouse, meant for building that company's careers site. Remote OK API is a public JSON feed of the jobs posted on the Remote OK remote job board.
The short answer
- Greenhouse Job Board API: Reading a known company's live openings straight from its own applicant tracking system.
- Remote OK API: The simplest no-key feed of remote tech and startup jobs for a site that links back to Remote OK.
Side by side
| Greenhouse Job Board API | Remote OK API | |
|---|---|---|
| Searches | One employer's Greenhouse job board per call (by board_token); employer-direct, no cross-company search. | Remote OK's own remote job board only. |
| Returns | JSON jobs with id, title, location.name, updated_at, absolute_url and, with content=true, the full description, departments and offices. | JSON array of jobs with id, slug, company, position, tags, location, salary_min, salary_max, url, apply_url, date, epoch, description and logo fields. |
| Before the first call | Nothing for GET: no authentication; you need the company's board_token. Submitting applications needs the company's API key. | Nothing: no key or sign-up. The feed at remoteok.com/api answers without one. |
| Free | No key needed, and its pages state no price | No key needed, and its pages state no price |
| Acting on a result | absolute_url is the employer's own job post (the docs don't say where it is hosted). | Both url and apply_url point to the job page on remoteok.com, not to the employer. |
| Limits on keeping or showing results | Not stated on its pages | Must link back (followed, not nofollow) to the Remote OK URL and name Remote OK as source, or access is suspended; don't use the Remote OK logo without written permission. |
| Coverage | Wherever the employer hires. | Remote jobs; location is free text (e.g. 'Remote', 'US, UK, Canada, Australia + 35 other countries'). |
| MCP server | No official server listed | No official server listed |
Where Openpath fits
If the agent needs a job to apply for in Austin, Texas, or a remote one, Openpath returns the listings themselves, free and with no key. See Openpath vs Greenhouse Job Board API and Openpath vs Remote OK API.
Questions people ask
What do I need before I can use Greenhouse Job Board API?
Nothing for GET: no authentication; you need the company's board_token. Submitting applications needs the company's API key.
Is Greenhouse Job Board API free?
No key needed, and its pages state no price.
What do I need before I can use Remote OK API?
Nothing: no key or sign-up. The feed at remoteok.com/api answers without one.
Is Remote OK API free?
No key needed, and its pages state no price.
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
Greenhouse Job Board API, read on October 15, 2026:
- docs.greenhouse.io/job-board.html: “Job Board data is publicly available, so authentication is not required for any GET endpoints.”
- docs.greenhouse.io/job-board.html: “a simple JSON representation of your company's offices, departments, and published jobs”
Remote OK API, read on October 15, 2026:
- remoteok.com/api: “Please link back (with follow, and without nofollow!) to the URL on Remote OK”
- remoteok.com/api: “If you do not we'll have to suspend API access.”
- remoteok.com/api: “https://remoteOK.com/remote-jobs/remote-ai-trainer-imerit-technology-1137513”