What does it mean that oc-integrations-test.ola.click is verified for UCP?

It means oc-integrations-test.ola.click publishes a valid UCP profile at /.well-known/ucp, the profile passes schema validation against 2026-08-25, and UCP agents can read what it offers from that file instead of from its web pages. That is what the store declares. Whether an agent actually completes a purchase is a separate question — where an observed agent run is shown on this page, it answers that one.

Can I trust oc-integrations-test.ola.click for AI agent purchases?

Verified means the store publishes a UCP profile at /.well-known/ucp that passes schema validation, with its services and payment handlers declared. Where we call a service, such as asking an MCP service for its tools, this page shows the answer; services we did not call are marked as declared only. It doesn't grade business reputation or fulfilment quality. For trust on the commerce side itself, check the store's own reviews. For the agent integration side, this page shows what the store's UCP profile declares and whether it validates.

How is oc-integrations-test.ola.click delivering UCP?

The transports listed above show how oc-integrations-test.ola.click's profile says agents reach it: REST, MCP (Model Context Protocol), A2A or Embedded.

How was this UCP report for oc-integrations-test.ola.click generated?

With public requests on 9 November 2026: we asked for oc-integrations-test.ola.click/.well-known/ucp and read its robots.txt, then validated the profile against the UCP release it declares and checked that its spec and schema links resolve. No sign-in, no purchase and no manual review. How we check.

How do I get a newer result for oc-integrations-test.ola.click?

This page shows the stored result of our last check (9 November 2026). To run a new one, enter oc-integrations-test.ola.click on the Check page.

Why does this status matter?

Universal Commerce Protocol is an open standard that lets a UCP agent find out what a store sells, build a cart and check out through a published contract instead of reading web pages. A valid UCP profile is how a store declares that support.

UCP Score

UCP Score for oc-integrations-test.ola.click

Nearly there

80 out of 100, grade B: nearly there. The missing 20 points are spread across Discovery and Conformance and Capabilities. One spec break on the status page isn't counted in the score.

Discovery 90Conformance 86Capabilities 62release 2026-08-25

UCP Score 80/100 grade B · nearly there

Points missing 20 Discovery, Conformance, Capabilities Fixes 4 raise the score Spec breaks 1 not in the score

How the score is made

three areas, weighted

Discovery 30%

Can a UCP agent find and read the profile: HTTPS, an answer at /.well-known/ucp, robots.txt allowing it, and five files outside UCP (llms.txt, sitemap, Open Graph, Organization schema, viewport).

90−3 pts

Conformance 40%

Does the profile follow the spec: valid against its release (counted three times), a dated release, keys published, few warnings, spec and schema links that resolve.

86−5.6 pts

Capabilities 30%

What an agent can do here: how many capabilities, checkout, at least one service, payment handlers, and services that answer our check.

62−11.4 pts

A85–100Ready for UCP agents

B70–84Nearly there

C50–69Partly ready

D30–49Hard for UCP agents

F0–29Not ready

Raise the score

fixes that move the number

part of +6

1Fix broken spec or schema URLs

One or more spec/schema URLs declared in the profile 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 profile setup. See the Full Check Breakdown for the specific URLs that failed.

Conformance · effort low

part of +3

2Publish Organization schema (JSON-LD) on the homepage

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

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.

Discovery · effort medium

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

Drop into <head> or end of <body>. Use OnlineStore (more specific) when the entire site is an ecommerce store; Organization is the generic fallback.

part of +3

3Add Open Graph meta tags to the homepage

OG tags missing or incomplete on your homepage.

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.

Discovery · effort low

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

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

part of +6

4Cryptographic message signing is not yet enabled

Your UCP profile lists no public keys, so cryptographic message signing is not yet enabled for this store. HTTPS already confirms your store's identity; signing adds a further layer for checkout, payment and webhook messages.

The UCP spec recommends signing checkout completion and payment responses, and requires it for webhooks. A store that sends order updates by webhook needs keys; others can add them later.

Conformance · effort medium

{
  "keys": [
    {
      "kty": "EC",
      "crv": "P-256",
      "x": "<base64url x>",
      "y": "<base64url y>",
      "kid": "store-2026-10",
      "use": "sig",
      "alg": "ES256"
    }
  ],
  "ucp": { ... }
}

Create a P-256 (ES256) key pair: ES256 is the one algorithm every UCP agent must be able to check. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, with its own "kid", and keep the private key on your server. The spec recommends a new key every 90 days: publish the new one next to the old, sign with it, and remove the old key a week later.

Every check

10 passed · 8 to fix

Agent Discovery · 6 of 8

6 OK

HTTPS, UCP profile reachable, AI bot access, llms.txt, sitemap.xml, Mobile viewport metaShow

HTTPS · Profile URL uses https://
UCP profile reachable · HTTP 200
AI bot access · robots.txt allows /.well-known/ucp
llms.txt · Found at /llms.txt
sitemap.xml · Found at /sitemap.xml
Mobile viewport meta · <meta name="viewport"> present

Problem

Open Graph tags

Missing or incomplete on homepage. Fix 3 above.

Discovery

Problem

Organization schema (JSON-LD)

Missing or incomplete on homepage. Fix 2 above.

Discovery

UCP Conformance · 2 of 5

2 OK

Profile passes schema validation, Protocol version present and well-formedShow

Profile passes schema validation · No structural errors
Protocol version present and well-formed · Version: 2026-08-25

To fix

Public keys published

No keys list at the top level of the profile. Fix 4 above.

Conformance

To fix

No validation warnings

1 warning.

Conformance

To fix

Spec & schema URLs resolve (17)

Did not resolve (4 of 17): https://olaclick.com/ucp/schemas/com.olaclick.common.location.services.json, https://olaclick.com/ucp/schemas/com.olaclick.marked_location.json, https://olaclick.com/ucp/schemas/com.olaclick.lab.modifiers.json, https://olaclick.com/ucp/schemas/com.olaclick.shopping.store_link.json.

Conformance

Capability Coverage · 2 of 5

2 OK

Transports declared, MCP transport reachableShow

Transports declared · MCP
MCP transport reachable · tools/list returned a JSON-RPC response in 128ms

To fix

Capabilities declared

2 of 6 capability families detected: Order Management, Catalog. A family counts once however many namespaces or extensions declare it.

Capabilities

Problem

Checkout capability

No checkout capability.

Capabilities

To fix

Payment handlers

Empty array: checkout-link redirect strategy.

Capabilities

Not in the score, but worth fixing first

spec breaks

To fix

The profile has no ETag or Last-Modified header

Spec level: SHOULD.

on the status page

The score measures what the profile declares across the three areas above. These break a rule in the spec that agents follow, so they can stop an agent before the score matters.