Install Jentic One Beta

Connect the RESO Web API to your agent

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

List Properties

Get Property by Listing Key

Integrate RESO Web API into automated workflows

Query and filter RESO Web API records by parameters

Monitor RESO Web API operational status and events

GET STARTED

Start building with RESO Web API

Explore with Jentic One

View OpenAPI Document

Automated Media Management

Automate media operations by combining multiple RESO Web API endpoints. Agents can get property by listing key and then list members/agents in a single workflow.

Call GET /Property('{listingKey}') to get property by listing key, then verify the result

AI Agent Integration via Jentic

AI agents discover and call RESO Web 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 bearer tokens manually.

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

Key Endpoints

7 endpoints — reso web api standard based on odata v4 for real estate data exchange.

METHOD

PATH

DESCRIPTION

GET

/Property

List Properties

GET

/Property('{listingKey}')

Get Property by Listing Key

GET

/Member

List Members/Agents

GET

/Office

List Offices

GET

/Media

List Media

GET

/OpenHouse

List Open Houses

GET

/$metadata

Get Service Metadata

GET

/Property

List Properties

GET

/Property('{listingKey}')

Get Property by Listing Key

GET

/Member

List Members/Agents

GET

/Office

List Offices

GET

/Media

List Media

GET

/OpenHouse

List Open Houses

GET

/$metadata

Get Service Metadata

Why Jentic?

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

Setup

Wiring the RESO Web API by hand means setting its bearer auth on every request, building OData query strings against the api.reso.org/odata host, and reading the $metadata document to shape entity calls yourself. Through Jentic you install once, import the RESO Web API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The RESO Web API puts the listing key in the URL path (/Property('{listingKey}')), so a rule can pin your agent to reading a specific property. Every operation here is read-only, and you choose which of them the agent may call.

Credential isolation

Your RESO Web API token 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 properties' or 'get a property by listing key', and Jentic returns the matching RESO Web API 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 RESO Web API through Jentic.

What authentication does the RESO Web API use?

The RESO Web API uses a Bearer token 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 properties with the RESO Web API?

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

What are the rate limits for the RESO Web 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 RESO Web API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the RESO Web API have?

The RESO Web API exposes 7 endpoints covering media, member, metadata operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which RESO Web API operations and credentials the agent may use, and every operation here (GET /Property, /Member, /Office, /Media, /OpenHouse, and /$metadata) is read-only, so the agent can never modify listing data. Since the listing key sits in the URL path, GET /Property('{listingKey}'), you can pin the agent to reading one specific property. You choose which of these endpoints the agent is allowed to call and which are off limits.

RESO Web API

Name: RESO Web API
Brand: RESO Web API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontbearer7 EndpointsREST

For Agents

Programmatically list properties, get property by listing key. Covers 7 operations with bearer authentication.

Use for: I need to properties, I want to property by listing key, Search for members/agents, Find all offices

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

RESO Web API standard based on OData V4 for real estate data exchange. Provides access to property listings, agents, and real estate data following RESO Data Dictionary standards. The API exposes 7 endpoints secured with bearer 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

27%

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.

50%

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: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RESO Web API to your agent

Capabilities

Start building with RESO Web API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

RESO Web API

Jentic AI Readiness Score

RESO Web 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