Jobicy Remote Jobs API

Name: Jobicy Remote Jobs API
Brand: Jobicy Remote Jobs API
Availability: InStock

✓ Official Vendor SpecHR recruitingRecruiting Atsnone1 EndpointsREST

For Agents

Read curated remote job listings from Jobicy's open feed via a single GET /remote-jobs endpoint — title, company, location, type, salary, and apply link.

Install Jentic One Beta

Connect the Jobicy Remote Jobs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jobicy Remote Jobs API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Jobicy Remote Jobs API.

Retrieve the latest remote job listings curated by Jobicy via GET /remote-jobs

Filter listings by job type (full-time, part-time, contract) when supported by query parameters

Filter listings by region or country preference where the listing exposes that field

GET STARTED

Start building with Jobicy Remote Jobs API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Jobicy Remote Jobs API for, with concrete tasks.

★ Daily Remote-Jobs Digest in Slack or Email

A scheduled bot pulls the latest /remote-jobs each morning, filters by tag (engineering, design, marketing), de-duplicates against yesterday's pull, and posts new listings to a Slack channel or email digest. Because the endpoint is open and a single call returns all current listings, this is a one-cron, no-credentials integration that takes minutes to build.

Call GET /remote-jobs, filter results to tag=engineering posted in the last 24 hours, and post each new listing as a Slack message with the title, company, and apply URL.

Remote-Jobs Aggregator Site or Widget

A personal site, newsletter, or Notion dashboard can embed a 'Latest remote jobs' widget by calling /remote-jobs server-side and rendering the response. Refreshing every few hours keeps the widget current without scraping the Jobicy site directly.

Call GET /remote-jobs, cache the response for 4 hours, and render the top 20 listings as cards on the page with title, company, location, and apply link.

Job-Market Analytics on Remote Hiring Trends

Researchers and HR teams pull /remote-jobs daily, store the snapshots, and compute trends — which roles are growing, which companies are most active, average posted salary by category — without crawling the Jobicy website. A small ETL job is sufficient to build a multi-month dataset.

Call GET /remote-jobs daily, persist each listing with a captured-at timestamp, and aggregate weekly counts by tag and average posted salary by tag for a trend dashboard.

AI Agent Integration via Jentic

A career-assistant agent uses Jentic to discover the Jobicy remote jobs operation. The agent searches for 'find remote jobs' and Jentic returns the GET /remote-jobs operation. Because the endpoint is open, no credentials are required — Jentic still adds value by serving the operation schema and parameters to the agent on demand.

Search Jentic for 'find remote jobs', load the GET /remote-jobs schema, and execute it filtered to the user's preferred tag and region.

Key Endpoints

1 endpoints — the jobicy remote jobs api exposes jobicy's curated feed of fully remote job listings through a single get /remote-jobs endpoint.

METHOD

PATH

DESCRIPTION

GET

/remote-jobs

List curated remote job listings

GET

/remote-jobs

List curated remote job listings

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

No credentials are needed — the endpoint is open. Jentic still serves the operation schema so an agent calls /remote-jobs with the right query parameters at runtime.

Intent-based discovery

Agents search Jentic with 'find remote jobs' and Jentic returns the GET /remote-jobs operation. No secrets to manage.

Time to first call

Direct Jobicy integration: under an hour — it's a single open GET. Through Jentic: minutes — search, load schema, execute, with the operation tracked in Jentic's catalogue.

FAQs

Specific to using Jobicy Remote Jobs API through Jentic.

What authentication does the Jobicy Remote Jobs API use?

None. The /remote-jobs endpoint is open and the spec declares a noAuth security scheme. You can call it directly from a server, Slack bot, or a Jentic agent without provisioning any credentials.

Can I filter results from the Jobicy API by job tag or region?

GET /remote-jobs is the single endpoint and accepts query parameters for filtering — the spec exposes the available filters. In practice, fetch the response and filter client-side as well, since the curated list is small enough to scan in memory.

What are the rate limits for the Jobicy Remote Jobs API?

Jobicy does not publish a fixed rate limit, but the open feed should be polled responsibly — typically once an hour or once every few hours is sufficient for a digest or widget. Use HTTP caching headers if returned, and back off on any 429 response.

How do I build a remote-jobs digest through Jentic?

Run pip install jentic, search for 'find remote jobs', and execute GET /remote-jobs on a schedule. Diff against the previous day's pull and post any new listings to your channel of choice — no credentials needed.

Is the Jobicy Remote Jobs API free?

Yes. The endpoint is open, no auth, no key, and Jobicy publishes it for community use. Respect the published terms on jobicy.com if you redistribute the listings at scale.