Install Jentic One Beta

Connect the Replify.ai API to your agent

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

Create, update, or remove campaign contacts

Manage identity auth data programmatically

Integrate Replify.ai API into automated workflows

Query and filter Replify.ai API records by parameters

Monitor Replify.ai API operational status and events

GET STARTED

Start building with Replify.ai API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Replify.ai API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Replify.ai API to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including create, update, or remove campaign contacts.

Call POST /campaigns/{campaignId}/contacts to create, update, or remove campaign contacts

Data Retrieval and Monitoring

Query Replify.ai API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Replify.ai API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Replify.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 'create, update, or remove campaign contacts', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

1 endpoints — replify.

METHOD

PATH

DESCRIPTION

POST

/campaigns/{campaignId}/contacts

Create, update, or remove campaign contacts

POST

/campaigns/{campaignId}/contacts

Create, update, or remove campaign contacts

Why Jentic?

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

Setup

Wiring Replify.ai by hand means setting its x-api-key header on every request against the api.heylibby.com host and mapping campaign ids into the contact payload yourself. Through Jentic you install once, import the Replify.ai API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Replify.ai puts the campaign id in the URL path (/campaigns/{campaignId}/contacts), so a rule can pin your agent to one campaign: it can add contacts to that campaign and nothing else. You choose the operations it may call, so the agent is limited to exactly the contact operation you grant.

Credential isolation

Your Replify.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 'add a contact to a campaign', and Jentic returns the matching Replify.ai operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Replify.ai API through Jentic.

What authentication does the Replify.ai API use?

The Replify.ai API uses an API key passed in the `x-api-key` 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 create, update, or remove campaign contacts with the Replify.ai API?

Yes. Use the POST /campaigns/{campaignId}/contacts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Replify.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 create, update, or remove campaign contacts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create, update, or remove campaign contacts'. Jentic returns the matching Replify.ai API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Replify.ai API have?

The Replify.ai API exposes 1 endpoints covering campaigns operations.

Can I limit what my agent is allowed to do with the Replify.ai API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and you can grant it only the one contact operation this API exposes, POST /campaigns/{campaignId}/contacts. Since the campaign id sits in the URL path, a rule can pin the agent to a single campaign so it manages contacts there and nothing else. Your Replify.ai API key stays with your instance and is injected only when that allowed call runs.

Replify.ai API

Name: Replify.ai API
Brand: Replify.ai API
Availability: InStock

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationapiKey1 EndpointsREST

For Agents

Programmatically create, update, or remove campaign contacts. Covers 1 operations with apiKey authentication.

Use for: I need to create, update, or remove campaign contacts, Find available identity auth operations, Get the current status of Replify.ai API resources, List all records from Replify.ai API

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

Replify.ai Campaign Service API allows you to manage campaign contacts programmatically. The API uses bearer token authentication obtained via OAuth2. The API exposes 1 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Replify.ai API to your agent

Capabilities

Start building with Replify.ai API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Replify.ai API