Wahi website screenshot

Wahi

Wahi is a Toronto-headquartered Canadian digital real estate platform and licensed brokerage — Wahi Inc., trading as Wahi Realty Inc., Brokerage — founded in 2021 by Benjy Katchen. It runs a consumer home search, an instant home valuation estimate, market data products (Market Pulse, House Price Index), a Wahi Select REALTOR matching service and a cashback program across Ontario, British Columbia, Alberta, Nova Scotia, Saskatchewan and New Brunswick. Wahi sits in the challenger layer of the Canadian listings value chain and does not own the data it surfaces: Canadian residential listings run through CREA, the single national cooperative that operates REALTOR.ca and the Data Distribution Facility (DDF), and Wahi reaches that data as a member brokerage and through a commercial MLS connectivity vendor (Repliers) rather than by operating a feed of its own. Wahi runs no developer programme: there is no developer portal, no api./developer./developers./docs. subdomain (all fail DNS resolution), no API key or OAuth credential path, and no RESO Web API certification, RESO Data Dictionary certification, OData service or $metadata document anywhere on its hosts — Wahi appears in neither the RESO certificates directory nor RESO's Canadian membership roster. The Terms of Use expressly forbid automated access, crawling and scraping, and forbid collecting, copying, storing or redistributing MLS data. It does, however, publish two agent-facing artifacts that a portal-shaped search misses: a 421KB llms.txt at https://wahi.com/llms.txt (Last-Updated 2025-07-20) and an OpenAI-style AI plugin manifest at /.well-known/ai-plugin.json that points to a genuine OpenAPI 3.0.1 "Listing Search API" at https://wahi.com/gpt/openapi.yaml — one anonymous searchListings operation with 30 typed filters over Canadian listings. The spec is still served; the server it names, api.prod.wahi.com/gpt, returns 404, so the contract is published but unserved. A live Apollo GraphQL endpoint exists at api.prod.wahi.com/graphql with introspection disabled and robots.txt disallowing it, and the stock WordPress REST API of the marketing CMS remains anonymously callable. Wahi is overwhelmingly an API consumer rather than a producer, but not a zero.

Wahi publishes 2 API contracts indexed on the APIs.io network, including Search API, and 1 more. Tagged areas include Real Estate, Canada, Property Listings, MLS, and Valuation.

The Wahi catalog on APIs.io includes 1 Spectral governance ruleset.

Wahi’s developer surface includes authentication, support, engineering blog, and 19 more developer resources.

35.8/100 thin ▬ flat Agent 28/100 agent aware Front door AI 1/6 silent Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessOpen
1 published contract 1 MCP Servers 1 Agent Skills
Real EstateCanadaProperty ListingsMLSValuationAVMPropTechRentalsBrokerage

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Securities & Market Data regime (on an ambiguous tag, where no other regime matched), so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
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.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Wahi It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/wahi/"><img src="https://apis.io/badge/wahi/card.svg" alt="Wahi on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
4 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
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 the provider profile at artifacts.apis.io/wahi/apis.yml: open an issue on github.com/api-evangelist/wahi to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (published)

APIs 2

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

Wahi Website (WordPress REST)

The public WordPress REST API (wp-json) of the Wahi website at wahi.com: the route index of the site's content management system, catalogued as one site surface rather than as s...

Wahi Search API

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

Open Collections 1

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

API Collection

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Wahi MCP Server

MCP SERVER

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Wahi API Rules

41 rules · 39 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Wahi Listing Search Overlay

5 actions · update · wahi-listing-search-openapi.yaml

DERIVED

Security Posture 2

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

Wahi Authentication

none/http-basic/cookie · 3 schemes

SECURITY

Wahi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

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

Wahi Agentic Access

1 operation

1 operations · 0 acting

AGENTIC

Resources

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

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 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: wahi
url: https://raw.githubusercontent.com/api-evangelist/wahi/refs/heads/main/apis.yml
name: Wahi
kind: company
description: 'Wahi is a Toronto-headquartered Canadian digital real estate platform and licensed brokerage — Wahi Inc., trading
  as Wahi Realty Inc., Brokerage — founded in 2021 by Benjy Katchen. It runs a consumer home search, an instant home valuation
  estimate, market data products (Market Pulse, House Price Index), a Wahi Select REALTOR matching service and a cashback
  program across Ontario, British Columbia, Alberta, Nova Scotia, Saskatchewan and New Brunswick. Wahi sits in the challenger
  layer of the Canadian listings value chain and does not own the data it surfaces: Canadian residential listings run through
  CREA, the single national cooperative that operates REALTOR.ca and the Data Distribution Facility (DDF), and Wahi reaches
  that data as a member brokerage and through a commercial MLS connectivity vendor (Repliers) rather than by operating a feed
  of its own. Wahi runs no developer programme: there is no developer portal, no api./developer./developers./docs. subdomain
  (all fail DNS resolution), no API key or OAuth credential path, and no RESO Web API certification, RESO Data Dictionary
  certification, OData service or $metadata document anywhere on its hosts — Wahi appears in neither the RESO certificates
  directory nor RESO''s Canadian membership roster. The Terms of Use expressly forbid automated access, crawling and scraping,
  and forbid collecting, copying, storing or redistributing MLS data. It does, however, publish two agent-facing artifacts
  that a portal-shaped search misses: a 421KB llms.txt at https://wahi.com/llms.txt (Last-Updated 2025-07-20) and an OpenAI-style
  AI plugin manifest at /.well-known/ai-plugin.json that points to a genuine OpenAPI 3.0.1 "Listing Search API" at https://wahi.com/gpt/openapi.yaml
  — one anonymous searchListings operation with 30 typed filters over Canadian listings. The spec is still served; the server
  it names, api.prod.wahi.com/gpt, returns 404, so the contract is published but unserved. A live Apollo GraphQL endpoint
  exists at api.prod.wahi.com/graphql with introspection disabled and robots.txt disallowing it, and the stock WordPress REST
  API of the marketing CMS remains anonymously callable. Wahi is overwhelmingly an API consumer rather than a producer, but
  not a zero.'
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: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://wahi.com/wp-content/uploads/2022/10/wahi-logo.svg
tags:
- Real Estate
- Canada
- Property Listings
- MLS
- Valuation
- AVM
- PropTech
- Rentals
- Brokerage
tags_raw:
- Real Estate
- Canada
- Property Listings
- MLS
- Valuation
- AVM
- PropTech
- Rentals
- Brokerage
- Real-Estate
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.23'
apis:
- aid: wahi:wahi-com-website-wordpress-rest
  name: Wahi Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the Wahi website at wahi.com: the route index of the site''s content
    management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://wahi.com/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  properties:
  - type: Documentation
    url: https://wahi.com/wp-json
  x-platform: wordpress
  x-platform-surface: rest
- aid: wahi:wahi-search-api
  name: Wahi Search API
  description: The Search API from Wahi — 1 operation(s) for search.
  humanURL: https://developer.wordpress.org/rest-api/
  baseURL: https://api.prod.wahi.com/gpt
  tags:
  - Search
  properties:
  - type: OpenAPI
    url: openapi/wahi-search-api-openapi.yml
  - type: DataModel
    url: data-model/wahi-data-model.yml
common:
- type: Overlay
  url: overlays/wahi-listing-search-overlay.yaml
- type: AgentSkill
  url: skills/wahi-search-listings.md
- type: MCPServer
  url: mcp/wahi-mcp.yml
- type: DomainSecurity
  url: security/wahi-domain-security.yml
- type: AgenticAccess
  url: agentic-access/wahi-agentic-access.yml
- type: LLMsTxt
  url: llms/wahi-llms.txt
- type: WellKnown
  url: well-known/wahi-well-known.yml
- type: Authentication
  url: authentication/wahi-authentication.yml
- type: Conventions
  url: conventions/wahi-conventions.yml
- type: ErrorCatalog
  url: errors/wahi-problem-types.yml
- type: Lifecycle
  url: lifecycle/wahi-lifecycle.yml
- type: Conformance
  url: conformance/wahi-conformance.yml
- type: Packages
  url: packages/wahi-packages.yml
- type: AgentSkill
  url: skills/_index.yml
- type: GitHubOrganization
  url: https://github.com/wahi-com
- type: Support
  url: https://wahi.com/ca/en/contact-us/
- type: Website
  url: https://wahi.com/ca/en
- type: About
  url: https://wahi.com/ca/en/about-us/
- type: TermsOfService
  url: https://wahi.com/ca/en/terms-of-use/
- type: PrivacyPolicy
  url: https://wahi.com/ca/en/privacy-policy/
- type: Blog
  url: https://wahi.com/ca/en/learning-centre/
- type: BlogRSS
  url: https://wahi.com/ca/en/feed/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Wahi API — frequently asked questions

Does Wahi have an API?

Yes. APIs.io lists 2 APIs from Wahi, including Wahi Website (WordPress REST) and Wahi Search API.

Is there an OpenAPI specification for the Wahi API?

Yes. APIs.io indexes 1 OpenAPI specification for Wahi, each linked for download from this page.

How do I authenticate with the Wahi API?

Wahi uses bearer-token authentication (none/http-basic/cookie · 3 schemes). The details are profiled on APIs.io as Wahi Authentication.

Does Wahi have an MCP server?

Yes. APIs.io lists 1 MCP server for Wahi.

Is the Wahi API ready for AI agents?

Wahi has a Kin Score of 35.8 out of 100 (thin) and an Agent Readiness score of 27.7 (agent-aware), scored by API Evangelist on 2026-11-06.

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/wahi"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/wahi/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/wahi/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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