Moving from the existing Casafari API
Already a Casafari API customer? Your token keeps working, and the existing API's reference is now on this site. Log in to your API account to see your token.
Short answer: for the REST API, nothing changes: if you are a Casafari client today, you keep the existing API, and nothing moves on its own. For MCP, Casafari's MCP servers are now the platform's, for everyone: mcp.casafari.com is the legacy gateway, still answering, moving to https://platform.casafari.com/mcp/<product>.
What stays as it is
If you have a Casafari account with API access, you are an existing client. Your contract, your prices, your token and your access stay as they are:
- the Casafari web app;
- the existing REST API and its documentation at docs.api.casafari.com (its reference is also on this site: Existing API customers).
MCP: the platform's servers
The old MCP gateway, mcp.casafari.com, is the legacy gateway: it still answers while its servers move. Every Casafari MCP server is now on the platform, existing clients included: one server for every product, https://platform.casafari.com/mcp, and each product's own server under https://platform.casafari.com/mcp/<product> (the list).
Already a Casafari client? Use the same server: sign up at https://platform.casafari.com/console/, and if you have a contract, Casafari sets your account up on the Custom plan. Steps for every client: Connect a client.
Who the Platform is for
The Casafari API and MCP Platform at https://platform.casafari.com is self-serve: people and teams who want to start on their own, as a developer, an AI agent or a small team, and, for MCP, existing Casafari clients too. Start with Connect to the Casafari Platform.
How the concepts map
| Existing Casafari | Casafari Platform | |
|---|---|---|
| MCP | Legacy gateway mcp.casafari.com, still answering, moving | One server for every product, https://platform.casafari.com/mcp; or one per product, https://platform.casafari.com/mcp/<product> |
| REST | The existing API at api.casafari.com | https://platform.casafari.com/v1/<product>, for example Location Lookup, Area Insights, Property Sourcing, High Potential Seller Leads, Comparables and Alerts |
| Credential for REST | A static token, from POST /login with your Casafari account | An API key (cf_sk_...) from the console |
| Credential for MCP | — | OAuth 2.1 with a Platform account, with dynamic client registration, or an API key |
| Price | Your contract | Tokens: Free 1,000 tokens for 30 days; 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, excluding VAT; Custom; extra usage as credits at EUR 0.04 a token (Pricing) |
| Terms | Your contract | Platform Terms of Use |
An existing token is not a Platform key, and a Platform key does not work on the existing API.
No account linking
A Platform account is separate from a Casafari account. There is no linking and no migration of REST users, tokens, subscriptions or usage in either direction. For MCP you open a Platform account; with a contract, Casafari sets it up on the Custom plan.