Install Jentic One Beta

Connect the Relevance AI API to your agent

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

List Agents

Get Agent

Delete Agent

Create or Update Agent

Trigger an Agent Task

GET STARTED

Start building with Relevance AI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Relevance AI API for, with concrete tasks.

★ HR and Recruiting Operations

Use the Relevance AI API to perform hr recruiting operations programmatically. The API provides 9 endpoints covering core functionality including list agents, get agent, delete agent.

Call POST /agents/list to list agents

Automated Agents Management

Automate agents operations by combining multiple Relevance AI API endpoints. Agents can get agent and then delete agent in a single workflow.

Call GET /agents/{agent_id} to get agent, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Relevance AI 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 apiKey tokens manually.

Search Jentic for 'list agents', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — relevance ai is the home of the ai workforce.

METHOD

PATH

DESCRIPTION

POST

/agents/list

List Agents

GET

/agents/{agent_id}

Get Agent

DELETE

/agents/{agent_id}

Delete Agent

POST

/agents/upsert

Create or Update Agent

POST

/agents/{agent_id}/tasks/trigger

Trigger an Agent Task

GET

/agents/{agent_id}/tasks/{conversation_id}/view_steps

View Task Steps

POST

/tools/list

List Tools

POST

/tools/studios/{tool_id}/run

Run a Tool

POST

/agents/list

List Agents

GET

/agents/{agent_id}

Get Agent

DELETE

/agents/{agent_id}

Delete Agent

POST

/agents/upsert

Create or Update Agent

POST

/agents/{agent_id}/tasks/trigger

Trigger an Agent Task

GET

/agents/{agent_id}/tasks/{conversation_id}/view_steps

View Task Steps

POST

/tools/list

List Tools

POST

/tools/studios/{tool_id}/run

Run a Tool

Why Jentic?

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

Setup

Wiring Relevance AI by hand means formatting its project_id:api_key Authorization header, choosing the right regional host on stack.tryrelevance.com, and mapping its agent and tool endpoints yourself. Through Jentic you install once, import Relevance AI from the API Directory, store the key once, and your agent calls it.

Permission scoping

Relevance AI puts the agent id in the URL path (/agents/{agent_id}), so a rule can pin your agent to viewing and triggering tasks for one agent. You choose the operations it may call, so deleting an agent is not included unless you add it.

Credential isolation

Your Relevance AI API key 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 'list agents' or 'trigger an agent task', and Jentic returns the matching Relevance AI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Relevance AI API through Jentic.

What authentication does the Relevance AI API use?

The Relevance AI API uses an API key passed 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 list agents with the Relevance AI API?

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

What are the rate limits for the Relevance AI 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 list agents through Jentic?

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

How many endpoints does the Relevance AI API have?

The Relevance AI API exposes 9 endpoints covering agents, knowledge, tasks operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Relevance AI operations and credentials the agent may use. Because Relevance AI puts the agent id in the URL path, such as GET /agents/{agent_id} and POST /agents/{agent_id}/tasks/trigger, you can pin the agent to viewing and triggering tasks for a single agent. You pick the operations it may call, so destructive calls like DELETE /agents/{agent_id} are excluded unless you explicitly add them.

Relevance AI API

Name: Relevance AI API
Brand: Relevance AI API
Availability: InStock

Official vendor OpenAPI document · agent-readyHR recruitingPayrollapiKey9 EndpointsREST

For Agents

Programmatically list agents, get agent. Covers 9 operations with apiKey authentication.

Use for: I need to agents, I want to agent, Search for agent, Find all or update agent

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

Relevance AI is the home of the AI workforce. The API allows you to manage agents, tools, tasks, and knowledge. Build autonomous AI agents that follow your processes. The API exposes 9 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Relevance AI API to your agent

Capabilities

Start building with Relevance AI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Relevance AI API