Knight Frank
Knight Frank LLP is a London-headquartered global real estate consultancy founded in 1896, structured as a partnership rather than a listed company, operating through a network of over 700 offices in more than 50 territories and best known for prime and super-prime residential agency, commercial agency and occupier services, valuation and advisory, capital markets, rural and agricultural consultancy, and the Knight Frank Research programme that publishes The Wealth Report and the Prime International Residential Index. It sits on the advisory and agency side of the property value chain rather than the data-platform side. Its home market is the United Kingdom, where there is no MLS and no cooperative listing standard — residential stock reaches consumers through the Rightmove and Zoopla duopoly by way of agency CRM software (Reapit, Alto, Street, Apex27) rather than a shared cooperative pool, so Knight Frank is a supplier into that pipe and not an operator of it. Its API posture is honest but unflattering: Knight Frank publishes no developer portal, no API programme, no developer terms, no SDK and no Postman collection, and every conventional developer entry point fails — developer., developers., docs. and apis.knightfrank.com do not resolve in DNS, and /developers, /api, /docs, /openapi.json, /swagger.json and /api-docs all return 404 on knightfrank.com and knightfrank.co.uk. On the UK site /developers is a homonym trap: it redirects to a commercial services page for property developers and housebuilders, not software developers. What does exist, entirely unadvertised, is a real machine-readable contract. The corporate search service at api-v3.web.prd-knightfrank.com serves a live Swagger UI and an OpenAPI 3.0.1 document (11 GET/POST operations across CMSPage, IntelligenceLab, Office, Person, Search, ServiceLine and Telemetry) to anonymous clients, and those endpoints answer with real office and people-directory data without any credential. The property search and saved-property service at api-v2.web.prd-knightfrank.com is the opposite: it returns 401 and is protected by Azure AD B2C (tenant KnightFrankB2Cprod, custom policy B2C_1A_MYKFSIGNIN, scope MyKf.ReadWrite) through a first-party MSAL client for the consumer My Knight Frank account, which is an end-user login and not a developer credential. There is no RESO Web API or Data Dictionary certification, no OData $metadata document and no Universal Property Identifier anywhere in the Knight Frank estate — RESO is a North American NAR/MLS construct and the United Kingdom has no MLS to certify against. Knight Frank publishes no open data either; its research ships as PDF and web narrative, and the genuinely open UK property layer belongs to the public sector — HM Land Registry Price Paid Data and Ordnance Survey open products — not to the brokerage.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Knight Frank the way a machine reads it — 8 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Knight Frank scores 36.4/100 (thin), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Knight Frank
Each block below is one kind of artifact we hold for Knight Frank. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
KnightFrank Api v3
The corporate search service behind knightfrank.com and knightfrank.co.uk, titled "KnightFrank Api v3" by its own OpenAPI document. It exposes 11 operations across seven tags — ...
Arazzo Workflows 2
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOKnight Frank office lookup
Search the Knight Frank office directory, then fetch the full record for the best-matching office.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
knight-frank-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Knight Frank — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/knight-frank · machine-readable index on apis.io