Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Century 21 Canada

CENTURY 21 Canada Limited Partnership is the Canadian master franchisor of the CENTURY 21® real estate brand, headquartered at 1285 West Pender Street in Vancouver, British Columbia. The master licence for Canada was secured in Vancouver in 1976 — the first international franchise of the CENTURY 21 System — and the network today spans roughly 400 independently owned and operated offices from coast to coast. Century 21 Canada sits in the brokerage/franchisor layer of the Canadian real estate value chain: it does not originate listing data, it consumes it. Canadian residential listings are consolidated nationally by the Canadian Real Estate Association (CREA), which runs REALTOR.ca and the Data Distribution Facility (DDF®); franchisors and brokerages redistribute that member-owned MLS® content under CREA rules rather than publishing it themselves. Century 21 Canada's API posture is accordingly empty. As of a 2026-07-26 probe there is no developer portal, no API documentation, no published base URL, no SDK, no webhooks, no Postman collection and no machine-readable contract of any kind on century21.ca or c21.ca — both century21.ca and c21.ca resolve to the same WordPress consumer site whose terms of use name MoxiWorks LLC as the site operator, and whose property search is a hosted MoxiWorks Web Marketing System surface rather than a first-party API. Wildcard DNS on *.century21.ca and *.c21.ca returns HTTP 200 for every subdomain probed (developer., developers., api., docs.) by parking them all on eboat.moxiworks.com, so those 200s are a DNS artifact and not a developer portal. RESO is absent: no RESO Web API or Data Dictionary certification, no OData or $metadata endpoint, and no Universal Property Identifier reference appears anywhere in the public surface — consistent with Canada, where RESO certification is not the operative seam and CREA's DDF® is. The only genuinely public, anonymously callable machine-readable surface found is the incidental WordPress REST API route index at https://www.c21.ca/wp-json/, which is a CMS artifact, is undocumented by Century 21 Canada, and is deliberately not listed here as a product API. Agent- and franchisee-facing tools live behind the hub21.ca member login. This profile is therefore identity-only and honestly records a brokerage franchisor with no published developer surface.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Century 21 Canada the way a machine reads it — 1 machine-readable artifact, 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 — Century 21 Canada scores 14.3/100 (minimal), with a separate agent-readiness read of 0/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 14.3/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Securities & Market Data 4.6 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Century 21 Canada

Each block below is one kind of artifact we hold for Century 21 Canada. 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 1

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.

Century 21 Canada Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Century 21 Canada — 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

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/century-21-canada · machine-readable index on apis.io