canonical: https://jentic.com/apis/repliers.io/repliers # Repliers API Real estate data API for MLS listings, agents, clients, saved searches, estimates, and more. The API exposes 42 endpoints secured with apiKey authentication. ## For AI agents Programmatically search listings, get listing by id. Covers 42 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Search listings - Get listing by ID - New NLP prompt search - Query and filter Repliers API records by parameters - Monitor Repliers API operational status and events ## Use cases ### Developer Tools Operations Use the Repliers API to perform developer tools operations programmatically. The API provides 42 endpoints covering core functionality including search listings, get listing by id, get similar listings. Example prompt: Call POST `/listings/search` to search listings ### Automated AI Search Management Automate ai search operations by combining multiple Repliers API endpoints. Agents can get listing by id and then get similar listings in a single workflow. Example prompt: Call GET `/listings/{id}` to get listing by id, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Repliers 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 tokens manually. Example prompt: Search Jentic for 'search listings', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/listings/search` | Search listings | | GET | `/listings/{id}` | Get listing by ID | | GET | `/listings/{id}/similar` | Get similar listings | | GET | `/listings/{address}/history` | Get address history | | GET | `/listings/deleted` | Get deleted listings | | POST | `/buildings/search` | Search buildings | | POST | `/nlp/prompts` | New NLP prompt search | | GET | `/nlp/prompts` | Filter prompts | ## Key resources - **AI Search** — Operations related to AI Search - **Agents** — Operations related to Agents - **Buildings** — Operations related to Buildings - **Clients** — Operations related to Clients - **Directory** — Operations related to Directory ## 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:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 52 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/repliers.io/repliers/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 ``` ## Why Jentic - **Setup:** Wiring Repliers by hand means setting its REPLIERS-API-KEY header on every request, building listing and building search bodies, and tracking listing ids across search, detail, and history calls yourself. Through Jentic you install once, import the Repliers API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Repliers puts the listing id in the URL path (`/listings/{id}`), so a rule can pin your agent to reading a listing and its similar and history data. You choose the operations it may call, so if you grant only search and read the agent never runs anything beyond lookups. - **Credential handling:** Your Repliers API key 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. - **Discovery method:** Agents search Jentic by intent such as 'search listings' or 'get a listing's price history', and Jentic returns the matching Repliers 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 Repliers API use? The Repliers API uses an API key passed in the `REPLIERS-API-KEY` 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 search listings with the Repliers API? Yes. Use the POST `/listings/search` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Repliers 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 search listings through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search listings'. Jentic returns the matching Repliers API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Repliers API have? The Repliers API exposes 42 endpoints covering ai search, agents, buildings operations. ### Can I limit what my agent is allowed to do with the Repliers API? Yes. Jentic One runs self-hosted, so your own rules decide which Repliers operations and credentials your agent may use. Because Repliers puts the listing id in the URL path, such as GET `/listings/{id}`, you can pin the agent to reading a listing and its similar and history data. If you grant only the search and read operations, the agent can look up listings and buildings but never run anything beyond those lookups.