RealtyAPI
Official vendor OpenAPI document · agent-readyHR recruitingRecruiting AtsapiKey5 EndpointsREST
For Agents
Programmatically search properties, get property details. Covers 5 operations with apiKey authentication.
Use for: I need to properties, I want to property details, Search for map search, Find all pricing history
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
RealtyAPI provides real estate data from Zillow, Redfin, Realtor, Airbnb, and more through a unified REST API and GraphQL interface. The API exposes 5 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the RealtyAPI to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RealtyAPI, 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%2Frealtyapi.io%2Frealtyapi" | 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%2Frealtyapi.io%2Frealtyapi" | 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 RealtyAPI API.
Search Properties
Get Property Details
Map Search
GraphQL Query
Access RealtyAPI hr recruiting resources via REST API
Use Cases
Patterns agents use RealtyAPI API for, with concrete tasks.
★ HR and Recruiting Operations
Use the RealtyAPI to perform hr recruiting operations programmatically. The API provides 5 endpoints covering core functionality including search properties, get property details, map search.
Call GET /properties/search to search properties
Automated GraphQL Management
Automate graphql operations by combining multiple RealtyAPI endpoints. Agents can get property details and then map search in a single workflow.
Call GET /properties/{propertyId} to get property details, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RealtyAPI 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 properties', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
5 endpoints — realtyapi provides real estate data from zillow, redfin, realtor, airbnb, and more through a unified rest api and graphql interface.
METHOD
PATH
DESCRIPTION
GET
/properties/search
Search Properties
GET
/properties/{propertyId}
Get Property Details
GET
/properties/map-search
Map Search
GET
/properties/{propertyId}/pricing-history
Get Pricing History
POST
/graphql
GraphQL Query
GET
/properties/search
Search Properties
GET
/properties/{propertyId}
Get Property Details
GET
/properties/map-search
Map Search
GET
/properties/{propertyId}/pricing-history
Get Pricing History
POST
/graphql
GraphQL Query
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the RealtyAPI by hand means passing its X-API-Key header, building property search and map-search queries, and composing GraphQL payloads for the /graphql endpoint yourself. Through Jentic you install once, import the RealtyAPI from the API Directory, store the key once, and your agent calls it.
Permission scoping
The RealtyAPI mixes read endpoints like /properties/{propertyId} with a POST /graphql, so you limit the agent to the operations it needs, such as searching properties or reading pricing history. It only calls the operations you allow, so the GraphQL endpoint stays out of scope unless you add it.
Credential isolation
Your RealtyAPI 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 properties' or 'get a property's pricing history', and Jentic returns the matching RealtyAPI 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 RealtyAPI API through Jentic.
What authentication does the RealtyAPI use?
The RealtyAPI uses an API key passed in the `X-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 properties with the RealtyAPI?
Yes. Use the GET /properties/search endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RealtyAPI?
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 properties through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search properties'. Jentic returns the matching RealtyAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the RealtyAPI have?
The RealtyAPI exposes 5 endpoints covering graphql, properties operations.
Can I limit what my agent is allowed to do with the RealtyAPI?
Yes. Because Jentic One is self-hosted and you set the rules, you decide which RealtyAPI operations your agent may call, so you can allow read-only endpoints like GET /properties/search, GET /properties/{propertyId}, and GET /properties/{propertyId}/pricing-history while keeping everything else out of scope. The POST /graphql endpoint is only reachable if you explicitly add it, so an agent restricted to property lookups cannot run arbitrary GraphQL queries. Your API key is stored once by your own instance and injected only for the operations you have permitted.
GET STARTED