Install Jentic One Beta

Connect the Rezora API to your agent

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

Create an agent

List agents

Get an agent

Update an agent

Delete an agent

Use Cases

Patterns agents use Rezora API for, with concrete tasks.

GET STARTED

Start building with Rezora API

Explore with Jentic One

View OpenAPI Document

Automated agents Management

Automate agents operations by combining multiple Rezora API endpoints. Agents can list agents and then get an agent in a single workflow.

Call GET /agents to list agents, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Rezora 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 an agent', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — rezora provides real estate marketing automation tools.

METHOD

PATH

DESCRIPTION

POST

/agents

Create an agent

GET

/agents

List agents

GET

/agents/{agentId}

Get an agent

PUT

/agents/{agentId}

Update an agent

DELETE

/agents/{agentId}

Delete an agent

POST

/contacts

Create a contact

GET

/contacts

List contacts

GET

/contacts/{contactId}

Get a contact

POST

/agents

Create an agent

GET

/agents

List agents

GET

/agents/{agentId}

Get an agent

PUT

/agents/{agentId}

Update an agent

DELETE

/agents/{agentId}

Delete an agent

POST

/contacts

Create a contact

GET

/contacts

List contacts

GET

/contacts/{contactId}

Get a contact

Why Jentic?

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

Setup

Wiring the Rezora API by hand means handling its X-API-Key header auth, sending that key on every call to data.rezora.com, and managing retries yourself. Through Jentic you install once, import the Rezora API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Rezora puts the agent id in the URL path (/agents/{agentId}), so a rule can pin your agent to one directory agent: it can read that agent record and nothing else. You choose the operations it may call, so destructive ones like deleting an agent are not included unless you add them.

Credential isolation

Your Rezora 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 'create an agent' or 'look up a contact', and Jentic returns the matching Rezora API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Rezora API through Jentic.

What authentication does the Rezora API use?

The Rezora 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 an agent with the Rezora API?

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

What are the rate limits for the Rezora 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 an agent through Jentic?

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

How many endpoints does the Rezora API have?

The Rezora API exposes 11 endpoints covering agents, contacts, distribution-lists operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Rezora API operations and credentials the agent may use. Because Rezora carries the agent id in the URL path, such as GET /agents/{agentId}, you can pin the agent to a single directory record so it reads that one agent and nothing else. You also pick the operations it may call, so destructive ones like DELETE /agents/{agentId} stay off the list unless you add them.

Rezora API

Name: Rezora API
Brand: Rezora API
Availability: InStock

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey11 EndpointsREST

For Agents

Programmatically create an agent, list agents. Covers 11 operations with apiKey authentication.

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

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Rezora provides real estate marketing automation tools. This API allows you to manage agents, contacts, and distribution lists. Note: The original Rezora API has been deprecated. This specification is based on legacy documentation and may not reflect the current API. The API exposes 11 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Rezora API to your agent

Capabilities

Use Cases

Start building with Rezora API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rezora API