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 9 APIs on the APIs.io network, including Comments API, Media API, O Embed API, and 6 more. Tagged areas include Real-Estate, Canada, Property Listings, MLS, and Valuation.

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

🌐 Visit website 📡 Source on GitHub

32.0/100 thin ▬ flat Agent 26/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Real-Estate Canada Property Listings MLS Valuation AVM PropTech Rentals Blog Content WordPress oEmbed Ontario British Columbia Toronto

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 32.0/100 · thin

Contract Quality 15.1 / 25

Developer Ergonomics 4.2 / 20

Access Clarity 4.2 / 20

Operational Transparency 0.3 / 13

Contract Governance 0.5 / 12

Discoverability 7.6 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 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 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. 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. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 9

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

HouseSigma Comments API

The Comments API from HouseSigma — 2 operation(s) for comments.

HouseSigma Media API

The Media API from HouseSigma — 2 operation(s) for media.

HouseSigma O Embed API

The oEmbed API from HouseSigma — 1 operation(s) for oembed.

HouseSigma Pages API

The Pages API from HouseSigma — 2 operation(s) for pages.

HouseSigma Posts API

The Posts API from HouseSigma — 2 operation(s) for posts.

HouseSigma Search API

The Search API from HouseSigma — 1 operation(s) for search.

HouseSigma Taxonomies API

The Taxonomies API from HouseSigma — 4 operation(s) for taxonomies.

HouseSigma Types API

The Types API from HouseSigma — 6 operation(s) for types.

HouseSigma Users API

The Users API from HouseSigma — 2 operation(s) for users.

Scroll for all 9

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

HouseSigma Blog Content API

OPEN COLLECTION

Examples 5

Example request and response payloads for these APIs.

Housesigma Blog Content Error 400 Rest_Invalid_Param

3 fields

EXAMPLE

Housesigma Blog Content Error 401 Rest_Forbidden

3 fields

EXAMPLE

Housesigma Blog Content Error 404 Rest_Post_Invalid_Id

3 fields

EXAMPLE

Housesigma Blog Content Getoembed 200

12 fields

EXAMPLE

Housesigma Blog Content Listtaxonomies 200

4 fields

EXAMPLE

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 5

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgenticAccess

LLMsTxt

WellKnown

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Components

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Examples

Examples

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

FAQ

FAQ

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 8

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

LinkedIn

About

Careers

Facebook

Instagram

Scroll for all 8

Other 3

Properties that don't map to a standard resource type

Overlay

Overlay

iOSApp

iOSApp

AndroidApp

AndroidApp

Source (apis.yml)

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.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
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
tags_raw:
- 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.23'
apis:
- aid: housesigma:housesigma-comments-api
  name: HouseSigma Comments API
  description: The Comments API from HouseSigma — 2 operation(s) for comments.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - Comments
  properties:
  - type: OpenAPI
    url: openapi/housesigma-comments-api-openapi.yml
  - 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
- aid: housesigma:housesigma-media-api
  name: HouseSigma Media API
  description: The Media API from HouseSigma — 2 operation(s) for media.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - Media
  properties:
  - type: OpenAPI
    url: openapi/housesigma-media-api-openapi.yml
  - 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
- aid: housesigma:housesigma-oembed-api
  name: HouseSigma O Embed API
  description: The oEmbed API from HouseSigma — 1 operation(s) for oembed.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - oEmbed
  properties:
  - type: OpenAPI
    url: openapi/housesigma-oembed-api-openapi.yml
  - 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
- aid: housesigma:housesigma-pages-api
  name: HouseSigma Pages API
  description: The Pages API from HouseSigma — 2 operation(s) for pages.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - Pages
  properties:
  - type: OpenAPI
    url: openapi/housesigma-pages-api-openapi.yml
  - 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
- aid: housesigma:housesigma-posts-api
  name: HouseSigma Posts API
  description: The Posts API from HouseSigma — 2 operation(s) for posts.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - Posts
  properties:
  - type: OpenAPI
    url: openapi/housesigma-posts-api-openapi.yml
  - 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
- aid: housesigma:housesigma-search-api
  name: HouseSigma Search API
  description: The Search API from HouseSigma — 1 operation(s) for search.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - Search
  properties:
  - type: OpenAPI
    url: openapi/housesigma-search-api-openapi.yml
  - 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
- aid: housesigma:housesigma-taxonomies-api
  name: HouseSigma Taxonomies API
  description: The Taxonomies API from HouseSigma — 4 operation(s) for taxonomies.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - taxonomies
  tags_raw:
  - Taxonomies
  properties:
  - type: OpenAPI
    url: openapi/housesigma-taxonomies-api-openapi.yml
  - 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
- aid: housesigma:housesigma-types-api
  name: HouseSigma Types API
  description: The Types API from HouseSigma — 6 operation(s) for types.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - Types
  properties:
  - type: OpenAPI
    url: openapi/housesigma-types-api-openapi.yml
  - 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
- aid: housesigma:housesigma-users-api
  name: HouseSigma Users API
  description: The Users API from HouseSigma — 2 operation(s) for users.
  humanURL: https://housesigma.com/blog-en/
  baseURL: https://housesigma.com/blog-en/wp-json
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/housesigma-users-api-openapi.yml
  - 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: X-MCPServerCandidate
  url: mcp/housesigma-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- 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

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/housesigma"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/housesigma/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/housesigma/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.