canonical: https://jentic.com/apis/apillow.co/apillow # Apillow Zillow Property Data The APIllow API returns detailed Zillow property data from a city, ZIP code, street address, Zillow Property ID, or listing URL. Each property comes back with dozens of fields including Zestimates, tax history, school ratings, and comparable sales, and requests can be narrowed with property-type and price-range filters. A results endpoint retrieves batch output, with CSV export available, and a usage endpoint reports consumption against the monthly quota. ## For AI agents Look up detailed Zillow property data by address, ZIP, city, Zillow ID, or URL, including Zestimates, tax history, school ratings, and comparable sales. ## Scope Does not list properties for sale, handle mortgages, or manage leases. Use for retrieving Zillow property data such as Zestimates, tax history, and comparable sales only. ## Capabilities - Retrieve Zillow property data by address, ZIP, city, Zillow Property ID, or URL - Return Zestimates, tax history, school ratings, and comparable sales for a property - Narrow a request with property-type and price-range filters - Fetch batch job results for a submitted property request, with CSV export - Report account usage against the monthly quota ## Use cases ### AI agent answering property questions A real-estate assistant needs factual property details when a user names an address. Through Jentic the agent searches for getting Zillow property data, loads the property lookup with the API key already injected, and returns the Zestimate, tax history, and school ratings for that address. The agent answers from live data rather than a stale cache. Example prompt: Call POST `/v1/properties` with a street address and return the Zestimate, tax history, and school ratings ### Property valuation lookup An investor's agent compares a home's estimated value against recent comparable sales. The APIllow API returns a Zestimate alongside comparable sales and tax history for a property, giving the agent the inputs for a quick valuation read. This replaces manually opening Zillow for each candidate property. Example prompt: Call POST `/v1/properties` for a Zillow Property ID and summarize the Zestimate against its comparable sales ### Area market scan An agent surveying a neighbourhood pulls properties in a ZIP code within a target price band. The APIllow API accepts a ZIP or city plus property-type and price-range filters and returns matching properties, up to the per-plan result limit, which an agent can export as CSV from the results endpoint. This builds a market snapshot without scraping listing pages. Example prompt: Call POST `/v1/properties` with a ZIP code and a price-range filter, then GET `/v1/results/{job_id}` to collect the output ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/properties` | Get property data by address, ZIP, city, Zillow Property ID, or URL | | GET | `/v1/results/{job_id}` | Retrieve batch job results for a submitted request | | GET | `/v1/usage` | Report account usage against the monthly quota | ## Key resources - **Properties** — Look up property data by address, ZIP, city, Zillow Property ID, or URL with type and price filters - **Results** — Retrieve batch job output for a submitted request, with CSV export - **Usage** — Report account consumption against the monthly quota ## 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:** 69 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 58 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 75 / 100 - **View full report:** https://jentic.com/apis/apillow.co/apillow/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 the APIllow API by hand means obtaining a key, sending it in the X-API-Key header, and shaping each property request with its address or ID inputs, type and price filters, and per-plan result limits. Through Jentic you install once, import APIllow from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The APIllow API is read-only: it looks up property data, returns batch results, and reports account usage. You choose the operations your agent may call, so you can allow the property-data lookup and leave the usage endpoint out, or include both, and the agent can never reach an operation you have not allowed. - **Credential handling:** Your APIllow 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 'get Zillow property data' or 'look up a Zestimate', and Jentic returns the matching APIllow operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **RentCast API** — Provides property records, value estimates, and rent estimates from its own data rather than Zillow - **ATTOM Data API** — A broad property data provider covering assessments, deeds, and ownership records - **SimplyRETS API** — Serves active MLS listings, which pair with APIllow's valuation and tax data ## FAQ ### What authentication does the APIllow API use? The APIllow API authenticates with an API key sent in the X-API-Key request header, per its OpenAPI spec. A free key covers a monthly allowance of properties with no card required. Through Jentic the key is stored once and injected at call time, so the agent never sees the raw key. ### Can I get a property's Zestimate and comparable sales? Yes. Call POST `/v1/properties` with an address, ZIP, Zillow Property ID, or URL and the response includes the Zestimate, tax history, school ratings, and comparable sales among its property fields. You can narrow which properties come back with property-type and price-range filters. ### What are the rate limits for the APIllow API? The OpenAPI spec does not define per-second rate ceilings. Instead each plan sets how many properties a single request may return and a monthly allowance, and you can read current consumption with GET `/v1/usage.` Check the APIllow documentation for your plan's figures before running large area scans. ### Is there an APIllow MCP server? You don't need an MCP server to give your agent the APIllow API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls operations such as POST `/v1/properties` on demand without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the APIllow API? Yes. Write a rule that allows only the property-data lookup and the usage check, so the agent can read property details and monitor consumption and nothing else, and every call it makes is logged. Because the API is read-only, there are no write operations to worry about, but you still decide which reads are in scope. ### How do I get Zillow property data through Jentic? Search Jentic for 'get Zillow property data', load the POST `/v1/properties` operation, and run it after your key is stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.