Remote OK API vs Coresignal for AI agents
Remote OK API is a public JSON feed of the jobs posted on the Remote OK remote job board. Coresignal is a B2B jobs data API and dataset of deduplicated job postings merged from many sources into one format.
The short answer
- Remote OK API: The simplest no-key feed of remote tech and startup jobs for a site that links back to Remote OK.
- Coresignal: Large-scale, historical job-postings data for analytics, research and data products.
Side by side
| Remote OK API | Coresignal | |
|---|---|---|
| Searches | Remote OK's own remote job board only. | Company websites, professional networks, ATS platforms and major job aggregators; 486M+ postings, 52M+ active, 195+ countries. |
| Returns | JSON array of jobs with id, slug, company, position, tags, location, salary_min, salary_max, url, apply_url, date, epoch, description and logo fields. | Records with job_id, status, title, description, seniority, employment_type, company_name, company_domain, location, country/city, salary (min, max, currency), external_url and job_sources[].url. |
| Before the first call | Nothing: no key or sign-up. The feed at remoteok.com/api answers without one. | A Coresignal account and API key (trial available); queries use Elasticsearch DSL. |
| Free | No key needed, and its pages state no price | Trial with 2,000 free credits, no credit card required (1 credit per job posting record). |
| Paid | Not stated on its pages | Self-serve plans from $49 per month (Mini, 2,500 credits per month); datasets are custom-priced from $1,000. |
| Acting on a result | Both url and apply_url point to the job page on remoteok.com, not to the employer. | external_url is the job URL on the company's own site (not always filled); job_sources[].url gives each source posting. |
| Limits on keeping or showing results | 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. | Not stated on its pages |
| Coverage | Remote jobs; location is free text (e.g. 'Remote', 'US, UK, Canada, Australia + 35 other countries'). | 195+ countries. |
| MCP server | No official server listed | Official Coresignal MCP server, OAuth 2.1: https://mcp.coresignal.com/mcp/v2 (legacy https://mcp.coresignal.com/mcp deprecated Nov 1, 2026) |
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 Remote OK API and Openpath vs Coresignal.
Questions people ask
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.
What do I need before I can use Coresignal?
A Coresignal account and API key (trial available); queries use Elasticsearch DSL.
Is Coresignal free?
Trial with 2,000 free credits, no credit card required (1 credit per job posting record).
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
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”
Coresignal, read on October 15, 2026:
- coresignal.com/solutions/jobs-data-api: “Jobs data from company websites, professional networks, ATS platforms, and major jobs data aggregators”
- coresignal.com/solutions/jobs-data-api: “2,000 free credits · No credit card required”
- coresignal.com/solutions/jobs-data-api: “195+ countries covered”
- coresignal.com/pricing: “monthly plans starting at $49/month”
- coresignal.com/pricing: “One price, full data record”
- docs.coresignal.com/jobs-api/multi-source-jobs-api/data-dictionary-multi-source-jobs-api: “External (company) job URL”
- docs.coresignal.com/integrations/coresignal-mcp: “OAuth 2.1 sign-in via the Coresignal dashboard”