UCP Checker
Back to status
yalarizo.co.id icon
UCP Score

UCP Score for yalarizo.co.id

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

✓Verified
A86/100
Analyzed Sep 29, 2026 · 3 recommendations ·Wix · v2026-08-25 latest
86
/ 100
UCP Conformance Score
A

yalarizo.co.id publishes a conforming manifest with broad capability coverage.

Agent Discovery100
UCP Conformance81
Capability Coverage80
Working

Agent Discovery is solid (100/100).

Start Here

Fix broken spec or schema URLs → Publish keys at the manifest root → Publish a schema URL for the service

Verified

yalarizo.co.id publishes a valid UCP manifest, with minor schema warnings.

Latency
473ms
Version
2026-08-25
Robots.txt
Allowed ✅

Top Priorities

1
Fix broken spec or schema URLs

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

Medium impact Low effort
2
Publish keys at the manifest root

Agents have nothing to verify your responses against.

Medium impact Medium effort
3
Publish a schema URL for the service

Service is missing its "schema" URL.

Low impact Medium effort

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

  • No items
Strategic Investments(0)

High impact, high effort

  • No items
Incremental Gains(2)

Medium impact & effort

  • Fix broken spec or schema URLs
  • Publish keys at the manifest root
Consider Later(1)

Lower priority

  • Publish a schema URL for the service

How you compare on Wix

Response time benchmarked against 7,497 Wixes we monitor.

fastWix median 438msslow
Your store
473ms
Wix percentile
Below median
Faster than 33% of Wix stores
Cohort range
398–497ms
p25 to p75 (middle half)

Recommendations

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

1

Fix broken spec or schema URLs

Medium impact Low effort ×6

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
2

Publish keys at the manifest root

Medium impact Medium effort

Agents have nothing to verify your responses against.

Why it matters

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.

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
3

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 .
Agent Discovery8/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.

    Organization-typed JSON-LD detected

    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.

  • Protocol version present and well-formedCore

    ucp.version follows YYYY-MM-DD format.

    Version: 2026-08-25

    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.

  • No validation warningsCore

    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 (12)Core

    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, …

    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 Coverage4/6 passed

What operations can agents actually perform?

  • Capabilities declaredCore

    Number of agent-readable capabilities under ucp.capabilities.

    3 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/250280f5-e064-473d-ab72-375da9faa6ce.

    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/250280f5-e064-473d-ab72-375da9faa6ce/mcp.

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

    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.4 KBe8234c4480a730c8
# Bika Ambon Larizo
> Larizo adalah produsen Bika Ambon yang telah beroperasi sejak tahun 1999, dengan fokus pada kualitas dan kesehatan produk. Perusahaan ini menawarkan berbagai varian Bika Ambon, serta kategori produk lain seperti roti, bolu, dan jajan pasar. Larizo juga memiliki program beasiswa untuk membantu generasi muda Indonesia meraih pendidikan tinggi, yang didukung oleh pelanggan setia dan donatur. Selain itu, Larizo telah memperluas jangkauannya melalui toko online di Shopee dan Tokopedia, memastikan kelezatan produknya dapat dinikmati di seluruh Indonesia.

## Homepage link
- [home](https://yalarizo.co.id/)

## Akses Agen AI

Situs ini didukung oleh Wix dan mendukung Model Context Protocol (MCP)
untuk akses AI agentik. Agen AI dapat terhubung langsung untuk mengambil konten situs langsung dan terkini - tidak perlu scraping.

- [**Titik Akhir MCP Situs**](https://yalarizo.co.id/_api/mcp)
- [**Dokumentasi MCP Wix**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)

## Alat MCP yang Tersedia

### GetBusinessDetails
Mengambil detail bisnis dan situs seperti zona waktu, email, telepon, dan alamat.
- Tidak ada parameter yang diperlukan.

### SearchInSite
Mencari informasi di situs.
- **searchTerm** - Istilah yang akan dicari di situs.

### SearchSiteApiDocs
Mengambil dokumentasi API untuk solusi bisnis Wix yang terinstal di
situs ini, dan memberi tahu klien AI cara menggunakan API. Gunakan alat ini untuk
menanyakan produk dan layanan (bukan SearchInSite).
- **searchTerm** - Istilah yang akan dicari di dokumentasi API situs.

### GenerateVisitorToken
Membuat sesi pengunjung baru dan mendapatkan token akses pengunjung untuk Situs.
Harus dipanggil sebelum membuat permintaan CallWixSiteAPI apa pun jika tidak ada token pengunjung
yang sudah tersedia dalam konteks.
- Tidak ada parameter yang diperlukan.

### CallWixSiteAPI
Memanggil metode API di situs untuk melakukan tindakan atas nama pengunjung,
seperti menanyakan data situs, memesan janji temu, atau memulai pembelian.
- **visitorToken** - Token akses pengunjung. Gunakan GenerateVisitorToken terlebih dahulu jika tidak tersedia.
- **url** - URL absolut metode API yang akan dipanggil (mis., https://www.wixapis.com/...). Ambil menggunakan SearchSiteApiDocs.
- **method** - Metode HTTP yang akan digunakan untuk panggilan API.
- **body** - Isi permintaan sebagai string JSON yang valid.

### ReadFullDocsArticle
Mengambil artikel lengkap dari portal dokumentasi Developer Wix.
- **articleUrl** - URL sebuah artikel di portal dokumentasi developer Wix.

### ReadFullDocsMethodSchema
Mengambil skema lengkap untuk metode API Wix. Harus dipanggil sebelum
memanggil metode yang sebenarnya melalui CallWixSiteAPI.
- **articleUrl** - URL artikel referensi untuk metode API Wix.

## Yang Dapat Dilakukan Pengunjung melalui AI + MCP

- Mendapatkan detail bisnis (info kontak, lokasi, jam kerja)
- Menemukan produk dan layanan yang ditawarkan
- Memesan layanan dan membuat reservasi
- Memulai pembelian dan diarahkan ke situs untuk menyelesaikan checkout
- Mengajukan pertanyaan dan mendapatkan jawaban yang relevan tanpa harus menjelajahi situs

## Catatan

- Tidak diperlukan autentikasi untuk terhubung ke titik akhir MCP
- Hanya informasi publik yang dapat diakses di situs yang tersedia
- Konten selalu langsung dan terbaru
- Untuk menerima pembaruan alat, terapkan panggilan alat/daftar setelah menerima notifikasi pembaruan alat
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
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

Technical Vitals

Technical details for this UCP endpoint
UCP Status Verified
Endpoint https://yalarizo.co.id/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
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 yalarizo.co.id badge for https://ucpchecker.com/score/yalarizo.co.idLive preview
Markdown
[![UCP Score for yalarizo.co.id](https://ucpchecker.com/score/yalarizo.co.id/badge.svg)](https://ucpchecker.com/score/yalarizo.co.id)
HTML
<a href="https://ucpchecker.com/score/yalarizo.co.id"><img src="https://ucpchecker.com/score/yalarizo.co.id/badge.svg" alt="UCP Score for yalarizo.co.id"></a>
New · Early access open
Is yalarizo.co.id 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 yalarizo.co.id'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.