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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjobicy.com%2Fjobicy" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjobicy.com%2Fjobicy" | 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

Read each listing's company name and original apply URL for downstream display or scraping

GET STARTED

Start building with Jobicy Remote Jobs API

Explore with Jentic One

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?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Jobicy Remote Jobs API by hand means reading its v2 feed docs, building the query parameters for its single /remote-jobs endpoint, and parsing the response yourself, even though it needs no auth. Through Jentic you install once, import the Jobicy Remote Jobs API from the API Directory, and your agent calls it with the right parameters at runtime.

Permission scoping

This API exposes a single read-only operation, GET /remote-jobs, so you limit the agent to the operations it needs, in this case just reading the curated remote-jobs feed. There is no write surface here, so the agent can query listings and nothing more.

Credential isolation

This endpoint is open, so there is no key to store; if that changes, any credential would be stored once, encrypted, by your own Jentic One instance and injected at execution time. It would never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find remote jobs' or 'list remote developer roles', and Jentic returns the GET /remote-jobs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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.

Can I limit what my agent is allowed to do with the Jobicy Remote Jobs API?

Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which operations your agent may call, and the Jobicy Remote Jobs API exposes only a single read-only operation, GET /remote-jobs. You can scope the agent to that one read operation, so it can fetch the curated remote-jobs feed and nothing more. There is no write surface here, so the agent can query listings but cannot create, edit, or delete anything.

Jobicy Remote Jobs API

AI ReadinessFoundational (D)46/100

See full scorecard

Official vendor OpenAPI document · agent-readyHR 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.

Use for: Find the latest remote software engineering jobs, List remote part-time roles available worldwide, Get all remote job postings from the last 7 days, Search for remote design jobs in Europe

Not supported: Does not handle applications, candidate tracking, or employer postings - use for reading Jobicy's curated remote jobs feed only.

The Jobicy Remote Jobs API exposes Jobicy's curated feed of fully remote job listings through a single GET /remote-jobs endpoint. Listings include title, company name, location preferences, job type (full-time, contract, part-time), salary range when known, posted date, and a link to apply. The endpoint is open (no authentication) and is intended for embedding remote-job listings in third-party sites, dashboards, and bots - for example a Slack bot that posts new remote roles each morning, or a personal job-search aggregator.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

22%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Jobicy Remote Jobs API to your agent

Capabilities

Start building with Jobicy Remote Jobs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jobicy Remote Jobs API

Jentic AI Readiness Score

Jobicy Remote Jobs API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness