Property Sourcing

#MCP server

https://platform.casafari.com/mcp/property-sourcing: Streamable HTTP, OAuth 2.1 sign-in in the browser with a Casafari API and MCP Platform account, or a platform API key. Its tools are named property-sourcing_<tool>, and it also has account_status. Also on the one server for every product, https://platform.casafari.com/mcp. How to connect.

#How the service describes itself

The backend service's own initialize instructions, from its source:

Property Sourcing: homes for sale or rent across the covered countries, one record per home merged from portals and agency websites. Turn a place name into location ids with locations_search first (free, on this server). property-sourcing_search finds homes by location, type, price, size, rooms and features, and by what only the merged record knows: how far below our estimated market value the asking price is (below_market_pct), days on the market across all sources (days_on_market), private or exclusive sellers, and when a home was first seen or last changed (first_seen_after, changed_after, sort newest). Every result carries its days on the market, market value and gap, and seller flags. Pass a page's next to property-sourcing_next_page for more. property-sourcing_get_property reads one home by its prop_ id: sources (every portal and agency listing of it, with asking prices and links) and price_story (price cuts, days on the market across relistings, gap to market value, price spread between agencies). property-sourcing_resolve_listing finds the home behind a portal or agency link or a listing reference. property-sourcing_get_closing_prices gives the aggregated registered sale prices of similar homes near a home (Spain, France, Italy, Poland, Portugal), with count, median and range per square metre and the closest sales; Portugal answers an official area median. Prices from search, get_property and resolve_listing are asking prices from the listings, never closing prices; a price of null means on request; closing prices are a different thing and always say so and name their source. Market value is our estimate, not an asking or a closing price. Search has no plain-language filter: express what the person wants with types, features, exclude_features, the filters and ranges. account_status is free and shows remaining tokens and a payment link when tokens run out.

#MCP tools

#REST API

5 operations on the platform's REST API, base https://platform.casafari.com/v1/property-sourcing, with a platform API key from the console (platform API keys), billed in tokens (1 token = EUR 0.04). Casafari clients with a contract also have 5 operations on the existing API at https://api.casafari.com (bearer token), listed after them under Existing API (contract clients). The same list with more detail: Property Sourcing REST API.

#Existing API (contract clients)

On the existing REST API at https://api.casafari.com, with a bearer token from your account's email and password (how to get one): for Casafari clients with a contract. The existing API.

#Pricing

1 token = EUR 0.04. Free: 1,000 tokens for 30 days; pay as you go: prepaid credits; Agent: EUR 49 a month, or EUR 39 a month billed yearly, with 1,500 tokens a month; Agency: EUR 149 a month, or EUR 119 a month billed yearly, with 5,000 tokens a month; Custom: talk to Casafari. See Pricing and platform API keys.

#What is Property Sourcing?

Property Sourcing is the REST search product of Casafari, the AI agent-native real estate data intelligence platform, for finding residential and commercial properties for sale or for rent in its deduplicated, cleaned property graph, where every property is one record with its full price and status history, however many agencies and portals advertise it. Built for AI agents as well as buyer's agents, agents prospecting for mandates, investors and proptech developers, it offers structured search, plain-language search, single-property reads and resolution of any portal or agency link or reference to its property. One request body works across Andorra, the United Arab Emirates, Austria, Belgium, Switzerland, Germany, Spain, France, Greece, Italy, Luxembourg, Monaco, Poland, Portugal, San Marino and the United States, on data from the most complete property index in Europe.

#Use cases

#Questions about Property Sourcing

• How do I find every property for sale in a town that matches my client's brief, without duplicates?
• Can I search by a plain-language description like 'sea view, needs renovation, near the beach'?
• Which properties in this area have the lowest price per square metre?
• How long has this property been on the market and what did it originally ask?
• Is this link my client sent the same property as the one I already have?
• How many agencies are advertising this property and at what prices?
• Can I filter by features like a rental licence, or exclude rented-out, life-annuity and business-transfer properties?
• What are the newest properties that came on the market in my area this week?
• Does the API return the seller's phone number or email?
• Does the same request work for Spain, France, Italy, Germany, Portugal and Greece?
• How many results can one search return and how do I page?
• What does a price of 0 mean in the results?
• How much does a search cost?
• Can an AI agent call this API directly with a user's prompt?

#MCP and REST compared

Over MCP: 5 tools. Over REST: 10 operations. Available over both.

• Equivalent: property-sourcing_search and POST /v1/property-sourcing/searches.
• Equivalent: property-sourcing_next_page and GET /v1/property-sourcing/searches/{cursor}.
• Equivalent: property-sourcing_get_property and GET /v1/property-sourcing/properties/{property_id}.
• Equivalent: property-sourcing_resolve_listing and POST /v1/property-sourcing/properties/resolve.
• Equivalent: property-sourcing_get_closing_prices and GET /v1/property-sourcing/properties/{property_id}/closing-prices.

Only over REST: POST /api/v1/properties/match-by-listings (existing API), POST /api/v1/properties/search (existing API), GET /api/v1/properties/search/{property_id} (existing API), POST /api/v1/properties/smart-links (existing API), POST /api/v2/properties/search (existing API).

Details: MCP and REST compared.

#Ask your assistant