canonical: https://jentic.com/apis/simplyrets.com/simplyrets

# SimplyRETS

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.

## For AI agents

Programmatically the simplyrets openhouses API, single openhouse endpoint. Covers 4 operations with basic authentication.

## Scope

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

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'the simplyrets openhouses API', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/openhouses` | The SimplyRETS OpenHouses API |
| GET | `/openhouses/{openHouseKey}` | Single OpenHouse Endpoint |
| GET | `/properties` | The SimplyRETS Listings API |
| GET | `/properties/{mlsId}` | Single Listing Endpoint |

## Key resources

- **openhouses** — Operations related to openhouses
- **properties** — Operations related to properties

## AI readiness

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.

- **Score:** 41 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 70 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/simplyrets.com/simplyrets/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.