Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SimplyRETS, 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%2Fsimplyrets.com%2Fsimplyrets" | shStep 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%2Fsimplyrets.com%2Fsimplyrets" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with SimplyRETS API.
The SimplyRETS OpenHouses API
Single OpenHouse Endpoint
Integrate SimplyRETS into automated workflows
Query and filter SimplyRETS records by parameters
Monitor SimplyRETS operational status and events
GET STARTED
Patterns agents use SimplyRETS API for, with concrete tasks.
★ Developer Tools Operations
Use the SimplyRETS to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including the simplyrets openhouses API, single openhouse endpoint, the simplyrets listings API.
Call GET /openhouses to the simplyrets openhouses API
Automated openhouses Management
Automate openhouses operations by combining multiple SimplyRETS endpoints. Agents can single openhouse endpoint and then the simplyrets listings API in a single workflow.
Call GET /openhouses/{openHouseKey} to single openhouse endpoint, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SimplyRETS 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 'the simplyrets openhouses API', load the operation schema, and execute with Jentic-managed credentials
4 endpoints — the simplyrets api is an exciting step towards making it easier for developers and real estate agents to build something awesome with real estate data! the documentation below makes live requests to our api using the trial data.
METHOD
PATH
DESCRIPTION
/openhouses
The SimplyRETS OpenHouses API
/openhouses/{openHouseKey}
Single OpenHouse Endpoint
/properties
The SimplyRETS Listings API
/properties/{mlsId}
Single Listing Endpoint
/openhouses
The SimplyRETS OpenHouses API
/openhouses/{openHouseKey}
Single OpenHouse Endpoint
/properties
The SimplyRETS Listings API
/properties/{mlsId}
Single Listing Endpoint
What agents get from Jentic-routed access to this vendor.
Setup
Wiring SimplyRETS by hand means setting up HTTP basic auth and carrying those credentials across every property and open-house query yourself. Through Jentic you install once, import SimplyRETS from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
SimplyRETS puts the listing id in the URL path (/properties/{mlsId}, /openhouses/{openHouseKey}), so a rule can pin your agent to a single listing lookup, and since the exposed operations are all read-only property and open-house queries, the agent can retrieve but never modify listings. You choose the operations it may call, so it stays limited to the reads you allow.
Credential isolation
Your SimplyRETS 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 'search property listings' or 'find open houses', and Jentic returns the matching SimplyRETS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using SimplyRETS API through Jentic.
What authentication does the SimplyRETS use?
The SimplyRETS 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 the simplyrets openhouses API with the SimplyRETS?
Yes. Use the GET /openhouses endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SimplyRETS?
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 the simplyrets openhouses API through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'the simplyrets openhouses API'. Jentic returns the matching SimplyRETS operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SimplyRETS have?
The SimplyRETS exposes 4 endpoints covering openhouses, properties operations.
Can I limit what my agent is allowed to do with the SimplyRETS API?
Yes. Because Jentic One is self-hosted, your own rules decide which SimplyRETS operations and credentials the agent may use. SimplyRETS exposes only read-only property and open-house lookups (GET /properties, GET /properties/{mlsId}, GET /openhouses, GET /openhouses/{openHouseKey}), so you can allow just the reads you want and the agent can retrieve listings but never modify them. Since the listing id sits in the URL path, you can even pin the agent to a single property or open-house lookup.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically the simplyrets openhouses API, single openhouse endpoint. Covers 4 operations with basic authentication.
Use for: I need to the simplyrets openhouses API, I want to single openhouse endpoint, Search for the simplyrets listings API, Find all single listing endpoint
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
The SimplyRETS API is an exciting step towards making it easier for developers and real estate agents to build something awesome with real estate data! The documentation below makes live requests to our API using the trial data. To get set up with the API using live MLS data, you must have RETS credentials from your MLS, which you can then use to create an app with SimplyRETS. For more information. The API exposes 4 endpoints secured with basic authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>