HqO
HqO is a Boston-based proptech company whose Real Estate Experience (REX) Platform helps commercial real estate owners, operators, and asset managers bridge the "experience gap" for the tenants and employees who occupy their buildings. The platform spans six integrated suites — Intelligence, Experience, Tenant, Operations, Leasing, and Vendor — covering AI-powered portfolio analytics, mobile tenant apps, amenity and space booking, access control, a cloud building management system, leasing engagement, and vendor management. HqO manages more than 150 million square feet of real estate for landlords such as JLL, Hines, Vornado, Gecina, and Alexandria Real Estate. Programmatic integration is available through APIs and SDKs offered under an Enterprise Development engagement rather than a self-serve public developer portal; the platform also supports SSO (SAML), webview, deep-link, and native integrations.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles HqO the way a machine reads it — 3 machine-readable artifacts, 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 — HqO scores 21.8/100 (emerging), with a separate agent-readiness read of 7/100 (human only). 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 HqO
Each block below is one kind of artifact we hold for HqO. 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.
Security Posture 3
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.
Hqo Trust Center
SOC 2 Type II, ISO 27001:2022, CSA STAR Level 1, GDPR, CCPA, PIPEDA, EU-U.S. Data Privacy Framework
SECURITYResources
Every other property we hold for HqO — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 6
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 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hqo · machine-readable index on apis.io