UCP Checker
Back to status
funwayamusements.com icon
UCP Score

UCP Score for funwayamusements.com

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

✓Verified
A86/100
Analyzed Oct 12, 2026 · 3 recommendations ·Wix · v2026-04-08 upgrade
86
/ 100
UCP Score
A

funwayamusements.com publishes a conforming profile 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 the public keys agents use to check your messages → Move to the latest UCP protocol version

Verified

funwayamusements.com publishes a valid UCP profile, with minor schema warnings.

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

Top Priorities

1
Fix broken spec or schema URLs

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

Medium impact Low effort
2
Publish the public keys agents use to check your messages

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Medium impact Medium effort
3
Move to the latest UCP protocol version

Your profile declares a valid but older protocol version. A newer one is published.

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(0)

High impact, high effort

  • No items
Incremental Gains(2)

Medium impact & effort

  • Fix broken spec or schema URLs
  • Publish the public keys agents use to check your messages
Consider Later(1)

Lower priority

  • Move to the latest UCP protocol version

How you compare on Wix

Response time benchmarked against 7,453 Wixes we monitor.

fastWix median 397msslow
Your store
321ms
Wix percentile
Top 10%
Faster than 95% of Wix stores
Cohort range
349–463ms
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 profile 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 profile setup. See the Full Check Breakdown for the specific URLs that failed.

UCP_PROBE_URL_BROKEN
2

Publish the public keys agents use to check your messages

Medium impact Medium effort

Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.

Why it matters

Agents use these keys to check that checkout messages really came from you. A store that takes payment through the agent needs them. A store that sends the buyer to its own checkout page can manage without them for now.

Show fix

Create an Ed25519 key pair. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, and keep the private key on your server. Replace the key once a year, giving each new key its own "kid".

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

Move to the latest UCP protocol version

Low impact Low effort

Your profile declares a valid but older protocol version. A newer one is published.

Why it matters

Older versions stay valid (agents use the version you declare), but newer abilities (embedded checkout, agent payment mandates, linked customer accounts, card authentication, payment terms and store location lookup) only work against the latest version. The profile itself barely changes: the signing keys move to a root-level "keys" list, and the rest of the update is in what capabilities can say.

Show fix

Set the version to 2026-08-25 and publish your public keys as a root-level "keys" list. The older "signing_keys" field is still accepted, but "keys" is the one every verifier reads.

"ucp": {
  "version": "2026-08-25",
  ...
},
"keys": [ ... ]   // beside "ucp", not inside it
UCP_VERSION_OUTDATED

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 profile?

  • HTTPSCore

    Profile served over a secure connection.

    Profile 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 profile reachableCore

    Profile 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 profile.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published profile 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 profile 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 profile meet the published spec?

  • Profile passes schema validationCore

    Profile structure conforms to the published UCP spec.

    No structural errors

    Why it matters

    Strict UCP agents reject profiles 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-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.

  • No validation warningsCore

    Profile passes structural and field-level rules.

    1 warning

    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 profile 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 of 6 capability families detected: Checkout, Cart Management, Catalog. A family counts once however many namespaces or extensions declare it.

    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/dc01ce01-5080-456a-aaa2-9b1acba31139.

    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 profile itself looks perfect.

  • MCP transport reachableInterop

    Live reachability check against https://www.wixapis.com/ecom/ucp/dc01ce01-5080-456a-aaa2-9b1acba31139/mcp.

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

    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 profile itself looks perfect.

/llms.txt content

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

3.1 KBc4f84dc21224ac47
# Funway Amusements

> Funway Amusements is a family entertainment center with two locations in Michigan: Farmington Hills (metro Detroit) and Saginaw. There is no entry fee at either location. Visitors pay only for the attractions they choose, starting at $4, or buy an unlimited play wristband. Both locations have an on-site restaurant serving halal food.

## Locations

- Farmington Hills: 30749 Grand River Ave, Farmington Hills, MI 48336. Phone (248) 471-5100. https://www.funwayamusements.com/farmingtonhills
- Saginaw: 5200 Kokomo Dr, Saginaw, MI 48604. Phone (989) 797-5656. https://www.funwayamusements.com/saginaw

## Hours (both locations)

- Monday to Thursday: 4:00 PM to 9:00 PM
- Friday: 4:00 PM to 10:00 PM
- Saturday: 12:00 PM to 10:00 PM
- Sunday: 12:00 PM to 9:00 PM

Hours can vary on holidays and seasonally.

## Attractions by location

Both locations: go-karts, mini golf, batting cages.

Farmington Hills only: VR rides, bungee trampoline.

Saginaw only: laser tag, bumper boats, bounce house.

## Pricing

- Batting cages: from $4, no height requirement
- Bounce house (Saginaw): $8, 48 inch minimum height
- Bungee trampoline (Farmington Hills): $9, 48 inch minimum height
- Bumper boats (Saginaw): $9, 48 inch minimum height
- Mini golf: $10, no height requirement
- Laser tag (Saginaw): $10, 48 inch minimum height
- VR rides (Farmington Hills): $10 single ride, $25 one hour unlimited, $40 two hours unlimited
- Go-karts: from $11, 54 inch minimum height

Attractions with no height requirement, suitable for younger children: mini golf and batting cages.

## Parties and field trips

- Birthday parties: $35 per person, 10 guest minimum. Includes two hours of unlimited outdoor attractions, a two hour party table in the dining room, two slices of pizza per guest, and unlimited soft drinks. Private party rooms and costumed characters available as upgrades.
- Field trips: $25 per person, 30 guest minimum. Includes three hours of unlimited outdoor attractions, two slices of pizza per guest, a two hour table area, and one soft drink per guest.
- Booking at least a week ahead is recommended. Last-minute bookings are sometimes possible when space allows.

## Food

On-site restaurant serving 14 inch pizzas by the pie or slice, cheesy breadsticks, jumbo chicken wings, chicken tenders and fries, nachos with cheese, hot dogs and slushies. Halal food is available at both locations.

## Visiting

- Walk-ins are welcome for individual attractions and unlimited play passes. No reservation needed.
- Parties and field trips should be booked in advance.
- Free on-site parking at both locations.
- No entry fee.

## Key pages

- Home: https://www.funwayamusements.com
- Farmington Hills attractions: https://www.funwayamusements.com/farmingtonhills
- Saginaw attractions: https://www.funwayamusements.com/saginaw
- Parties and field trips: https://www.funwayamusements.com/party
- Buy tickets and wristbands online: https://www.funwayamusements.com/buyonline
- Food menu: https://www.funwayamusements.com/eat
- Gift cards: https://www.funwayamusements.com/gift-card
- Contact: https://www.funwayamusements.com/contact
View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-04-08
Checkout ✓ Bound 2026-04-08
Discount Extension ✓ 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://funwayamusements.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 funwayamusements.com badge for https://ucpchecker.com/score/funwayamusements.comLive preview
Markdown
[![UCP Score for funwayamusements.com](https://ucpchecker.com/score/funwayamusements.com/badge.svg)](https://ucpchecker.com/score/funwayamusements.com)
HTML
<a href="https://ucpchecker.com/score/funwayamusements.com"><img src="https://ucpchecker.com/score/funwayamusements.com/badge.svg" alt="UCP Score for funwayamusements.com"></a>
New · Early access open
Is funwayamusements.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 funwayamusements.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.