Install Jentic One Beta

Connect the Recooty API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Recooty 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%2Frecooty.com%2Frecooty" | 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%2Frecooty.com%2Frecooty" | 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 Recooty API.

User login

Create job posting

List all jobs

Get job details

Update job

GET STARTED

Start building with Recooty API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Recooty API for, with concrete tasks.

★ HR and Recruiting Operations

Use the Recooty API to perform hr recruiting operations programmatically. The API provides 32 endpoints covering core functionality including user login, user logout, create job posting.

Call POST /login to user login

Automated Authentication Management

Automate authentication operations by combining multiple Recooty API endpoints. Agents can user logout and then create job posting in a single workflow.

Call POST /logout to user logout, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Recooty API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'user login', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

32 endpoints — recooty ai recruitment and applicant tracking system api.

METHOD

PATH

DESCRIPTION

POST

/login

User login

POST

/logout

User logout

POST

/jobs

Create job posting

GET

/jobs

List all jobs

GET

/jobs/{job_post}

Get job details

PUT

/jobs/{job_post}

Update job

DELETE

/jobs/{job_post}

Delete job

GET

/jobs/{job_post}/skills

Get job skills

POST

/login

User login

POST

/logout

User logout

POST

/jobs

Create job posting

GET

/jobs

List all jobs

GET

/jobs/{job_post}

Get job details

PUT

/jobs/{job_post}

Update job

DELETE

/jobs/{job_post}

Delete job

GET

/jobs/{job_post}/skills

Get job skills

Why Jentic?

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

Setup

Wiring the Recooty API by hand means handling its bearer token auth, pointing at the app.recooty.com host, and managing login yourself. Through Jentic you install once, import the Recooty API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Recooty puts the job id in the URL path (/jobs/{job_post}), so a rule can pin your agent to specific job posts. You choose the operations it may call, so writes like updating or deleting a job post are only included if you add them.

Credential isolation

Your Recooty token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a job post' or 'list a job's required skills', and Jentic returns the matching Recooty operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Recooty API through Jentic.

What authentication does the Recooty API use?

The Recooty API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I user login with the Recooty API?

Yes. Use the POST /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Recooty API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I user login through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'user login'. Jentic returns the matching Recooty API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Recooty API have?

The Recooty API exposes 32 endpoints covering authentication, jobs, applications operations.

Can I limit what my agent is allowed to do with the Recooty API?

Yes. Because you run Jentic One yourself, your own rules decide which Recooty operations and credentials the agent may use, so read-only calls like GET /jobs and GET /jobs/{job_post}/skills can be enabled while writes such as PUT or DELETE /jobs/{job_post} are included only if you add them. Since Recooty puts the job id in the URL path (/jobs/{job_post}), a rule can pin the agent to specific job posts rather than every one. Your Recooty token is stored once and injected at execution time, so the agent only ever acts within the operations you have granted.

Recooty API

Name: Recooty API
Brand: Recooty API
Availability: InStock

Official vendor OpenAPI document · agent-readyHR recruitingRecruiting Atsbearer32 EndpointsREST

For Agents

Programmatically user login, user logout. Covers 32 operations with bearer authentication.

Use for: I need to user login, I want to user logout, Search for job posting, Find all all jobs

Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.

Recooty AI recruitment and applicant tracking system API. Manage jobs, applications, interviews, candidates, and talent pools. The API exposes 32 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the Recooty API to your agent

Capabilities

Start building with Recooty API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Recooty API