HouseSigma

HouseSigma, Inc. Brokerage is a Toronto-based Canadian residential real estate portal and licensed brokerage that pairs map-based MLS listing search with sold-price history and machine-learning home valuations (SigmaEstimate) across Ontario, British Columbia, and Alberta. It sits in the challenger layer of the Canadian value chain, below CREA, which operates REALTOR.ca and the national Data Distribution Facility (DDF) that syndicates member boards' listings, and alongside Wahi, Zolo, and Properly, competing on visibility into data the boards control, a position it won in part through the Competition Bureau litigation that forced TRREB to release sold data in 2018. Its API posture is closed. There is no developer portal, no published API program, and no partner or data-licensing page; developer., developers., and docs.housesigma.com do not resolve in DNS, and /developers, /api, /api-docs, /openapi.json and /swagger.json all return the single-page-application shell rather than any contract. The listing, sold-history and valuation backend at housesigma.com/bkv2/api/ is private, keyless, undocumented, and explicitly disallowed to all crawlers in robots.txt. The one genuinely public, anonymously callable, machine-readable HTTP surface the company operates is the WordPress REST API behind housesigma.com/blog-en, which serves its Canadian housing-market analysis blog as JSON across 157 advertised routes; API Evangelist derived an OpenAPI for the 22 operations verified to answer anonymously. HouseSigma also publishes a real llms.txt and mobile deep-link association documents. RESO is absent: HouseSigma is not among the Canadian organizations RESO lists as members, and no Web API or Data Dictionary certification, OData $metadata document, or Universal Property Identifier usage was found. No open, unlicensed dataset is published. The underlying listing and sold data is board-licensed and reaches HouseSigma through its own brokerage membership, not through anything a third-party developer can sign up for.

HouseSigma publishes 1 API on the APIs.io network: Blog Content API. Tagged areas include Real Estate, Canada, Property Listings, MLS, and Valuation.

HouseSigma’s developer surface includes authentication, engineering blog, code examples, support, FAQ, and 24 more developer resources.

33.1/100 thin ▬ flat Agent 64/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
1 APIs
Real EstateCanadaProperty ListingsMLSValuationAVMPropTechRentalsBlogContentWordPressoEmbedOntarioBritish ColumbiaToronto

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 33.1/100 · thin
Contract Quality 14.2 / 25
Developer Ergonomics 4.8 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 64/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/housesigma: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

HouseSigma Blog Content API

The public, read-only WordPress REST API (wp/v2) behind housesigma.com/blog-en, which serves HouseSigma's Canadian housing-market analysis blog as JSON. This is the only anonymo...

Examples 5

Example request and response payloads for these APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Housesigma Authentication

http · 1 scheme

SECURITY

Housesigma Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Housesigma Agentic Access

22 operations

22 operations · 0 acting

AGENTIC

Resources

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

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 8

The organization behind the API

Scroll for all 8

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: housesigma
url: https://raw.githubusercontent.com/api-evangelist/housesigma/refs/heads/main/apis.yml
name: HouseSigma
kind: company
description: 'HouseSigma, Inc. Brokerage is a Toronto-based Canadian residential real estate portal and licensed brokerage
  that pairs map-based MLS listing search with sold-price history and machine-learning home valuations (SigmaEstimate) across
  Ontario, British Columbia, and Alberta. It sits in the challenger layer of the Canadian value chain, below CREA, which operates
  REALTOR.ca and the national Data Distribution Facility (DDF) that syndicates member boards'' listings, and alongside Wahi,
  Zolo, and Properly, competing on visibility into data the boards control, a position it won in part through the Competition
  Bureau litigation that forced TRREB to release sold data in 2018. Its API posture is closed. There is no developer portal,
  no published API program, and no partner or data-licensing page; developer., developers., and docs.housesigma.com do not
  resolve in DNS, and /developers, /api, /api-docs, /openapi.json and /swagger.json all return the single-page-application
  shell rather than any contract. The listing, sold-history and valuation backend at housesigma.com/bkv2/api/ is private,
  keyless, undocumented, and explicitly disallowed to all crawlers in robots.txt. The one genuinely public, anonymously callable,
  machine-readable HTTP surface the company operates is the WordPress REST API behind housesigma.com/blog-en, which serves
  its Canadian housing-market analysis blog as JSON across 157 advertised routes; API Evangelist derived an OpenAPI for the
  22 operations verified to answer anonymously. HouseSigma also publishes a real llms.txt and mobile deep-link association
  documents. RESO is absent: HouseSigma is not among the Canadian organizations RESO lists as members, and no Web API or Data
  Dictionary certification, OData $metadata document, or Universal Property Identifier usage was found. No open, unlicensed
  dataset is published. The underlying listing and sold data is board-licensed and reaches HouseSigma through its own brokerage
  membership, not through anything a third-party developer can sign up for.'
image: https://housesigma.com/apple-touch-icon.png?v=2
tags:
- Real Estate
- Canada
- Property Listings
- MLS
- Valuation
- AVM
- PropTech
- Rentals
- Blog
- Content
- WordPress
- oEmbed
- Ontario
- British Columbia
- Toronto
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.19'
apis:
- name: HouseSigma Blog Content API
  description: 'The public, read-only WordPress REST API (wp/v2) behind housesigma.com/blog-en, which serves HouseSigma''s
    Canadian housing-market analysis blog as JSON. This is the only anonymously callable, machine-readable HTTP surface HouseSigma
    operates: 157 routes across 8 namespaces are advertised by the live route-discovery document at https://housesigma.com/blog-en/wp-json/
    (HTTP 200), of which 22 GET operations - posts, pages, media, categories, tags, authors, comments, search, the type/taxonomy/status
    registry, and oEmbed - were verified to answer without credentials. Page-number pagination with X-WP-Total / X-WP-TotalPages
    / RFC 8288 Link headers; errors use the WordPress {code,message,data.status} envelope rather than RFC 9457. It is NOT
    an official HouseSigma developer product: the company documents, supports and issues keys for nothing, and its listing,
    sold-price and SigmaEstimate valuation data is served only by the private, robots-disallowed /bkv2/api/ backend, which
    is deliberately not listed here.'
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - Blog
  - Content
  - Real Estate
  - Canada
  - WordPress
  - oEmbed
  properties:
  - type: OpenAPI
    url: openapi/housesigma-blog-content-openapi.yml
  - type: Overlay
    url: overlays/housesigma-blog-content-overlay.yaml
  - type: Examples
    url: examples/
  - type: ErrorCatalog
    url: errors/housesigma-problem-types.yml
  - type: DataModel
    url: data-model/housesigma-data-model.yml
  - type: Conventions
    url: conventions/housesigma-conventions.yml
common:
- type: AgenticAccess
  url: agentic-access/housesigma-agentic-access.yml
- type: DomainSecurity
  url: security/housesigma-domain-security.yml
- type: Authentication
  url: authentication/housesigma-authentication.yml
- type: Website
  url: https://housesigma.com/
- type: Blog
  url: https://housesigma.com/blog-en/
- type: BlogRSS
  url: https://housesigma.com/blog-en/feed/
- type: GitHubOrganization
  url: https://github.com/housesigma
- type: LinkedIn
  url: https://www.linkedin.com/company/housesigma
- type: LLMsTxt
  url: llms/housesigma-llms.txt
- type: WellKnown
  url: well-known/housesigma-well-known.yml
- type: Conventions
  url: conventions/housesigma-conventions.yml
- type: ErrorCatalog
  url: errors/housesigma-problem-types.yml
- type: Lifecycle
  url: lifecycle/housesigma-lifecycle.yml
- type: Conformance
  url: conformance/housesigma-conformance.yml
- type: DataModel
  url: data-model/housesigma-data-model.yml
- type: Components
  url: components/housesigma-components.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Examples
  url: examples/
- type: Overlay
  url: overlays/housesigma-blog-content-overlay.yaml
- type: TermsOfService
  url: https://housesigma.com/blog-en/2018/04/25/terms-of-use/
- type: PrivacyPolicy
  url: https://housesigma.com/blog-en/2018/04/25/privacy-policy/
- type: Support
  url: https://housesigma.com/blog-en/contact-us/
- type: FAQ
  url: https://housesigma.com/blog-en/faq/
- type: About
  url: https://housesigma.com/blog-en/about-us/
- type: Careers
  url: https://team.housesigma.com/
- type: iOSApp
  url: https://itunes.apple.com/ca/app/toronto-real-estate-housesigma/id1255490256?mt=8
- type: AndroidApp
  url: https://play.google.com/store/apps/details?id=com.housesigma.android&hl=en_CA
- type: Facebook
  url: https://www.facebook.com/housesigma/
- type: Instagram
  url: https://www.instagram.com/housesigma/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com