UCP Checker
Sign in Start monitoring
Back to status
petitsloustics.com icon
UCP Score

UCP Score for petitsloustics.com

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

✓Verified
A87/100
Analyzed Sep 19, 2026 · 5 recommendations ·Wix · v2026-04-08 upgrade
87
/ 100
UCP Conformance Score
A

petitsloustics.com is conforming and ready for agent discovery and checkout.

Agent Discovery95
UCP Conformance88
Capability Coverage78
Biggest blockers
Publish keys at the manifest root
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 → Publish Organization schema (JSON-LD) on the homepage → Confirm checkout-link redirect strategy

Verified

petitsloustics.com is agent-ready but has minor schema warnings.

Latency
122ms
Version
2026-04-08
Robots.txt
Allowed ✅

Top Priorities

1
Publish keys at the manifest root

Agents have nothing to verify your responses against.

High impact Medium effort
2
Publish Organization schema (JSON-LD) on the homepage

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

Medium impact Medium effort
3
Confirm checkout-link redirect strategy

payment_handlers is present but empty.

Low 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(1)

High impact, high effort

  • Publish keys at the manifest root
Incremental Gains(1)

Medium impact & effort

  • 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,773 Wixes we monitor.

fastWix median 136msslow
Your store
122ms
Wix percentile
Top quartile
Faster than 75% of Wix stores
Cohort range
122–165ms
p25 to p75 (middle half)

Recommendations

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

1

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
2

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
3

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
4

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
5

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.

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

Capability Coverage2/4 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.

/llms.txt content

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

3.9 KB3e31b86e1449451b
# Des Petits Loustics
> L'élevage des Petits Loustics se spécialise dans le Chihuahua, le Spitz Allemand et le Pomsky, mettant l'accent sur la santé, le caractère et la morphologie de ses chiens. L'éleveuse, Laurie Causse, partage son parcours passionné et son approche méticuleuse de la sélection, incluant des tests ADN et une connaissance approfondie des lignées. Le site détaille les conditions d'adoption, les processus de réservation et de paiement, ainsi que des informations sur les différentes races et leurs caractéristiques. Des conseils sur le quotidien avec un chiot et des témoignages de familles adoptantes sont également disponibles, soulignant l'engagement de l'élevage à offrir des compagnons équilibrés et aimants.

## Homepage link
- [home](https://www.petitsloustics.com/)

## 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.petitsloustics.com/_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://petitsloustics.com/.well-known/ucp
HTTP Status 200
UCP Version 2026-04-08
Transports REST, MCP
Last Observed
Last Full Index

Embed your UCP Score

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

UCP Score for petitsloustics.com badge for https://ucpchecker.com/score/petitsloustics.comLive preview
Markdown
[![UCP Score for petitsloustics.com](https://ucpchecker.com/score/petitsloustics.com/badge.svg)](https://ucpchecker.com/score/petitsloustics.com)
HTML
<a href="https://ucpchecker.com/score/petitsloustics.com"><img src="https://ucpchecker.com/score/petitsloustics.com/badge.svg" alt="UCP Score for petitsloustics.com"></a>
New · Early access open
Is petitsloustics.com 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 petitsloustics.com'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.