UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
labinmed.com.br publishes a conforming manifest with broad capability coverage.
Agent Discovery is solid (100/100).
Fix broken spec or schema URLs → Publish keys at the manifest root → Publish a schema URL for the service
One or more spec/schema URLs declared in the manifest do not resolve.
Agents have nothing to verify your responses against.
Service is missing its "schema" URL.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
Response time benchmarked against 7,325 Wixes we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
One or more spec/schema URLs declared in the manifest do not resolve.
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.
Agents have nothing to verify your responses against.
Signing keys let agents check that checkout responses really came from you. Tokenized payment flows in v2026-04-08+ require them. Since 2026-07-12 the spec expects a root-level "keys" list (the older "signing_keys" field is still accepted while stores move). Stores that hand the buyer a checkout link instead of taking payment through the agent can go without them for now.
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": { ... }
}Service is missing its "schema" URL.
The schema lets agents validate request/response shapes before sending. Highly recommended for any non-trivial endpoint.
"schema": "https://yourstore.com/.well-known/ucp/schemas/shopping.json"Every signal we evaluate, grouped by category.
Can AI agents find your store and its UCP manifest?
Manifest served over a secure connection.
Manifest URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Manifest fetched OK from /.well-known/ucp.
HTTP 200
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
robots.txt allows agent crawlers to fetch the manifest.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published manifest gets ignored if the file is disallowed for known agent user-agents.
Hand-written brief at /llms.txt for AI agents.
Found at /llms.txt
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
XML sitemap published at /sitemap.xml.
Found at /sitemap.xml
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
OG meta tags on the homepage.
og:title and og:type/url present
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Schema.org Organization (or OnlineStore) JSON-LD on homepage.
Organization-typed JSON-LD detected
Gives agents a structured representation of your brand identity — used to verify you are who your manifest claims you are.
Viewport meta tag for mobile rendering.
<meta name="viewport"> present
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.
Does your manifest meet the published spec?
Manifest structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject manifests with structural errors. The error code in the diagnostic shows which field failed.
ucp.version follows YYYY-MM-DD format.
Version: 2026-08-25
UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.
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)
Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.
Manifest passes structural and field-level rules.
2 warnings
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 12 spec/schema URLs declared across the manifest to confirm agents can fetch each one.
Did not resolve (6 of 12): https://ucp.dev/services/shopping/rest.openapi.json, https://ucp.dev/schemas/shopping/cart.json, https://ucp.dev/schemas/shopping/catalog-lookup.json, https://ucp.dev/schemas/shopping/checkout.json, https://ucp.dev/schemas/shopping/fulfillment.json, …
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.
What operations can agents actually perform?
Number of agent-readable capabilities under ucp.capabilities.
3 capabilities detected
Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.
Store declares a checkout-namespaced capability.
dev.ucp.shopping.checkout detected
Without a checkout capability, agents can browse but can't complete a purchase end-to-end.
Service transports (REST/MCP/A2A/Embedded) declared on services.
REST, MCP
Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.
Tokenized payment handlers registered for in-conversation checkout.
Empty array: checkout-link redirect strategy
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
Live reachability check against https://www.wixapis.com/ecom/ucp/f20ea66d-65ad-4e9f-9667-739ca217db7c.
Host responded with HTTP 404 — endpoint reachable but path may be method-restricted
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.
Live reachability check against https://www.wixapis.com/ecom/ucp/f20ea66d-65ad-4e9f-9667-739ca217db7c/mcp.
tools/list returned a JSON-RPC response in 158ms
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.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# Laboratório Labinmed
> O Laboratório Labinmed oferece uma ampla gama de exames de análises clínicas e patológicas, com 18 anos de experiência no Distrito Federal e Goiás. O laboratório se destaca pela excelência, equipamentos de última geração e investimento em capacitação profissional, possuindo acreditação nacional DICQ/SISTEMA NACIONAL DE ACREDITAÇÃO. O Labinmed também disponibiliza resultados de exames online, possui diversas unidades de atendimento, aceita múltiplos convênios e oferece serviços como atendimento móvel gratuito e programas de cuidado para pacientes e colaboradores.
## Homepage link
- [home](https://labinmed.com.br/)
## Acesso de agentes de IA
Este site é desenvolvido pelo Wix e é compatível com o Model Context Protocol (MCP)
para acesso de IA agêntica. Agentes de IA podem se conectar diretamente para recuperar
conteúdo do site online e atualizado - não é necessário extrair dados.
- [**Endpoint MCP do site**](https://labinmed.com.br/_api/mcp)
- [**Wix MCP Docs**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)
## Ferramentas MCP disponíveis
### GetBusinessDetails
Recupera informações comerciais e do site, como fuso horário, email, telefone e endereço.
- Nenhum parâmetro é necessário.
### SearchInSite
Faz buscas no site para obter informações.
- **searchTerm** - O termo a ser buscado no site.
### SearchSiteApiDocs
Recupera a API documentation para as soluções de negócios Wix instaladas
neste site e informa o cliente de IA como usar as APIs. Use este recurso para
consultar produtos e serviços (em vez de SearchInSite).
- **searchTerm** - O termo a ser buscado na API documentation do site.
### GenerateVisitorToken
Cria uma nova sessão de visitante e obtém um token de acesso de visitante para o site.
Deve ser chamado antes de fazer qualquer solicitação de CallWixSiteAPI se nenhum token de visitante
estiver disponível no contexto.
- Nenhum parâmetro é necessário.
### CallWixSiteAPI
Faz chamadas dos métodos da API no site para realizar ações em nome de um visitante,
como consultar dados do site, fazer um agendamento ou iniciar uma compra.
- **visitorToken** - Token de acesso do visitante. Use GenerateVisitorToken primeiro se não estiver disponível.
- **url** - URL absoluto do método da API a ser chamado (por exemplo: https://www.wixapis.com/...). Recupere usando SearchSiteApiDocs.
- **method** - Método HTTP a ser usado para a chamada de API.
- **body** - Corpo da solicitação como uma string do JSON válida.
### ReadFullDocsArticle
Busca um artigo completo do portal de documentação para desenvolvedores Wix.
- **articleUrl** - URL de um artigo no portal de documentação para desenvolvedores Wix.
### ReadFullDocsMethodSchema
Busca o esquema completo para um método da API do Wix. Deve ser chamado antes de
chamar o método real via CallWixSiteAPI.
- **articleUrl** - URL do artigo de referência para o método da API do Wix.
## O que os visitantes podem fazer via IA + MCP
- Obter informações comerciais (informações de contato, local, horário)
- Descobrir produtos e serviços em oferta
- Agendar serviços e fazer reservas
- Iniciar uma compra e ser direcionado para o site para concluir o checkout
- Fazer perguntas e obter respostas relevantes sem precisar navegar no site
## Observações
- Nenhuma autenticação é necessária para se conectar ao endpoint MCP
- Apenas informações públicas acessíveis no site estão disponíveis
- O conteúdo está sempre online e em tempo real
- Para receber atualizações de ferramentas, implemente uma chamada de tools/list ao receber uma notificação de atualização de ferramenta| Cart ✓ Bound | 2026-08-25 |
| Checkout ✓ Bound | 2026-08-25 |
| Fulfillment Extension ✓ Bound | 2026-08-25 |
| Catalog Lookup ✓ Bound | 2026-08-25 |
| Catalog Search ✓ Bound | 2026-08-25 |
| UCP Status | Verified |
| Endpoint | https://labinmed.com.br/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-08-25 |
| Transports | REST, MCP |
| Last Observed | |
| Last Full Index |
Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.
Live preview[](https://ucpchecker.com/score/labinmed.com.br)<a href="https://ucpchecker.com/score/labinmed.com.br"><img src="https://ucpchecker.com/score/labinmed.com.br/badge.svg" alt="UCP Score for labinmed.com.br"></a>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.
Track labinmed.com.br'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.
Track domains and get emailed when their UCP status changes.
By continuing you agree to our Terms & Privacy Policy.