Landcor Data

Landcor Data Corporation is a New Westminster, British Columbia property data and automated valuation company, founded in 2000, that sells residential valuations, assessment detail and land title documents across the roughly 1.9 million residential properties in BC. It sits in the valuation and public-record layer of the Canadian value chain rather than the listings layer: its inputs are BC Assessment detail, Land Title and Survey Authority (LTSA) title and document search, BC Registry Services, municipal tax certificates and materials licensed from the Integrated Cadastral Information Society (ICIS), and its outputs are the Valuator AVM report, the Adjusted Value Profiler, the Property Profiler, Title Search Plus and historic valuation reports sold to lenders, appraisers, notaries, insurers and brokerages. Its API posture is the unusual case in this study: a real, live, anonymously readable machine-readable contract exists with no developer programme around it. The host api.landcor.com runs a FastAPI service on Azure App Service in Canada Central that serves a valid OpenAPI 3.1.0 document titled "Landcor Property API" version 0.1.0 at /openapi.json, with Swagger UI at /docs and ReDoc at /redoc, all returning HTTP 200 without credentials. Twelve operations cover property search, property detail, PDF report retrieval, valuation range, valuation history, loan-to-value checks, neighbourhood sales series, comparables, address autocomplete and an AVM narrative summary. Every operation except /health requires an HTTP Bearer token and returns 401 "Missing token" without one, and no route to obtain that token is published anywhere: landcor.com carries no developer, API, partner or data-licensing page, does not link api.landcor.com at all, and the store.landcor.com self-serve account is for buying individual reports through the web store, not for API credentials. RESO is absent, which is the expected Canadian answer. Landcor is not among the nineteen Canadian organizations RESO lists as members, holds no Web API or Data Dictionary certification, exposes no OData $metadata document, and uses its own PID identifier rather than the RESO Universal Property Identifier. No open, unlicensed dataset is published: the underlying assessment, title and cadastral data is licensed to Landcor from provincial bodies and resold, so the public record itself is a commercial product here.

Landcor Data publishes 5 API contracts indexed on the APIs.io network, including AVM Summary API, Comparables API, Health API, and 2 more. Tagged areas include Real Estate, Canada, Valuation, AVM, and Property Records.

The Landcor Data catalog on APIs.io includes 1 Spectral governance ruleset.

Landcor Data’s developer surface includes authentication, documentation, API reference, pricing, signup flow, support, engineering blog, and 26 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

40.2/100 developing ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent Heartbeat 33/100 slowing saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 3 Agent Skills

Real Estate Canada Valuation AVM Property Records Title Land Registry Mortgage PropTech Property Data

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Real Estate Valuation & Appraisal Management

BC-4970

AVM SummaryComparablesValuation

GET /comparables/{pid} GET /valuationRange/{pid} GET /valuationRange/{pid}/history POST /valuation/ltv-check

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 40.2/100 · developing

Contract Quality 9.4 / 19

Developer Ergonomics 5.6 / 15

Access Clarity 6.7 / 15

Operational Transparency 1.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.0 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

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

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/landcor/"><img src="https://apis.io/badge/landcor/card.svg" alt="Landcor Data 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
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
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)

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 37.5 — up to +12.5 composite points
Contract Quality scores 50.0 — up to +12.5 composite points
Operational Transparency scores 13.2 — up to +11.3 composite points

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/landcor/apis.yml: open an issue on github.com/api-evangelist/landcor 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Consumer Lending Licensing (UK, US, Canada credit licence registers)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

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

Landcor Data AVM Summary API

The AVM Summary API from Landcor Data — 1 operation(s) for avm summary.

Landcor Data Comparables API

The Comparables API from Landcor Data — 1 operation(s) for comparables.

Landcor Data Health API

The Health API from Landcor Data — 1 operation(s) for health.

Landcor Data Property API

The Property API from Landcor Data — 4 operation(s) for property.

Landcor Data Valuation API

The Valuation API from Landcor Data — 5 operation(s) for valuation.

Open Collections 1

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

Landcor Property API

OPEN COLLECTION

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

Landcor — address to valuation

Resolve a BC street address to a Landcor PID, then pull property detail, the AVM valuation range and the valuation history.

ARAZZO

Landcor — loan-to-value check and valuation report

Run a proposed mortgage amount against Landcor's AVM value for a BC property and retrieve the password-protected PDF valuation report for the file.

ARAZZO

Agent Skills 3

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

Pull Landcor comparables and neighbourhood market context

AGENT SKILL

Run a Landcor loan-to-value check

AGENT SKILL

Value a BC property with Landcor

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Landcor Data API Rules

50 rules · 42 errors 5 warnings 3 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.

Landcor Property Api Overlay

11 actions · servers · landcor-property-api-openapi.json

DERIVED

Security Posture 2

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

Landcor Authentication

http · 1 scheme

SECURITY

Landcor Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

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

Landcor Agentic Access

12 operations · 2 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

AgentSkill

LLMsTxt

WellKnownProbe

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Arazzo

Arazzo

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

SecurityPolicy

SecurityPolicy

Operate 2

Status, limits, changes, and where to get help

Support

Support

Contact

Contact

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 4

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

LinkedIn

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Products

Products

Source (apis.yml)

aid: landcor
url: https://raw.githubusercontent.com/api-evangelist/landcor/refs/heads/main/apis.yml
name: Landcor Data
kind: company
description: 'Landcor Data Corporation is a New Westminster, British Columbia property data and automated valuation company,
  founded in 2000, that sells residential valuations, assessment detail and land title documents across the roughly 1.9 million
  residential properties in BC. It sits in the valuation and public-record layer of the Canadian value chain rather than the
  listings layer: its inputs are BC Assessment detail, Land Title and Survey Authority (LTSA) title and document search, BC
  Registry Services, municipal tax certificates and materials licensed from the Integrated Cadastral Information Society (ICIS),
  and its outputs are the Valuator AVM report, the Adjusted Value Profiler, the Property Profiler, Title Search Plus and historic
  valuation reports sold to lenders, appraisers, notaries, insurers and brokerages. Its API posture is the unusual case in
  this study: a real, live, anonymously readable machine-readable contract exists with no developer programme around it. The
  host api.landcor.com runs a FastAPI service on Azure App Service in Canada Central that serves a valid OpenAPI 3.1.0 document
  titled "Landcor Property API" version 0.1.0 at /openapi.json, with Swagger UI at /docs and ReDoc at /redoc, all returning
  HTTP 200 without credentials. Twelve operations cover property search, property detail, PDF report retrieval, valuation
  range, valuation history, loan-to-value checks, neighbourhood sales series, comparables, address autocomplete and an AVM
  narrative summary. Every operation except /health requires an HTTP Bearer token and returns 401 "Missing token" without
  one, and no route to obtain that token is published anywhere: landcor.com carries no developer, API, partner or data-licensing
  page, does not link api.landcor.com at all, and the store.landcor.com self-serve account is for buying individual reports
  through the web store, not for API credentials. RESO is absent, which is the expected Canadian answer. Landcor is not among
  the nineteen Canadian organizations RESO lists as members, holds no Web API or Data Dictionary certification, exposes no
  OData $metadata document, and uses its own PID identifier rather than the RESO Universal Property Identifier. No open, unlicensed
  dataset is published: the underlying assessment, title and cadastral data is licensed to Landcor from provincial bodies
  and resold, so the public record itself is a commercial product here.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - 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-11-06'
  method: derived
image: https://www.landcor.com/wp-content/uploads/2026/01/favicon-152.png
tags:
- Real Estate
- Canada
- Valuation
- AVM
- Property Records
- Title
- Land Registry
- Mortgage
- PropTech
- Property Data
tags_raw:
- Real Estate
- Canada
- Valuation
- AVM
- Property Records
- Title
- Land Registry
- Mortgage
- PropTech
- Property Data
- Real-Estate
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.23'
apis:
- aid: landcor:landcor-avm-summary-api
  name: Landcor Data AVM Summary API
  description: The AVM Summary API from Landcor Data — 1 operation(s) for avm summary.
  humanURL: https://api.landcor.com/docs
  baseURL: https://api.landcor.com
  tags:
  - AVM Summary
  properties:
  - type: OpenAPI
    url: openapi/landcor-avm-summary-api-openapi.yml
  - type: Documentation
    url: https://api.landcor.com/docs
  - type: APIReference
    url: https://api.landcor.com/redoc
  - type: Authentication
    url: https://api.landcor.com/docs
- aid: landcor:landcor-comparables-api
  name: Landcor Data Comparables API
  description: The Comparables API from Landcor Data — 1 operation(s) for comparables.
  humanURL: https://api.landcor.com/docs
  baseURL: https://api.landcor.com
  tags:
  - Comparables
  properties:
  - type: OpenAPI
    url: openapi/landcor-comparables-api-openapi.yml
  - type: Documentation
    url: https://api.landcor.com/docs
  - type: APIReference
    url: https://api.landcor.com/redoc
  - type: Authentication
    url: https://api.landcor.com/docs
- aid: landcor:landcor-health-api
  name: Landcor Data Health API
  description: The Health API from Landcor Data — 1 operation(s) for health.
  humanURL: https://api.landcor.com/docs
  baseURL: https://api.landcor.com
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/landcor-health-api-openapi.yml
  - type: Documentation
    url: https://api.landcor.com/docs
  - type: APIReference
    url: https://api.landcor.com/redoc
  - type: Authentication
    url: https://api.landcor.com/docs
- aid: landcor:landcor-property-api
  name: Landcor Data Property API
  description: The Property API from Landcor Data — 4 operation(s) for property.
  humanURL: https://api.landcor.com/docs
  baseURL: https://api.landcor.com
  tags:
  - Property
  properties:
  - type: OpenAPI
    url: openapi/landcor-property-api-openapi.yml
  - type: Documentation
    url: https://api.landcor.com/docs
  - type: APIReference
    url: https://api.landcor.com/redoc
  - type: Authentication
    url: https://api.landcor.com/docs
- aid: landcor:landcor-valuation-api
  name: Landcor Data Valuation API
  description: The Valuation API from Landcor Data — 5 operation(s) for valuation.
  humanURL: https://api.landcor.com/docs
  baseURL: https://api.landcor.com
  tags:
  - Valuation
  properties:
  - type: OpenAPI
    url: openapi/landcor-valuation-api-openapi.yml
  - type: Documentation
    url: https://api.landcor.com/docs
  - type: APIReference
    url: https://api.landcor.com/redoc
  - type: Authentication
    url: https://api.landcor.com/docs
common:
- type: CapabilityMap
  url: capabilities/landcor-capability-edges.yml
  name: Landcor Data Business Capability Map
- type: AgenticAccess
  url: agentic-access/landcor-agentic-access.yml
- type: DomainSecurity
  url: security/landcor-domain-security.yml
- type: Authentication
  url: authentication/landcor-authentication.yml
- type: Documentation
  url: https://api.landcor.com/docs
- type: APIReference
  url: https://api.landcor.com/redoc
- type: Conventions
  url: conventions/landcor-conventions.yml
- type: ErrorCatalog
  url: errors/landcor-problem-types.yml
- type: Lifecycle
  url: lifecycle/landcor-lifecycle.yml
- type: Conformance
  url: conformance/landcor-conformance.yml
- type: DataModel
  url: data-model/landcor-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/landcor-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: ToolCrosswalk
  url: mcp/landcor-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Landcor — address to valuation
  url: arazzo/landcor-address-to-valuation.yml
- type: Arazzo
  name: Landcor — loan-to-value check and valuation report
  url: arazzo/landcor-ltv-check-and-report.yml
- type: LLMsTxt
  url: llms/landcor-llms.txt
- type: Overlay
  url: overlays/landcor-property-api-overlay.yaml
- type: WellKnownProbe
  url: well-known/landcor-well-known.yml
- type: Website
  url: https://www.landcor.com/
- type: Products
  url: https://www.landcor.com/online-property-tools/
- type: Pricing
  url: https://www.landcor.com/pricing/
- type: SignUp
  url: https://store.landcor.com/user/user_add.aspx
- type: Login
  url: https://store.landcor.com/user/login.aspx
- type: Support
  url: https://www.landcor.com/support/
- type: Contact
  url: https://www.landcor.com/contact/
- type: Blog
  url: https://www.landcor.com/about-us/landcor-news/
- type: BlogRSS
  url: https://www.landcor.com/feed/
- type: PrivacyPolicy
  url: https://www.landcor.com/privacy-policy/
- type: TermsOfService
  url: https://www.landcor.com/acceptable-use/
- type: SecurityPolicy
  url: https://www.landcor.com/security-policy/
- type: GitHubOrganization
  url: https://github.com/Landcor
- type: LinkedIn
  url: https://ca.linkedin.com/company/landcor-data-corporation
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Landcor Data API — frequently asked questions

Does Landcor Data have an API?

Yes. APIs.io lists 5 APIs from Landcor Data, including Landcor Data AVM Summary API, Landcor Data Comparables API and Landcor Data Health API, and 2 more.

Is there an OpenAPI specification for the Landcor Data API?

Yes. APIs.io indexes 5 OpenAPI specifications for Landcor Data, each linked for download from this page.

How do I authenticate with the Landcor Data API?

Landcor Data uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Landcor Authentication.

Is the Landcor Data API ready for AI agents?

Landcor Data has a Kin Score of 40.2 out of 100 (developing) and an Agent Readiness score of 27.0 (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/landcor"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/landcor/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.

GitHub Google LinkedIn

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