Back to AI app discovery
Rareplace Hospitality Intel API logo

Rareplace Hospitality Intel API

STR market data API for AI agents. Nashville & Austin.

Developer Tools

Screenshots

Rareplace Hospitality Intel API Homepage

About Rareplace Hospitality Intel API

Rareplace Hospitality Intel is a REST API returning live short-term rental market data for Nashville, TN and Austin, TX. Structured JSON, designed for machine consumption rather than human dashboards. WHAT IT RETURNS - occupancy_rate — share of available nights booked, as a trailing 365-day estimate - adr — average daily rate, USD - revpar — revenue per available room - median_nightly_rate — median rate, USD - active_listings — active STR listings in the market - demand_score — 0-100 composite: occupancy 40%, review velocity 40%, listing count 20%, each normalised against the city maximum for that period - review_recency_index — share of a market's all-time reviews posted in the trailing twelve months - pricing_methodology — which price definition the rate figures use - period — start and end date of the data period Nashville is segmented by council district (1-35). Austin by 43 ZIP codes. READING THE RATE FIGURES Every metrics object carries pricing_methodology. list_price is the host's advertised nightly rate; quoted_price is a live booking quote for near-term dates. The upstream source changed this between Q3 2025 and Q2 2026, so rate figures either side of that boundary are not comparable — a 60% ADR move across it is the measurement changing, not the market. /v1/market/history enforces this: when the two most recent periods differ in methodology it returns trend: null and sets meta.trend_comparable to false with a reason. Check trend_comparable before using trend. demand_score is normalised within each period, so it measures standing inside its own quarter and is not comparable across periods. DATA SOURCE All figures derive from InsideAirbnb. Vrbo and direct bookings are not captured — material in family and group-travel submarkets. Occupancy is a trailing 365-day estimate, not a figure for the labelled quarter. ENDPOINTS GET /v1/market?neighbourhood=District+19 Current period metrics for any Nashville district or Austin ZIP. GET /v1/market/top?limit=10 Top markets by demand score across both cities. GET /v1/markets/zip?zip=78702 Returns a query object and a markets array. Nashville ZIPs often span several districts, so the array holds one entry per match; Austin ZIPs map one-to-one. Iterate markets in both cases — nothing branches on city. A ZIP matching nothing costs zero credits. GET /v1/market/history?neighbourhood=District+19 Every loaded quarter, with a trend object when periods are methodologically comparable and trend: null with a stated reason when they are not. GET /v1/markets/list Paginated list of all covered markets. GET /v1/market/preview Public — no key, no credits. Top Nashville market, top Austin market, and the overall runner-up. Safe for public pages and demos. GET /v1/hospitality/openapi.json Full OpenAPI 3.0.3 spec at a stable unauthenticated URL. Works with LangChain OpenAPIToolkit, n8n HTTP nodes, and any framework that generates tools from a spec. Every data endpoint also answers on a /v1/hospitality/ path. Both call the same handler at the same cost; the original paths are permanent. BUILT FOR AGENT FRAMEWORKS LangChain: load the spec via OpenAPIToolkit and auto-generate tools. demand_score gives an LLM one comparable signal across markets within a period. n8n: HTTP Request node with an x-api-key header. Flat JSON, no nested parsing for the core metrics. OpenAI Function Calling / Agents SDK: import the spec directly. Field names are consistent across endpoints and across both cities. CrewAI / AutoGen / LlamaIndex: any framework that can make an authenticated HTTP call. Every meta block includes credits_remaining so agents can self-monitor budget. A 404 returns a structured help object naming valid query formats rather than raising — an agent can correct its own query without a human in the loop. AUTHENTICATION API key in the x-api-key header. Not Authorization: Bearer. Keys are provisioned on purchase — no waiting, no approval. PRICING Credit packs in USDC. No subscription, no recurring

Ratings & reviews

Announcements

No announcements yet.

Community activity

Recent follows, shares, ratings, and collection saves for Rareplace Hospitality Intel API.

No community activity yet. Follow or share Rareplace Hospitality Intel API to get things started.

Comments

Appz prompt

What kind of project would you trust Rareplace Hospitality Intel API with first?

Sign in to join the discussion.