Install Jentic One Beta

Connect the RealPage Exchange API to your agent

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

List residents

Get resident details

Access RealPage Exchange API crm resources via REST API

Use Cases

Patterns agents use RealPage Exchange API for, with concrete tasks.

★ CRM Operations

Use the RealPage Exchange API to perform crm operations programmatically. The API provides 14 endpoints covering core functionality including list residents, get resident details, get resident events.

Call GET /residents to list residents

GET STARTED

Start building with RealPage Exchange API

Explore with Jentic One

View OpenAPI Document

Automated Residents Management

Automate residents operations by combining multiple RealPage Exchange API endpoints. Agents can get resident details and then get resident events in a single workflow.

Call GET /residents/{residentId} to get resident details, then verify the result

AI Agent Integration via Jentic

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

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

Key Endpoints

14 endpoints — the realpage exchange (rpx) api enables integration with realpage's property management platform.

METHOD

PATH

DESCRIPTION

GET

/residents

List residents

GET

/residents/{residentId}

Get resident details

GET

/residents/events

Get resident events

GET

/leases

List leases

GET

/leases/{leaseId}

Get lease details

GET

/sites

List sites

GET

/sites/{siteId}

Get site details

GET

/sites/{siteId}/units

List units for a site

GET

/residents

List residents

GET

/residents/{residentId}

Get resident details

GET

/residents/events

Get resident events

GET

/leases

List leases

GET

/leases/{leaseId}

Get lease details

GET

/sites

List sites

GET

/sites/{siteId}

Get site details

GET

/sites/{siteId}/units

List units for a site

Why Jentic?

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

Setup

Wiring the RealPage Exchange API by hand means combining its X-License-Key header with HTTP basic auth, navigating residents, leases, sites, and units, and handling paging and retries yourself. Through Jentic you install once, import the RealPage Exchange API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The RealPage Exchange API puts the site id in the URL path (/sites/{siteId}/units), so a rule can pin your agent to one site. You choose the operations it may call, and since these endpoints are read-only, it retrieves residents, leases, and units rather than changing them.

Credential isolation

Your RealPage Exchange API credential 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 residents' or 'get units for a site', and Jentic returns the matching RealPage Exchange API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using RealPage Exchange API through Jentic.

What authentication does the RealPage Exchange API use?

The RealPage Exchange API uses apiKey, basic authentication. 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 residents with the RealPage Exchange API?

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

What are the rate limits for the RealPage Exchange 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 residents through Jentic?

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

How many endpoints does the RealPage Exchange API have?

The RealPage Exchange API exposes 14 endpoints covering residents, leases, sites operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which RealPage Exchange API operations and credentials your agent may use. Since the site id lives in the URL path (/sites/{siteId}/units), you can pin the agent to a single site, and you pick exactly which operations it may call, such as GET /residents, GET /leases, or GET /sites/{siteId}/units. These endpoints are read-only, so the agent retrieves resident, lease, and unit data rather than changing it.

RealPage Exchange API

Name: RealPage Exchange API
Brand: RealPage Exchange API
Availability: InStock

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMCustomer SupportapiKey, basic14 EndpointsREST

For Agents

Programmatically list residents, get resident details. Covers 14 operations with apiKey, basic authentication.

Use for: I need to residents, I want to resident details, Search for resident events, Find all leases

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

The RealPage Exchange (RPX) API enables integration with RealPage's property management platform. The API provides access to resident management, lease tracking, property operations, and financial data. Access requires an active RealPage partner agreement through the RPX AppPartner Program. The API supports both REST and SOAP interfaces; this specification covers the REST API endpoints. The API exposes 14 endpoints secured with apiKey, basic authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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.

100%

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: DSignals: 4

24%

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.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

30%

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

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RealPage Exchange API to your agent

Capabilities

Use Cases

Start building with RealPage Exchange API

Key Endpoints

Why Jentic?

Related APIs

FAQs

RealPage Exchange API

Jentic AI Readiness Score

RealPage Exchange 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