A valuation and market-intelligence platform across ten countries, against a French-first listings API. They overlap less than the category names suggest — but they do overlap.
PriceHubble AG is a Swiss company headquartered in Zurich, active in ten countries, whose core product is automated valuation and property market intelligence.
Stream.Estate is a real estate data API: 1,500+ aggregated sources, 50M+ deduplicated listings, one endpoint, self-service keys, France as the primary market plus Belgium.
One correction up front, because it is the most common thing written about PriceHubble and it is wrong: PriceHubble's API does return listings. Its documented offers/search endpoint gives you the advert's title, description, images, agency contact and the original advert URL, for both sales and rentals. What it does not give you is a bulk feed — and that distinction, not "valuation vs listings", is the real difference between these two products.
The same real estate data, two very different operating models.
| Criterion | Stream.Estate | PriceHubble |
|---|---|---|
| Primary purpose | Listings data feed — everything on the market, deduplicated | Automated valuation and property market intelligence |
| Returns real adverts | Yes — full listing records from 1,500+ sources | Yes — offers/search returns title, description, images, agency contact, original advert URL |
| Result ceiling per query | 30 items per page, paginated; count capped at 10,000 | offset max 1,000, limit max 500; totalItems accurate only below 1,500 |
| Historical depth of adverts | Per-advert change events (price, surface, pictures, expiry) | Rolling 5-year window, enforced; inactive offers carry endDate and daysOnMarket |
| Automated valuation (AVM) | No — market data to build one on | Yes — POST /api/v1/valuation/property_value with salePrice, range and confidence |
| Neighbourhood and market analytics | Price-per-m² indicators (average, median, time series) | Socio-economics, POI, isochrones, location scores, building projects, cadastre, house price indices |
| Push on change | Webhooks on saved searches — new ad, price, surface, pictures, expiry | Not documented publicly |
| Geographic coverage | France (primary) and Belgium | 10 countries: CH, FR, DE, AT, UK, JP, BE, CZ, SK, US (docs also reference ES and NL) |
| Published pricing | €0.01/item pay-as-you-go; €99 / €399 / €799 per month; Enterprise custom | Not published — no pricing page in any locale sitemap |
| Self-service signup | Yes — sign up and create a key, €5 in credits | No — "Request a demo"; credentials are issued in advance |
| Public API documentation | Public reference at docs.stream.estate | Public docs at docs.pricehubble.com, no login |
| Auth model | X-API-KEY header on every request | POST /auth/login/credentials, token valid 12 hours |
PriceHubble's offers/search endpoint is a bounded comparables search, and its own documentation says so in the limits. Pagination offset is capped at 1,000 and limit at 500, and totalItems is documented as "capped and is only accurate if there are less than 1'500 results". It also enforces a rolling five-year window: offers whose startDate is earlier than today minus five years are never returned, with the cutoff computed dynamically.
Within that window it is rich. You get endDate ("date when the offer disappeared from the market; only set for historical (inactive) offers"), daysOnMarket and isActive, so you can reason about how long something sat and at what price it left. For valuing a specific property against its neighbours, that is exactly the right shape.
What it is not designed for is ingesting a market. If your product needs every new listing in a region as it appears, a 1,500-result ceiling per query is a hard structural limit, not a plan tier. Stream.Estate is built the other way round: a full listings feed over 1,500+ aggregated sources, deduplicated, with webhooks that push new adverts and price changes to your endpoint as they happen.
So the honest framing is: PriceHubble answers "what is this property worth, and what did comparable ones do". Stream.Estate answers "what is on the market right now, everywhere, and tell me the moment that changes".
PriceHubble states it is active in 10 countries: Switzerland, France, Germany, Austria, the United Kingdom, Japan, Belgium, the Czech Republic, Slovakia and the United States. Its API filter documentation additionally references Spain and the Netherlands, which do not appear in that ten-country marketing list — worth checking with them if either matters to you.
Stream.Estate covers France as its primary market plus Belgium. If you operate across Europe or into Japan and the US, PriceHubble covers ground a French-first API simply does not, and no amount of framing changes that.
Product breadth is the second place PriceHubble is ahead. Beyond valuation and offer search, its public documentation covers socio-economic data, points of interest, isochrones, location scores, building projects, cadastre, house price indices, and transaction search and statistics — plus a white-label front-end layer for banks and agencies. Stream.Estate ships none of that; it ships listings.
Both publish readable API documentation without a login, which is not universal in this market.
PriceHubble does not publish pricing. No pricing page appears in any of its eleven locale sitemaps, and every call to action on the live site is "Request a demo" or "Log in". Authentication is by credentials issued to you in advance — POST /auth/login/credentials, returning a token valid for 12 hours ("expires_in": 43200) — so there is no path from landing page to first request without a conversation.
Stream.Estate publishes its plans: pay-as-you-go at €0.01 per item with no minimum commitment, Starter at €99/month (15,000 items included), Growth at €399/month (150,000 items), Scale at €799/month (350,000 items), and a custom Enterprise tier. New accounts get €5 in credits, and PropTech startups can apply for the Starter plan free for three months.
One caveat on PriceHubble's public site, in fairness to them: it was rebuilt on the day we checked it (the page source is stamped 2026-09-09), and several older pages — press, imprint, some product pages — now redirect to the homepage. Facts that were probably documented last week may simply be missing right now rather than withdrawn.
Every statement about PriceHubble above comes from a page published by PriceHubble or from a public source, read on the date shown. Products change: if something here has gone out of date, tell us.
One API key, one endpoint, deduplicated real-time data.