generated: '2026-07-26' method: searched source: >- https://www.teranet.ca/registry-solutions/province-of-ontario/teranet-connect/ plus live probes of every Teranet host (see well-known/teranet-well-known.yml) and the RESO directory work recorded in review.yml summary: >- Teranet conforms to almost none of the cross-cutting API standards the catalog tracks, and this is a posture rather than an oversight: Teranet Connect predates the modern spec ecosystem and is distributed under licence to a small set of legal-software vendors who receive their interface documentation privately. The one standard genuinely evidenced is XML over Web services, which Teranet states in its own words. Everything else is recorded as not-conforming with the evidence of absence, not asserted as absent by assumption. standards: - id: xml-web-services conforms: true evidence: >- Teranet: "by utilizing XML and Web services interfaces as well as standardized rules-based routing of information" (Teranet Connect product page and product sheet). - id: openapi conforms: false evidence: >- No OpenAPI or Swagger document exists on any Teranet host. /openapi.json, /openapi.yaml, /swagger.json, /api-docs and /docs were probed on www.teranet.ca, teranet.ca, www.teraview.ca, www.onland.ca, www.purview.ca, www.teranetmanitoba.ca and the NXDOMAIN candidates api./developer./docs./connect.teranet.ca. Every 200 was a WordPress soft-404 HTML page. - id: wsdl conforms: false evidence: >- Teranet describes Web services interfaces but publishes no WSDL. No service description of any kind is retrievable anonymously. - id: asyncapi conforms: false evidence: No event, streaming or webhook surface is documented on any Teranet property. - id: graphql conforms: false evidence: No /graphql endpoint found on any Teranet host. - id: mcp conforms: false evidence: No Model Context Protocol server, no llms.txt, no agent-facing surface. - id: oauth2 conforms: false evidence: >- No authorization server. /.well-known/oauth-authorization-server returns a soft-404 HTML page on every host. Authentication is a proprietary account plus RSA hardware token; see authentication/teranet-authentication.yml. - id: openid-connect conforms: false evidence: /.well-known/openid-configuration returns a soft-404 HTML page on every probed host. - id: rfc9457-problem-details conforms: false evidence: No error reference, error registry or problem-details schema is published. - id: rfc9116-security-txt conforms: false evidence: /.well-known/security.txt returns 404 or a soft-404 on every Teranet host. - id: rfc9727-api-catalog conforms: false evidence: /.well-known/api-catalog returns a soft-404 HTML page. - id: rfc8594-sunset-header conforms: false evidence: No deprecation or sunset policy is published; see lifecycle/teranet-lifecycle.yml. - id: reso-web-api conforms: false evidence: >- No RESO Web API certification, no RESO Data Dictionary certification, no OData $metadata document and no Universal Property Identifier reference appears on teranet.ca, teraview.ca, onland.ca, geowarehouse.ca, purview.ca, teranetmanitoba.ca or thenewrealm.ca. Teranet is a land registry operator, not an MLS; RESO does not govern Canadian land registration. Full directory evidence is recorded in review.yml under sectorBlock.resoPosture. - id: odata conforms: false evidence: No OData service root or $metadata document on any Teranet host. - id: json-api conforms: false evidence: The interface is XML, not JSON. compliance_programs: published: false certifications: [] evidence: >- No trust centre, no security page, no SOC 2, ISO 27001, PCI DSS or FedRAMP claim was found on any Teranet property, and probe-security-programs.py returned no trust-centre and no vulnerability-disclosure hit. Teranet operates under statutory and contractual obligations to the Province of Ontario and to Manitoba rather than under a publicly marketed compliance programme, so no Compliance pointer is emitted.