What does it mean that golfrivesud.ca is verified for UCP?

It means golfrivesud.ca publishes a valid UCP manifest at /.well-known/ucp, the manifest passes schema validation against 2026-04-08, and AI agents can discover its commerce capabilities without needing to scrape HTML. In plain terms: agents can shop here reliably.

Can I trust golfrivesud.ca for AI agent purchases?

Verification means the store is technically ready — payment handlers declared, transports reachable, schema valid. It doesn't grade business reputation or fulfilment quality. For trust on the commerce side itself, check the store's own reviews. For trust on the agent integration side, this page is the source of truth.

What platform does golfrivesud.ca use for UCP?

Our detection identifies golfrivesud.ca as running on Wix. Many large UCP-verified stores use Shopify, BigCommerce, or custom stacks built on the open spec. The transport list above shows the exact mechanism (REST, MCP, A2A, Embedded) the manifest declares.

How was this UCP report for golfrivesud.ca generated?

Our crawler fetches golfrivesud.ca/.well-known/ucp directly, parses the manifest against the official UCP JSON schema, checks robots.txt for AI bot policies, and runs payment-handler validation. No manual review, no opinions — just what the manifest actually says. The check ran 3 hours ago.

How often is golfrivesud.ca re-checked?

Every domain in our directory is re-crawled at least every 24 hours. You can also trigger a fresh check from this page at any time, or subscribe to alerts to get notified the moment the status changes — that's how we built the only continuously updated UCP directory on the internet.

Why does this status matter?

Universal Commerce Protocol is the standard AI shopping agents (ChatGPT, Claude, Gemini, Apple Intelligence) use to discover what a store sells, how to add items to a cart, and how to check out. If a store isn't UCP-verified, agents can still scrape it — but they'll be slower, less reliable, and far more likely to fail at checkout. UCP turns a guess into a guarantee.

Back to status

UCP Score

UCP Score for golfrivesud.ca

UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.

✓Verified

B84/100

Analyzed Sep 18, 2026 · 7 recommendations ·Wix · v2026-04-08 upgrade

/ 100

UCP Conformance Score

Solid UCP setup on golfrivesud.ca with a few gaps left to close.

Agent Discovery95

UCP Conformance81

Capability Coverage77

Biggest blockers

Publish keys at the manifest rootRepair declared transport endpoints

Working

Agent Discovery is solid (95/100).

Blocking

Publish keys at the manifest root — Agents have nothing to verify your responses against.

Start Here

Publish keys at the manifest root → Repair declared transport endpoints → Fix broken spec or schema URLs

Top Priorities

Publish keys at the manifest root

Agents have nothing to verify your responses against.

High impact Medium effort

Repair declared transport endpoints

One or more declared transport endpoints did not respond when probed.

High impact Medium effort

Fix broken spec or schema URLs

One or more spec/schema URLs declared in the manifest do not resolve.

Medium impact Low effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

No items

Strategic Investments(2)

High impact, high effort

Publish keys at the manifest root
Repair declared transport endpoints

Incremental Gains(2)

Medium impact & effort

Fix broken spec or schema URLs
Publish Organization schema (JSON-LD) on the homepage

Consider Later(3)

Lower priority

Confirm checkout-link redirect strategy
Upgrade to the latest UCP spec version
Publish a schema URL for the service

How you compare on Wix

Response time benchmarked against 6,678 Wixes we monitor.

fastWix median 137msslow

Your store

210ms

Wix percentile

Bottom quartile

Faster than 13% of Wix stores

Cohort range

123–162ms

p25 to p75 (middle half)

Recommendations

All improvements ranked by priority, with evidence and actionable fixes.

Publish keys at the manifest root

High impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

Signing keys let agents cryptographically verify checkout responses came from you, not a man-in-the-middle. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec's canonical field is a root-level RFC 7517 "keys" array (the legacy "signing_keys" field was removed from the profile schema; we accept both during the migration). Stores using checkout-link redirects (e.g. WooCommerce) often skip this safely.

Show fix

Generate an Ed25519 keypair, publish the public key as a JWK in a root-level "keys" array (the canonical field since spec PR #566; "signing_keys" is legacy). Rotate annually; keep "kid" stable across rotations of the same key.

{
  "keys": [
    {
      "kty": "OKP",
      "crv": "Ed25519",
      "x": "<base64url-encoded-public-key>",
      "kid": "key-2026-04",
      "alg": "EdDSA"
    }
  ],
  "ucp": { ... }
}

UCP_MISSING_SIGNING_KEYS

Repair declared transport endpoints

High impact Medium effort

One or more declared transport endpoints did not respond when probed.

Why it matters

A manifest that declares transports without working endpoints is the worst kind of broken — it looks perfect to static validators but agents hit a dead end the moment they try to use the capability. Connection refused, DNS failure, TLS errors, and 5xx responses all fall here. See the Full Check Breakdown below for the specific endpoints that failed.

UCP_PROBE_TRANSPORT_FAILED

Fix broken spec or schema URLs

Medium impact Low effort ×5

One or more spec/schema URLs declared in the manifest do not resolve.

Why it matters

Spec and schema URLs let agents validate request/response shapes before sending. When they 404 or time out, runtime validation degrades to "best effort" and strict agents reject the integration entirely. Common cause: copy-pasting a placeholder URL during initial manifest setup. See the Full Check Breakdown for the specific URLs that failed.

UCP_PROBE_URL_BROKEN

Publish Organization schema (JSON-LD) on the homepage

Medium impact Medium effort

No Organization-typed JSON-LD detected on your homepage.

Why it matters

Organization schema gives agents a structured representation of your brand identity — name, logo, social profiles, contact info, founding date. Agents use this to verify you are who you claim to be and to link your manifest data to a recognizable entity.

Show fix

Drop into <head> or end of <body>. Use OnlineStore (more specific) when the entire site is an ecommerce store; Organization is the generic fallback.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "name": "Yourstore",
  "url": "https://yourstore.com",
  "logo": "https://yourstore.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourstore",
    "https://www.instagram.com/yourstore"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-800-000-0000",
    "contactType": "Customer Service"
  }
}
</script>

UCP_MISSING_ORG_SCHEMA

Confirm checkout-link redirect strategy

Low impact Low effort

payment_handlers is present but empty.

Why it matters

An empty payment_handlers array tells agents "I do not tokenize — redirect the buyer to my hosted checkout instead." Common and valid for WooCommerce stores. Only an issue if you intended to support tokenized payment.

UCP_EMPTY_PAYMENT_HANDLERS

Upgrade to the latest UCP spec version

Low impact Low effort

Your manifest declares a valid but older spec version. A newer published version is available.

Why it matters

Older versions stay valid (agents pin to the version you declare), but newer agent capabilities — embedded checkout, AP2 mandates, identity linking, 3DS payment authentication, payment terms and location lookup — only resolve against the latest spec. The manifest envelope barely moved: signing_keys went from inside ucp to the root as of 2026-04-08, and v2026-08-25 replaced it with keys (a JWK Set). Everything else in v2026-08-25 changed in the capability vocabulary, not the envelope.

Show fix

Bump version to 2026-08-25 and publish your public keys as a root-level keys array (JWK Set). Legacy signing_keys is still accepted, at the root or nested, but keys is the canonical field every verifier reads. See /specs/2026-08-25 for the full release notes.

"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // JWK Set, sibling of ucp, not nested inside

UCP_VERSION_OUTDATED

Publish a schema URL for the service

Low impact Medium effort

Service is missing its "schema" URL.

Why it matters

The schema lets agents validate request/response shapes before sending. Highly recommended for any non-trivial endpoint.

Show fix

"schema": "https://yourstore.com/.well-known/ucp/schemas/shopping.json"

UCP_SERVICE_MISSING_SCHEMA

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran Sep 14, 2026.

Agent Discovery7/8 passed

Can AI agents find your store and its UCP manifest?

HTTPSCore

Manifest served over a secure connection.

Manifest URL uses https://

Why it matters
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
UCP manifest reachableCore

Manifest fetched OK from /.well-known/ucp.

HTTP 200

Why it matters
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
AI bot accessCore

robots.txt allows agent crawlers to fetch the manifest.

robots.txt allows /.well-known/ucp

Why it matters
Agents respect robots.txt. Even a published manifest gets ignored if the file is disallowed for known agent user-agents.
llms.txtExperimental

Hand-written brief at /llms.txt for AI agents.

Found at /llms.txt

Why it matters
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
sitemap.xmlCore

XML sitemap published at /sitemap.xml.

Found at /sitemap.xml

Why it matters
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
Open Graph tagsCore

OG meta tags on the homepage.

og:title and og:type/url present

Why it matters
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Organization schema (JSON-LD)Core

Schema.org Organization (or OnlineStore) JSON-LD on homepage.

Missing or incomplete on homepage

Why it matters
Gives agents a structured representation of your brand identity — used to verify you are who your manifest claims you are.
Mobile viewport metaCore

Viewport meta tag for mobile rendering.

<meta name="viewport"> present

Why it matters
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.

UCP Conformance2/5 passed

Does your manifest meet the published spec?

Manifest passes schema validationCore

Manifest structure conforms to the published UCP spec.

No structural errors

Why it matters
Strict UCP agents reject manifests with structural errors. The error code in the diagnostic shows which field failed.
Spec version present and well-formedCore

ucp.version follows YYYY-MM-DD format.

Version: 2026-04-08

Why it matters
UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.
Signing keys publishedCore

Root-level keys array (canonical since 2026-07-12; legacy signing_keys also accepted) for response verification.

No signing_keys at root (common for managed/redirect-checkout stores)

Why it matters
Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.
Validation warnings clearCore

Manifest passes structural and field-level rules.

2 warnings

Why it matters
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Spec & schema URLs resolve (10)Core

Resolves the 10 spec/schema URLs declared across the manifest to confirm agents can fetch each one.

Did not resolve (5 of 10): https://ucp.dev/services/shopping/rest.openapi.json, https://ucp.dev/schemas/shopping/checkout.json, https://ucp.dev/schemas/shopping/fulfillment.json, https://ucp.dev/schemas/shopping/catalog-search.json, https://ucp.dev/schemas/shopping/catalog-lookup.json

Why it matters
Spec and schema URLs let agents validate request/response shapes before sending. Broken URLs degrade runtime validation to "best effort" and cause strict agents to refuse the capability entirely.

Capability Coverage3/6 passed

What operations can agents actually perform?

Capabilities declaredCore

Number of agent-readable capabilities under ucp.capabilities.

2 capabilities detected

Why it matters
Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.
Checkout capabilityCore

Store declares a checkout-namespaced capability.

dev.ucp.shopping.checkout detected

Why it matters
Without a checkout capability, agents can browse but can't complete a purchase end-to-end.
Transports declaredInterop

Service transports (REST/MCP/A2A/Embedded) declared on services.

REST, MCP

Why it matters
Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.
Payment handlersCore

Tokenized payment handlers registered for in-conversation checkout.

Empty array — checkout-link redirect strategy

Why it matters
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
REST transport reachableInterop

Live reachability check against https://www.wixapis.com/ecom/ucp/d913d0ac-c770-49b1-af55-e2bb6e5fb315.

Host responded with HTTP 404 — endpoint reachable but path may be method-restricted

Why it matters
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the manifest itself looks perfect.
MCP transport reachableInterop

Live reachability check against https://www.wixapis.com/ecom/ucp/d913d0ac-c770-49b1-af55-e2bb6e5fb315/mcp.

tools/list returned a JSON-RPC response in 178ms

Why it matters
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the manifest itself looks perfect.

/llms.txt content

The plain-text brief this store publishes to AI agents. Captured on the most recent check.

3.9 KBc21d89fd70184ac8

# Golf Rive-Sud
> Le Club de golf Rive-Sud présente une offre complète pour les passionnés de golf, incluant la découverte détaillée de son parcours, des installations d'entraînement et une boutique bien garnie. Le site met en avant son Académie, proposant des cours pour tous niveaux, ainsi que diverses ligues pour juniors, femmes et mixtes, axées sur l'apprentissage et la socialisation. Des services de fitting personnalisés, animés par des professionnels, sont également disponibles pour optimiser la performance des joueurs. En outre, le club célèbre l'héritage de Jack Bissegger, une figure marquante du golf québécois, renforçant ainsi son identité et son engagement envers le sport.

## Homepage link
- [home](https://www.golfrivesud.ca/)

## Accès des agents IA

Ce site est proposé par Wix et prend en charge le protocole MCP
pour l'accès de l'IA agentive. Les agents IA peuvent se connecter directement pour récupérer le contenu du site en ligne et à jour, sans avoir besoin d'extraire les données.

- [**Point de terminaison MCP du site**](https://www.golfrivesud.ca/_api/mcp)
- [**Documentation MCP de Wix**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)

## Outils MCP disponibles

### GetBusinessDetails
Récupère les détails de l'entreprise et du site tels que le fuseau horaire, l'e-mail, le téléphone et l'adresse.
- Aucun paramètre n'est requis.

### SearchInSite
Recherche des informations sur le site.
- **searchTerm** - Le terme à rechercher dans le site.

### SearchSiteApiDocs
Récupère la documentation de l'API pour les solutions professionnelles Wix installées sur ce site et informe le client IA sur la manière d'utiliser les API. Utilisez cet outil pour interroger les articles et les services (au lieu de SearchInSite).
- **searchTerm** - Le terme à rechercher dans la documentation de l'API du site.

### GenerateVisitorToken
Crée une nouvelle session de visiteur et obtient un jeton d'accès visiteur pour le site.
Doit être appelé avant d'effectuer toute requête CallWixSiteAPI si aucun jeton de visiteur n'est déjà disponible dans le contexte.
- Aucun paramètre n'est requis.

### CallWixSiteAPI
Appelle les méthodes d'API sur le site pour effectuer des actions au nom d'un visiteur, telles que l'interrogation des données du site, la réservation d'un rendez-vous ou le commencement d'un achat.
- **visitorToken** - Jeton d'accès visiteur. Utilisez GenerateVisitorToken en premier si non disponible.
- **url** - URL absolue de la méthode d'API à appeler (ex. https://www.wixapis.com/...). Récupérez en utilisant SearchSiteApiDocs.
- **method** - Méthode HTTP à utiliser pour l'appel d'API.
- **body** - Corps de la requête sous forme de chaîne JSON valide.

### ReadFullDocsArticle
Récupère un article complet du portail de documentation pour développeurs Wix.
- **articleUrl** - URL d'un article dans le portail de documentation pour développeurs Wix.

### ReadFullDocsMethodSchema
Récupère le schéma complet d'une méthode d'API Wix. Doit être appelé avant d'appeler la méthode réelle via CallWixSiteAPI.
- **articleUrl** - URL de l'article de référence pour la méthode d'API Wix.

## Ce que les visiteurs peuvent faire via l'IA + le MCP

- Obtenir les détails de l'entreprise (informations de contact, emplacement, horaires)
- Découvrir les articles et services proposés
- Effectuer des réservations
- Démarrer un achat et être redirigés vers le site pour finaliser le paiement
- Poser des questions et obtenir des réponses pertinentes sans avoir à parcourir le site

## Remarques

- Aucune authentification n'est requise pour se connecter au point de terminaison MCP
- Seules les informations publiques accessibles sur le site sont disponibles
- Le contenu est toujours en ligne et à jour
- Pour recevoir des mises à jour des outils, implémentez un appel tools/list dès réception d'une notification de mise à jour d'outil

View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Checkout ✓ Bound	2026-04-08
Fulfillment Extension ✓ Bound	2026-04-08
Catalog Lookup ✓ Bound	2026-04-08
Catalog Search ✓ Bound	2026-04-08

Technical Vitals

Technical details for this UCP endpoint
UCP Status	Verified
Endpoint	https://golfrivesud.ca/.well-known/ucp
HTTP Status	200
UCP Version	2026-04-08
Transports	REST, MCP
Last Observed	2026-09-18T13:14:06+00:00
Last Full Index	Sep 18, 2026 1:14 PM UTC

Embed your UCP Score

Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.

Live preview

Markdown

[![UCP Score for golfrivesud.ca](https://ucpchecker.com/score/golfrivesud.ca/badge.svg)](https://ucpchecker.com/score/golfrivesud.ca)

HTML

<a href="https://ucpchecker.com/score/golfrivesud.ca"><img src="https://ucpchecker.com/score/golfrivesud.ca/badge.svg" alt="UCP Score for golfrivesud.ca"></a>

New · Early access open

Is golfrivesud.ca yours? Claim it & monitor it daily

Prove ownership with one DNS record and the new monitoring dashboard watches it every day — score trends, break alerts, staging drift and a watchlist that benchmarks you against the field. Free while in beta.

Start monitoring →

This score reflects data from the most recent crawl. Run a fresh check to update, or read the methodology to see how each signal is scored.

Save this report

Track golfrivesud.ca's UCP score over time. We'll re-run the full check weekly and email you if the score drops, a capability regresses, or status flips.

Free. One email when something changes — no marketing. Privacy.