Part of Quanthome Data
Your own systems and AI tools query Quanthome data directly.
No more copy paste into Excel spreadsheets. The API puts the same data as the platform inside the systems your team already uses. MCP (Model Context Protocol) connects Claude, ChatGPT and your own AI tools to it directly. Both are part of Quanthome Data and billed separately from the platform license, with no migration to manage.
What you get
One access layer connects Quanthome data to your stack: a REST API for your applications and an MCP server for your AI assistants and agents.
Capabilities
One key reaches the same records from your applications and from your AI tools.
Feed BI dashboards, enrich a CRM, and supply financial models with building, fund, transaction and ESG data, queried straight from your own systems.
Agent-ready by design. Claude, ChatGPT and your own agents query Quanthome data directly, and their answers rest on figures linked to their source.
Connect the API or MCP key in a few lines of configuration. Your stack stays as it is.
Each user and each agent reaches only the data you allow.
Use cases
These jobs run inside the systems and AI tools your team already uses, on the same records as the platform.
See institutional deals with buyer, seller, price and yield.
Aggregate direct lines and fund holdings into one exposure view, resolve fund positions down to the building, and read a picture that stays current, so each reporting cycle is a refresh, not a rebuild.
Describe the question in plain language and get a dashboard that combines your data and Quanthome market data, kept live for the next question.
Why Quanthome
Three things make the connection worth building.
Direct and indirect, down to the building, structured and matched before any tool or agent reads it.
Each value links back to the record it came from.
The assistants and agent frameworks you run today, and the ones you switch to.
Two offerings
See what others can't. Decide before others do.
Swiss real estate data, three ways in: the platform for the team that works in it all day, the API for the systems you already use, and MCP for your own AI tools.
Inside Quanthome Data
Grow the portfolio, not the back office.
We deliver the result. On data structured by the Quanthome Data Engine, our engineers and agents build and run your data-intensive workflows.
Explore Quanthome WorkforceBoth rest on the Quanthome Data Engine, which connects your sources and ours and ties every record to its building or vehicle. How the engine works
FAQ
No. You connect an API or MCP key in a few lines of configuration and keep your existing systems and workflows. There is no data to move, and your stack stays as it is.
Claude, ChatGPT and the agent frameworks your team runs. The MCP server gives them the same records as the platform, so their answers rest on figures linked to their source, and it keeps working when you switch tools.
Every call runs through secure authentication, and access is set per user, so each user and each agent reaches only the data you allow.
Tell us which systems and AI tools your teams use. We plan the API and MCP connection with you in a working session.
Tell us which tools your teams useWe use essential cookies to operate this site and, with your consent, analytics cookies (Google Analytics) to measure traffic. You can change your choice at any time via the "Cookie settings" link in the footer.