Install Jentic One Beta

Connect the Cavuno v1 REST API to your agent

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

Post, publish, duplicate, and expire job listings

Create candidate profiles and attach or download resumes

Track companies and employer records with custom fields

Search jobs and companies and export the results

Import candidate and company records from uploaded files

GET STARTED

Start building with Cavuno v1 REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cavuno v1 REST API for, with concrete tasks.

★ AI Agent Job Posting

An AI agent connected through Jentic can open a role end to end: it creates the job for a company, publishes it to the board, and confirms the listing is live. Cavuno handles the listing lifecycle so the agent coordinates posting and publishing instead of stepping through the dashboard.

Create a job for a given company, publish it to the board, and confirm the job status is live

Candidate Pipeline Management

Keep applicant records current by creating candidate profiles, attaching resumes, and updating custom fields as people move through hiring. Cavuno supports candidate reconciliation, deactivation, and reactivation so the pipeline reflects real status.

Create a candidate profile with contact details, attach a resume, and set the role they applied for

Bulk Data Import

Load existing candidate or company data by uploading a file, confirming the field mapping, and running the import. Cavuno reports import quota and per-batch status so large migrations stay auditable.

Upload a candidate CSV, confirm the column mapping, and start the import batch

Job and Company Search

Power syndication and reporting by searching jobs and companies and exporting the matched records. Cavuno exposes dedicated search operations plus exports so downstream systems stay in sync.

Search jobs matching a keyword and location, then export the matched listings

Key Endpoints

260 endpoints — the cavuno api powers a job board and applicant-tracking platform where you post jobs, publish and expire listings, and move candidates through hiring.

METHOD

PATH

DESCRIPTION

POST

/jobs

Create a job

POST

/jobs/{id}/publish

Publish a job

POST

/jobs/search

Search jobs

POST

/candidates

Create a candidate

GET

/candidates

List candidates

POST

/companies

Create a company

GET

/subscribers

List subscribers

POST

/jobs

Create a job

POST

/jobs/{id}/publish

Publish a job

POST

/jobs/search

Search jobs

POST

/candidates

Create a candidate

GET

/candidates

List candidates

POST

/companies

Create a company

GET

/subscribers

List subscribers

Why Jentic?

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

Setup

Wiring Cavuno by hand means handling its bearer-token auth and tracking resource paths for jobs, candidates, companies, and imports across a large surface yourself. Through Jentic you install once, import Cavuno from the API Directory, store the token once, and your agent calls it.

Permission scoping

You choose which Cavuno operations the agent may call, such as posting and publishing jobs and reading candidates, so destructive operations like deleting candidates or companies are not included unless you add them.

Credential isolation

Your Cavuno bearer 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 'post a job' or 'create a candidate', and Jentic returns the matching Cavuno operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cavuno v1 REST API through Jentic.

What authentication does the Cavuno API use?

The Cavuno API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec. You create the token in your Cavuno account, and through Jentic it is stored encrypted by your own Jentic One instance and injected at call time, so it never appears in the agent's prompt or logs.

Can I manage candidates with the Cavuno API?

Yes. You can create candidate profiles, attach and download resumes, set custom-field values, and move candidates through reconciliation, deactivation, and reactivation. Candidates can also be imported in batches from an uploaded file.

Can I search jobs and companies with the Cavuno API?

Yes. The API exposes dedicated search operations for jobs and companies, plus exports for jobs, companies, candidates, and subscribers. You can page through large result sets for reporting or syndication.

Is there a Cavuno MCP server?

You do not need an MCP server to give your agent the Cavuno API. Jentic connects it directly from the API Directory: import Cavuno, store your token once, and your agent posts jobs and manages candidates through the operations the API already exposes. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.

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

Yes. Write a rule that allows only the operations the agent needs, for example posting and publishing jobs and reading candidates, and leave out destructive ones like deleting candidates or companies. The agent works the pipeline within those bounds, and every call it makes is logged.

How do I post a job through Jentic with the Cavuno API?

Search Jentic for 'post a job', which returns the Cavuno job-creation operation with its input schema, then supply the company and job details and the agent runs it before publishing. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Cavuno v1 REST API

AI ReadinessFoundational (C)54/100

See full scorecard

Official vendor OpenAPI document · agent-readyHR recruitingRecruiting Atsbearer260 EndpointsREST

For Agents

Post and publish jobs, track candidate profiles and resumes, manage companies and employers, and search listings through the Cavuno job-board API.

Use for: Post a new job listing for a company, Publish a drafted job to the board, Create a candidate profile and attach a resume, Search jobs by keyword and location

Not supported: Does not handle payroll, background checks, or offer-letter e-signatures. Use for job-board listings, candidate tracking, and employer management only.

The Cavuno API powers a job board and applicant-tracking platform where you post jobs, publish and expire listings, and move candidates through hiring. It manages candidate profiles, resumes, companies, and employers, and supports bulk imports, saved searches, and custom fields across those records. Blog content, billing, SSO connections, webhooks, and board settings round out the platform surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

35%

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.

96%

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).

100%

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: C-Signals: 4

47%

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.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Cavuno v1 REST API to your agent

Capabilities

Start building with Cavuno v1 REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cavuno v1 REST API

Jentic AI Readiness Score

Cavuno v1 REST 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