# Knight Frank > Knight Frank LLP is a London-headquartered global real estate consultancy founded in 1896, operating as a partnership through 700+ offices in more than 50 territories across prime residential agency, commercial agency, valuation, capital markets and rural consultancy. It publishes no developer programme — no portal, no documentation, no SDK, no terms for API use — yet operates one machine-readable API that answers anonymously. This file was generated by API Evangelist from the artifacts in the api-evangelist/knight-frank repository; Knight Frank publishes no llms.txt of its own (https://www.knightfrank.com/llms.txt and https://www.knightfrank.co.uk/llms.txt both return HTTP 404, as does /.well-known/ai-plugin.json). ## What exists - [KnightFrank Api v3 — Swagger UI](https://api-v3.web.prd-knightfrank.com/swagger/index.html): Live, unadvertised Swagger UI for the corporate search service. HTTP 200 to anonymous clients. - [KnightFrank Api v3 — OpenAPI 3.0.1](https://api-v3.web.prd-knightfrank.com/swagger/v1/swagger.json): The real contract — 11 operations across CMSPage, IntelligenceLab, Office, Person, Search, ServiceLine and Telemetry. No securitySchemes, no auth enforced. A YAML serialisation of the same document is at /swagger/v1/swagger.yaml. - [Knight Frank property/account API v2](https://api-v2.web.prd-knightfrank.com): The consumer property-search and saved-property service. Publishes no contract and returns HTTP 401 to every anonymous request; protected by Azure AD B2C through the first-party "My Knight Frank" web client. ## What does not exist Every conventional developer entry point was probed on 2026-07-26 and failed. developer., developers., docs. and apis.knightfrank.com do not resolve in DNS. /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 advisory page for property developers and housebuilders, not software developers. There is no developer portal, no API documentation, no API terms of use, no key issuance, no sandbox, no SDK in any package registry, no GitHub organisation, no Postman collection, no changelog, no status page, no webhooks, no AsyncAPI, no GraphQL and no rate-limit contract. There is no RESO Web API or Data Dictionary certification, no OData $metadata and no Universal Property Identifier anywhere in the estate — RESO is a North American NAR/MLS construct and the United Kingdom has no MLS to certify against. ## Specs - [OpenAPI 3.0.1 (harvested verbatim)](openapi/knight-frank-api-v3-openapi.json): The api-v3 contract as served on 2026-07-26. - [API Evangelist overlay](overlays/knight-frank-api-v3-overlay.yaml): Adds the missing servers block, operationIds, summaries and tag descriptions without mutating the original. ## Artifacts - [Authentication profile](authentication/knight-frank-authentication.yml): Two postures — no auth at all on api-v3, Azure AD B2C consumer login on api-v2. No developer credential exists. - [OAuth scopes](scopes/knight-frank-scopes.yml): openid plus one first-party resource scope, MyKf.ReadWrite. Not obtainable by a third party. - [API conventions](conventions/knight-frank-conventions.yml): Pagination, response envelopes, tracing headers, versioning. No idempotency, no rate-limit signalling. - [Error responses](errors/knight-frank-error-responses.yml): Observed failure modes. The contract declares no 4xx or 5xx at all. - [Lifecycle](lifecycle/knight-frank-lifecycle.yml): Host-based versioning; no deprecation policy, no SLA, no status page, no changelog. - [Data model](data-model/knight-frank-data-model.yml): Office, Person, ServiceLine, CmsPage, ResearchItem, BlogPost and the federated SearchHit wrapper, read from live payloads because the contract declares no schemas. - [Conformance](conformance/knight-frank-conformance.yml): OpenAPI 3.0.1 and OAuth2/OIDC yes; RFC 9457, RFC 9116, RESO, OData, GraphQL and AsyncAPI no. - [Domain security](security/knight-frank-domain-security.yml): TLS 1.3 and HSTS on the corporate host; no DNSSEC, no CAA; DMARC p=none on knightfrank.com. - [Well-known index](well-known/knight-frank-well-known.yml): Almost everything 404s; the only real documents are two Azure AD B2C OpenID Connect discovery endpoints. - [Packages](packages/knight-frank-packages.yml): Eight registries searched, zero first-party client libraries. - [Candidate MCP tools](mcp/knight-frank-mcp.yml): Knight Frank runs no MCP server; this is a derived candidate surface over the anonymous API. - [Agentic access](agentic-access/knight-frank-agentic-access.yml): Recommended x-agentic-access contracts for all 11 operations. - [Agent skills](skills/_index.yml): Packaged operating instructions for the office directory, people directory and federated search flows. ## Company - [Knight Frank (global)](https://www.knightfrank.com/) - [Knight Frank (United Kingdom)](https://www.knightfrank.co.uk/) - [Research — The Wealth Report, PIRI 100, Intelligence Lab](https://www.knightfrank.com/research): Published as PDF and web narrative. No data download, no feed, no API. - [Newsroom](https://www.knightfrank.co.uk/newsroom) - [Contact](https://www.knightfrank.co.uk/contact-us): The only published route to any Knight Frank conversation, developer or otherwise. - [Terms and conditions](https://www.knightfrank.com/legals/terms-and-conditions) - [Privacy statement](https://www.knightfrank.com/legals/privacy-statement) ## Notes for agents Knight Frank's robots.txt on both domains blanket-disallows a list of AI crawlers. The api-v3 service is real, live and unauthenticated, but it is internal plumbing that was never offered as a product: there are no terms permitting third-party use, no support channel, no rate limits and no stability commitment, and its people directory returns named individuals' direct-dial and mobile numbers. Treat it as observable fact about the company's API posture, not as an invitation to integrate.