UCP Checker
Sign in Start monitoring
Back to status
finqu-agentic-commerce.vercel.app icon
UCP Score

UCP Score for finqu-agentic-commerce.vercel.app

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

✕Invalid
C56/100
Analyzed Oct 12, 2026 · 6 recommendations ·Custom · v2026-08-25 latest
56
/ 100
UCP Score
C

Partial UCP coverage — several improvements would lift the score.

Agent Discovery80
UCP Conformance42
Capability Coverage50
Biggest blockers
Declare ucp.services
Working

Agent Discovery is solid (80/100).

Blocking

Declare ucp.services: No services declared, so agents have no transport endpoints to call.

Start Here

Declare ucp.services → Publish the public keys agents use to check your messages → Publish Organization schema (JSON-LD) on the homepage

Invalid

finqu-agentic-commerce.vercel.app responded, but its profile did not pass schema validation.

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

Top Priorities

1
Declare ucp.services

No services declared, so agents have no transport endpoints to call.

High impact Medium 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
Publish Organization schema (JSON-LD) on the homepage

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

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

High impact, high effort

  • Declare ucp.services
Incremental Gains(2)

Medium impact & effort

  • Publish the public keys agents use to check your messages
  • Publish Organization schema (JSON-LD) on the homepage
Consider Later(3)

Lower priority

  • Publish a /llms.txt brand brief
  • Publish a sitemap.xml
  • Add Open Graph meta tags to the homepage

How you compare on Custom

Response time benchmarked against 132 Customs we monitor.

fastCustom median 315msslow
Your store
272ms
Custom percentile
Above median
Faster than 59% of Custom stores
Cohort range
160–507ms
p25 to p75 (middle half)
Headless / custom stackCustom-built storefronts have the most flexibility but also the most surface area for inconsistency between environments. Run the score in staging before each deploy that touches profile, schemas, or transports.

Recommendations

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

1

Declare ucp.services

High impact Medium effort

No services declared, so agents have no transport endpoints to call.

Why it matters

Services are the actual endpoints agents hit. A capability without a service is a promise without a URL.

Show fix

Each service entry needs version, transport, endpoint (for REST/MCP/A2A), and a schema URL.

"ucp": {
  "services": {
    "dev.ucp.shopping": [
      {
        "version": "2026-08-25",
        "transport": "mcp",
        "endpoint": "https://yourstore.com/api/ucp/mcp",
        "spec": "https://ucp.dev/2026-08-25/specification/overview/",
        "schema": "https://yourstore.com/.well-known/ucp/schemas/shopping.json"
      }
    ]
  }
}
UCP_MISSING_SERVICES
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

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

Publish a /llms.txt brand brief

Low impact Low effort Emerging

No /llms.txt file detected at the root of your domain.

Why it matters

llms.txt is an emerging convention (analogous to robots.txt) that lets you give AI agents a hand-written brief about your brand, product categories, return policy, and crawl preferences. Strict UCP agents do not require it, but recommendation/discovery agents increasingly read it for context.

Show fix

Save as /llms.txt at your site root. Plain text, written for an LLM audience. The format is informal: these section headings are a working convention, not a spec. Replace the placeholders with your own brand details and update when policies or product lines change.

# llms.txt
# Public brief for AI agents about Yourstore

# About
One or two sentences on what you sell, who you sell to, and any defining context (founded, mission, sustainability stance, etc.).

# Product Categories
- Category one
- Category two
- Category three

# Policies
- Returns: e.g. 30 days, full refund
- Shipping: e.g. Free over $30, 3-5 business days
- Any other policy worth surfacing (cruelty-free, vegan, made-to-order, etc.)

# Agent Capabilities
- UCP manifest: /.well-known/ucp
- Supported flows: cart, checkout, tokenized payment, etc.
- Anything explicitly NOT supported (e.g. "no subscription products via agent")

# Contact
[email protected]
UCP_MISSING_LLMS_TXT
5

Publish a sitemap.xml

Low impact Low effort

No sitemap.xml detected at the root of your domain.

Why it matters

Sitemaps tell agents and crawlers which pages on your store are canonical and how often they change. Without one, agents fall back to following internal links, which is slower and less complete, especially for catalog pages buried behind faceted nav.

Show fix

Most ecommerce platforms generate sitemap.xml automatically. If yours does not, generate one and serve it at /sitemap.xml.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yourstore.com/</loc>
    <changefreq>daily</changefreq>
  </url>
  <url>
    <loc>https://yourstore.com/products</loc>
    <changefreq>daily</changefreq>
  </url>
  <!-- one <url> entry per indexable page -->
</urlset>
UCP_MISSING_SITEMAP
6

Add Open Graph meta tags to the homepage

Low impact Low effort

OG tags missing or incomplete on your homepage.

Why it matters

OG tags give agents and link unfurlers (Slack, iMessage, ChatGPT) a clean title, description, and image to represent your store. Without them, shares show garbled fallback text.

Show fix

Add inside <head>. og:title and og:type are the minimum; og:url, og:description, and og:image are strongly recommended.

<meta property="og:title" content="Yourstore | short tagline">
<meta property="og:type" content="website">
<meta property="og:url" content="https://yourstore.com/">
<meta property="og:description" content="One-sentence description of what you sell.">
<meta property="og:image" content="https://yourstore.com/og-cover.jpg">
<meta property="og:site_name" content="Yourstore">
UCP_MISSING_OG_TAGS

Full Check Breakdown

Every signal we evaluate, grouped by category.

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

    HTTP 404 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.

    HTTP 404 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.

    Missing or incomplete on homepage

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

Does your profile meet the published spec?

  • Profile passes schema validationCore

    Profile structure conforms to the published UCP spec.

    Missing required field: ucp.services

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

    Profile passes structural and field-level rules.

    No outstanding validation issues

    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.

    6 of 6 capability families detected: Checkout, Identity Linking, Cart Management, Order Management, Payment Token Exchange, 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.

    No transports declared

    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.

    No handlers declared

    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.

Capabilities Detected

UCP capabilities supported by this endpoint
Cart ✓ Bound 2026-08-25
Discount Extension ✓ Bound 2026-08-25
Order Management ✓ Bound 2026-08-25
Checkout ✓ Bound 2026-08-25
Loyalty Extension ✓ Bound 2026-08-25
Fulfillment Extension ✓ Bound 2026-08-25
Buyer Consent Extension ✓ Bound 2026-08-25
Split Payments Extension ✓ Bound 2026-08-25
Permalink ✓ Bound 2026-08-25
Location Lookup ✓ Bound 2026-08-25
Location Search ✓ Bound 2026-08-25
Identity Linking ✓ 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 Invalid
Endpoint https://finqu-agentic-commerce.vercel.app/.well-known/ucp
HTTP Status 200
UCP Version 2026-08-25
Transports —
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 finqu-agentic-commerce.vercel.app badge for https://ucpchecker.com/score/finqu-agentic-commerce.vercel.appLive preview
Markdown
[![UCP Score for finqu-agentic-commerce.vercel.app](https://ucpchecker.com/score/finqu-agentic-commerce.vercel.app/badge.svg)](https://ucpchecker.com/score/finqu-agentic-commerce.vercel.app)
HTML
<a href="https://ucpchecker.com/score/finqu-agentic-commerce.vercel.app"><img src="https://ucpchecker.com/score/finqu-agentic-commerce.vercel.app/badge.svg" alt="UCP Score for finqu-agentic-commerce.vercel.app"></a>
New · Early access open
Is finqu-agentic-commerce.vercel.app 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 finqu-agentic-commerce.vercel.app'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.