generated: '2026-07-26'
method: derived
source: >-
  openapi/re-max-canada-blog-wp-json-index.json, live probes 2026-07-26, and the
  RESO certification directory (https://www.reso.org/certificates/, HTTP 200,
  416,233 bytes)
scope: >-
  What RE/MAX Canada's reachable surface does and does not conform to. The
  sector standards are the point of this file: a brokerage-tier organisation in
  Canada holds none of them, because Canadian listing conformance sits with CREA
  and the member boards, not with the brand.
standards:
- id: reso-web-api
  conforms: false
  evidence: >-
    No OData service root, service document or $metadata anywhere.
    https://api.remax.ca/odata, /Reso and /RESO/odata/$metadata all return HTTP
    301 to www.remax.ca; https://www.remax.ca/$metadata returns HTTP 404.
- id: reso-data-dictionary
  conforms: false
  evidence: >-
    No RESO Data Dictionary field appears in any harvested document. A
    case-insensitive regex for "re ?/? ?max" over the full RESO certification
    directory returns zero matches — RE/MAX Canada is absent from it entirely,
    while 30 Canadian board and pooled-platform entries are present.
- id: reso-upi
  conforms: false
  evidence: >-
    Zero occurrences of "UPI" or "Universal Property Identifier" in the
    remax.ca homepage (339,385 bytes) or the harvested WordPress REST index.
- id: odata-v4
  conforms: false
  evidence: No OData surface; every candidate path 301s or 404s.
- id: openapi
  conforms: false
  evidence: >-
    No OpenAPI or Swagger document exists. /openapi.json, /swagger.json,
    /api-docs, /docs and /swagger/v1/swagger.json were probed on both
    www.remax.ca and api.remax.ca — all 404 or 301. Nothing was generated to
    stand in for one.
- id: graphql
  conforms: false
  evidence: https://api.remax.ca/graphql returns HTTP 301 to www.remax.ca.
- id: asyncapi
  conforms: false
  evidence: No event, streaming or webhook surface of any kind is documented.
- id: oauth2
  conforms: false
  evidence: >-
    No OAuth 2.0 anywhere. /.well-known/oauth-authorization-server returns 404
    on every host.
- id: oidc
  conforms: false
  evidence: /.well-known/openid-configuration returns 404 on every host.
- id: rfc7617-http-basic
  conforms: true
  evidence: >-
    WordPress Application Passwords are HTTP Basic over TLS, declared in the
    harvested discovery index with authorization endpoint
    https://blog.remax.ca/wp-admin/authorize-application.php.
- id: rfc9457-problem-details
  conforms: false
  evidence: >-
    Errors are the WordPress {code,message,data.status} envelope served as
    application/json, not application/problem+json. See
    errors/re-max-canada-problem-types.yml.
- id: rfc8288-web-linking
  conforms: true
  evidence: >-
    Link headers with rel="next" observed on
    /wp-json/wp/v2/posts?per_page=1, and rel="https://api.w.org/" on the site
    root. Resources carry a _links hypermedia block.
- id: rfc9116-security-txt
  conforms: false
  evidence: /.well-known/security.txt returns 404 or 301 on every host.
- id: rfc9727-api-catalog
  conforms: false
  evidence: /.well-known/api-catalog returns 404 or 301 on every host.
- id: rfc8594-sunset-header
  conforms: false
  evidence: No Sunset or Deprecation header observed on any response.
- id: cors
  conforms: true
  evidence: >-
    Access-Control-Allow-Origin *, Allow-Methods GET, and
    Access-Control-Expose-Headers X-WP-Total, X-WP-TotalPages, Link.
- id: oembed
  conforms: true
  evidence: >-
    The oembed/1.0 namespace with /embed and /proxy routes is declared in the
    harvested discovery index (a WordPress platform default).
- id: rss
  conforms: true
  evidence: >-
    https://blog.remax.ca/feed/ returns HTTP 200, 411,175 bytes,
    Content-Type application/rss+xml.
- id: robots-ai-preferences
  conforms: true
  evidence: >-
    blog.remax.ca/robots.txt names and explicitly allows GPTBot, OAI-SearchBot,
    ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot,
    Perplexity-User, Google-Extended, CCBot and cohere-ai. An explicit,
    machine-readable agent-access preference — the opposite of the
    www.remax.ca terms of use, which forbid automated access outright.
compliance_program:
  published: false
  certifications: []
  note: >-
    No trust centre, no SOC 2 / ISO 27001 / PCI DSS / HIPAA claim and no
    compliance page was found (trust.remax.ca is a DNS wildcard artifact).
    Because no certification is published, NO `Compliance` pointer is wired into
    apis.yml.
sector_context: >-
  RESO conformance in Canada is a board-level phenomenon. The national
  cooperative that actually syndicates listings — CREA, via REALTOR.ca and the
  Data Distribution Facility — appears in RESO as a Class F association member
  rather than as a certified data provider, and only 2 of the 30 observed
  Canadian directory entries carry status "Certified Current". A brokerage brand
  is structurally the wrong tier to look for RESO conformance in either country.