Install Jentic One Beta

Connect the OwnerRez API to your agent

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

List properties

Get propertie

Create booking

Use Cases

Patterns agents use OwnerRez API for, with concrete tasks.

★ E-Commerce Operations

Use the OwnerRez API to perform e commerce operations programmatically. The API provides 34 endpoints covering core functionality including list properties, get propertie, create booking.

Call GET /properties to list properties

GET STARTED

Start building with OwnerRez API

Explore with Jentic One

View OpenAPI Document

Automated Bookings Management

Automate bookings operations by combining multiple OwnerRez API endpoints. Agents can get propertie and then create booking in a single workflow.

Call GET /properties/{id} to get propertie, then verify the result

AI Agent Integration via Jentic

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

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

Key Endpoints

34 endpoints — ownerrez vacation rental management api.

METHOD

PATH

DESCRIPTION

GET

/properties

List properties

GET

/properties/{id}

Get propertie

POST

/bookings

Create booking

GET

/bookings

List bookings

GET

/bookings/{id}

Get booking

POST

/quotes

Create quote

GET

/quotes

List quotes

GET

/quotes/{id}

Get quote

GET

/properties

List properties

GET

/properties/{id}

Get propertie

POST

/bookings

Create booking

GET

/bookings

List bookings

GET

/bookings/{id}

Get booking

POST

/quotes

Create quote

GET

/quotes

List quotes

GET

/quotes/{id}

Get quote

Why Jentic?

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

Setup

Wiring OwnerRez by hand means building and sending HTTP basic auth on every property, booking, and quote call. Through Jentic you install once, import the OwnerRez API from the API Directory, store the basic credentials once, and your agent calls it.

Permission scoping

OwnerRez puts the resource id in the URL path (/properties/{id}, /bookings/{id}), so a rule can pin your agent to one property or booking for the reads it needs. You choose the operations it may call, so creating a booking or quote is not included unless you add it.

Credential isolation

Your OwnerRez basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list properties' or 'create a booking quote', and Jentic returns the matching OwnerRez operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using OwnerRez API through Jentic.

What authentication does the OwnerRez API use?

The OwnerRez API uses HTTP Basic authentication with username and password. 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 properties with the OwnerRez API?

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

What are the rate limits for the OwnerRez 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 properties through Jentic?

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

How many endpoints does the OwnerRez API have?

The OwnerRez API exposes 34 endpoints covering bookings, channels, charges operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which OwnerRez operations and credentials the agent may use. Because OwnerRez puts the resource id in the URL path, such as /properties/{id} and /bookings/{id}, you can pin the agent to a single property or booking for the reads it needs. You also choose the operations it may call, so writes like POST /bookings or POST /quotes stay off unless you explicitly add them.

Ownerreservations OwnerRez API

Name: OwnerRez API
Brand: OwnerRez API
Availability: InStock

Official vendor OpenAPI document · agent-readyE CommerceStorefrontbasic34 EndpointsREST

For Agents

Programmatically list properties, get propertie. Covers 34 operations with basic authentication.

Use for: I need to properties, I want to propertie, Search for booking, Find all bookings

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

OwnerRez vacation rental management API. The API exposes 34 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document