Reonomy Property API
66
AI ReadinessAI-Aware (B)66/100
Agent-ready OpenAPI document · curated by JenticMaps GeolocationPlaces Searchbearer8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Search US commercial properties by filters, location, or address, then pull details, ownership, and parcel shapes from Reonomy. Read-only, bearer token auth.
Use for: Find industrial properties in Newark, NJ built after 1990, Search for office buildings within 2 miles of this point, Who owns 123 Main Street, Boston?, Get the sales history and mortgage details for this property
Not supported: Does not handle property listings for sale or lease, transactions, or residential home valuations. Use for searching US commercial property records, ownership, and parcels only.
Jentic publishes the only available OpenAPI specification for the Reonomy Property API, keeping it validated and agent-ready. The Reonomy Property API searches US commercial real estate and returns the record behind each property: building characteristics, tax assessments, sales history, mortgage information, ownership, and parcel shape. Searches filter by asset_type such as office, retail, industrial, or multifamily, by state, city, and zip_code, and by ranges for building area, lot area, year built, sale date, and assessed value. Geographic search covers a radius around a point, a polygon, or a bounding box, and properties can also be resolved from a street address or found inside a GeoJSON boundary.
Install Jentic One Beta
Connect the Reonomy Property API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reonomy Property 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%2Freonomy.com%2Freonomy" | 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%2Freonomy.com%2Freonomy" | 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 Reonomy Property API.
Search commercial properties by asset_type, location, building size, year built, and sale date
Find properties within a radius, polygon, or bounding box
Resolve a street address to a Reonomy property record
Pull building, tax assessment, sales, and mortgage details for a property
Read a property's current owner, owner type, mailing address, and ownership history
Fetch a property's parcel boundary as GeoJSON
Retrieve details for many properties at once from a list of property_ids
Use Cases
Patterns agents use Reonomy Property API for, with concrete tasks.
★ Agent-run commercial property prospecting
A broker's agent turns a brief like 'industrial buildings over 50,000 sq ft in New Jersey that sold before 2015' into a Reonomy search with asset_type, state, building_area_sqft, and sale_date filters, then reads ownership for each hit to build a call list.
Call POST /property/search with filters asset_type ['industrial'], state ['NJ'], and building_area_sqft min 50000, then GET /property/{propertyId}/ownership for each result
Site selection by geography
For a site search around a target location, the geo search takes type set to radius with a center and radius_miles, or a polygon or bounding_box, combined with the same property filters, so an agent can list candidate retail or office sites in a trade area.
Call POST /property/geo/search with type set to radius, a center point, radius_miles set to 2, and filters asset_type ['retail']
Address to ownership lookup
Given only a street address, the agent resolves it to a Reonomy property, then reads the ownership record for the owner name, owner type, and mailing address, and the property details for tax and mortgage context.
Call POST /property/address/search with street_address, city, state, and zip_code, then GET /property/{propertyId}/ownership for the returned property
Parcel mapping for a portfolio
Parcel boundaries come back as GeoJSON, so an agent can map a portfolio by fetching each property's parcel, or find every parcel inside a drawn boundary with the GeoJSON parcel search.
Call POST /property/parcel/geojson/search with geometry set to the district polygon, then GET /property/{propertyId}/parcel for parcels of interest
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for the reonomy property api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/property/search
Search properties with filters
POST
/property/geo/search
Search properties by geolocation
POST
/property/address/search
Resolve property by address
GET
/property/{propertyId}
Get property details
GET
/property/{propertyId}/ownership
Get property ownership
GET
/property/{propertyId}/parcel
Get parcel shape
POST
/property/bulk
Get details for multiple properties
POST
/property/search
Search properties with filters
POST
/property/geo/search
Search properties by geolocation
POST
/property/address/search
Resolve property by address
GET
/property/{propertyId}
Get property details
GET
/property/{propertyId}/ownership
Get property ownership
GET
/property/{propertyId}/parcel
Get parcel shape
POST
/property/bulk
Get details for multiple properties
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
Reonomy Property API
- AI-Aware (B)66/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability60
Security84
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
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).
100%
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.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
33%
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.
50%
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.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
84
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
84%
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 Reonomy by hand means handling its bearer access token, building nested filter objects with min and max ranges, and choosing between radius, polygon, and bounding_box geo search shapes. Through Jentic you install once, import Reonomy from the API Directory, store the token once, and your agent calls it.
Permission scoping
Reonomy puts the property id in the URL path for detail, ownership, and parcel reads (/property/{propertyId}/...), so a rule can tie those calls to a specific property, while searches carry their criteria in the request body. Every operation is a read, so scoping here is about which lookups and how broad a search your agent may run.
Credential isolation
Your Reonomy access token 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 'find who owns a commercial property' or 'search properties within a radius', and Jentic returns the matching Reonomy operation with its input schema so the agent builds the right filters.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Reonomy Property API through Jentic.
Why is there no official OpenAPI spec for the Reonomy Property API?
Reonomy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Reonomy Property API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What authentication does the Reonomy Property API use?
Per its OpenAPI spec, the Reonomy Property API uses an access token obtained from Reonomy, sent as a bearer token in the Authorization header. Through Jentic, the token is stored encrypted by your own Jentic One instance and injected at execution time.
Can I find who owns a commercial property with Reonomy?
Yes. Resolve the property with POST /property/address/search, then call GET /property/{propertyId}/ownership for the current owner, owner type, mailing address, and ownership history. Property detail calls accept an exclude_pii flag when personal data should be left out.
What are the rate limits for the Reonomy Property API?
The OpenAPI spec does not give a number; it notes that a 429 response means a rate limit or API credit limit was exceeded. Check your Reonomy agreement or https://www.reonomy.com for current limits.
Is there a Reonomy MCP server?
You don't need an MCP server to give your agent Reonomy. Jentic connects it directly from the API Directory: import it, store your access token once, and your agent calls it, discovering the search and detail operations as it needs them.
Can I limit what my agent is allowed to do with the Reonomy Property API?
Yes. You might allow only POST /property/address/search and GET /property/{propertyId}/ownership for an owner-lookup agent, so it answers 'who owns this address' without running broad market searches or bulk detail pulls against your credit allowance. Every call is logged.
GET STARTED