Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey42 EndpointsREST
For Agents
Programmatically search listings, get listing by id. Covers 42 operations with apiKey authentication.
Use for: I need to listings, I want to listing by id, Search for similar listings, Find all address history
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Real estate data API for MLS listings, agents, clients, saved searches, estimates, and more. The API exposes 42 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Repliers API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Repliers 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.
1
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%2Frepliers.io%2Frepliers" | sh2
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%2Frepliers.io%2Frepliers" | 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.
Capabilities
What an agent can do with Repliers API.
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
Patterns agents use Repliers API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'search listings', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
42 endpoints — real estate data api for mls listings, agents, clients, saved searches, estimates, and more.
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
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
Jentic AI Readiness Score
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.
R
Repliers API
- AI-Aware (B)66/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
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).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
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.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
48%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
62%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
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.
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Repliers API through Jentic.
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.
GET STARTED