Real estate · Reference plans
Real Estate Master Stack is API Aha's dual-meter property family: Data Credits for bounded collector reads, Premium Requests for valuation and intelligence operations. The ladder below mirrors the retained pricing artifact — it is a reference package table, not a checkout path and not a claim that the family is open for subscription.
How a call becomes a decision
Public listing URLs, addresses, and market labels enter bounded collectors. Dollar figures are scripted. Optional intelligence endpoints add labeled signals — never invented occupancy, never a fabricated rent floor.
Buyer-surface collector map
Green nodes are on the published buyer surface. Staged collectors (Redfin, Crexi, dedicated Zillow-named routes, extra international pulls) stay off the live ring until they clear configuration and evidence. We do not advertise them as available coverage.
Advertised operations
Every path listed here is present on the Real Estate Master Stack route manifest buyer surface. This is a capability inventory, not a live-verification badge and not a total endpoint count.
straight pull
Straight property detail pulls plus focused field extracts and a small batch surface on the buyer path.
POST /api/realestate/realtorProperty detail collectPOST /api/realestate/realtor-photosPhotos field-extractPOST /api/realestate/realtor-addressAddress field-extractPOST /api/realestate/realtor-pricePrice field-extractPOST /api/realestate/realtor-batchDetail batch collectstraight pull
Listing, host, availability, and pricing collectors with a batch path — billed as bounded Data Credits.
POST /api/realestate/airbnbSTR listing collectPOST /api/realestate/airbnb-availabilityAvailability field-extractPOST /api/realestate/airbnb-hostHost signals field-extractPOST /api/realestate/airbnb-pricingPricing field-extractPOST /api/realestate/airbnb-batchSTR batch collectstraight pull
A Zoopla property detail collector on the buyer surface. Other international collectors remain staged off the buyer path.
POST /api/realestate/zoopla-propertyZoopla property detailstraight pull
Generic property and listing collectors that accept a public detail URL or address-shaped input. No dedicated single-portal route is claimed beyond the named collectors above.
POST /api/realestate/propertyProperty detailPOST /api/realestate/listings-by-urlListings by URLPOST /api/realestate/property-factsProperty facts field-extractPOST /api/realestate/property-priceProperty price field-extractPOST /api/realestate/property-mediaProperty media field-extractPOST /api/realestate/properties-batchProperties batchPOST /api/realestate/bulk-listingsBulk listings (uncapped record billing)Documented uncapped per-record billing exception on Data Credits.valuation
Deterministic valuation and deal surfaces. Dollar figures come from scripted models; optional narration never invents a number.
POST /api/realestate/valueProperty strategy valuatorConsensus value + confidence band, LTR/STR blocks, verdict. Deal Score is tier-gated on Ultra+.POST /api/realestate/comp-valueComp valuatorSubject vs sold comps → estimate, p25/p75 range, $/sqft position.POST /api/realestate/deal-finderDeal finderZIP scan ranked by discount to comp-adjusted value.intelligence
Premium signal endpoints that bill Data Credits for record reads plus one Premium Request per analysis operation. Outputs are labeled signals — not appraisals.
POST /api/realestate/ai-price-cut-signalPrice-cut signalPOST /api/realestate/ai-pricing-recencyPricing activity recencyPOST /api/realestate/ai-market-heatMarket heat indexPOST /api/realestate/ai-live-pricing-percentileLive pricing percentilePOST /api/realestate/ai-offer-competitivenessOffer competitivenessPOST /api/realestate/ai-compset-qualityComp-set quality scorePOST /api/realestate/ai-price-trendPrice trend signalPOST /api/realestate/ai-estimate-divergenceEstimate divergence signalExplicitly not advertised
Implemented handlers exist but are excluded from the buyer launch surface until collector configuration and evidence land.
Handlers exist in-repo; they are not on the published OpenAPI / route-manifest buyer path yet.
No dedicated Zillow route is published. Public listing URL intake accepts detail URLs generically — that is not a Zillow product claim.
Implemented but excluded from the buyer launch surface (dormant configuration).
Reference packages
Numbers are read from the same catalog package reference used by /pricing and /catalog/real-estate-master-stack. They are not a separate hard-coded ladder. Direct-channel fee treatment is coordinated with the platform pricing SSOT — this page does not invent a second set of figures.
Basic
Pro
Ultra · common pick
Mega
How it meters: Data Credits bill bounded supplier record reads with requestUnits = min(30, max(1, recordsRead)); Premium Requests add one analysis-operation unit on the 20 premium endpoints. /bulk-listings is the documented uncapped per-record exception.
| Capability | Basic | Pro | Ultra | Mega |
|---|---|---|---|---|
| Standard collectors (markets, rentals, property pulls) | Included (PAYG) | Included | Included | Included |
| Premium valuation: /value, /comp-value, /deal-finder | PAYG access | Included access | Included access | Included access |
| Remaining premium + AI intelligence endpoints | PAYG access | Not on plan | Included access | Included access |
| Data Credits included / month | 0 (pay per use) | 10,000 | 25,000 | 100,000 |
| Premium Requests included / month | 0 (pay per use) | 250 | 1,500 | 5,000 |
| Data Credit overage | $0.02 | $0.02 | $0.015 | $0.01 |
| Premium Request overage | $0.20 | $0.20 | $0.15 | $0.10 |
Billing shape
Standard collector work bills Data Credits. Premium valuation and AI intelligence bill both meters. /bulk-listings is the documented uncapped per-record exception; other calls stay under the per-call credit cap.
Access boundary
This page documents the reference ladder and buyer-surface map. Direct API keys are not publicly issued. RapidAPI hub links appear on API Aha only after full-surface buyer evidence is retained. Prefer the catalog status over any marketing shorthand.