What does it mean that 146.59.63.162.sslip.io is verified for UCP?

It means 146.59.63.162.sslip.io publishes a valid UCP manifest at /.well-known/ucp, the manifest passes schema validation against 2026-08-25, and AI agents can discover its commerce capabilities without needing to scrape HTML. In plain terms: agents can shop here reliably.

Can I trust 146.59.63.162.sslip.io for AI agent purchases?

Verification means the store is technically ready — payment handlers declared, transports reachable, schema valid. It doesn't grade business reputation or fulfilment quality. For trust on the commerce side itself, check the store's own reviews. For trust on the agent integration side, this page is the source of truth.

What platform does 146.59.63.162.sslip.io use for UCP?

Our detection identifies 146.59.63.162.sslip.io as running on Custom. Many large UCP-verified stores use Shopify, BigCommerce, or custom stacks built on the open spec. The transport list above shows the exact mechanism (REST, MCP, A2A, Embedded) the manifest declares.

How was this UCP report for 146.59.63.162.sslip.io generated?

Our crawler fetches 146.59.63.162.sslip.io/.well-known/ucp directly, parses the manifest against the official UCP JSON schema, checks robots.txt for AI bot policies, and runs payment-handler validation. No manual review, no opinions — just what the manifest actually says. The check ran 3 hours ago.

How often is 146.59.63.162.sslip.io re-checked?

Every domain in our directory is re-crawled at least every 24 hours. You can also trigger a fresh check from this page at any time, or subscribe to alerts to get notified the moment the status changes — that's how we built the only continuously updated UCP directory on the internet.

Why does this status matter?

Universal Commerce Protocol is the standard AI shopping agents (ChatGPT, Claude, Gemini, Apple Intelligence) use to discover what a store sells, how to add items to a cart, and how to check out. If a store isn't UCP-verified, agents can still scrape it — but they'll be slower, less reliable, and far more likely to fail at checkout. UCP turns a guess into a guarantee.

Back to status

UCP Score

UCP Score for 146.59.63.162.sslip.io

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

✓Verified

A90/100

Analyzed Sep 17, 2026 · 2 recommendations ·Custom · v2026-08-25 latest

/ 100

UCP Conformance Score

146.59.63.162.sslip.io is conforming and ready for agent discovery and checkout.

Agent Discovery100

UCP Conformance77

Capability Coverage97

Working

Agent Discovery is solid (100/100).

Start Here

Fix broken spec or schema URLs → Publish a schema URL for the service

Top Priorities

Fix broken spec or schema URLs

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

Medium impact Low effort

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

Medium impact & effort

Fix broken spec or schema URLs

Consider Later(1)

Lower priority

Publish a schema URL for the service

How you compare on Custom

Response time benchmarked against 106 Customs we monitor.

fastCustom median 342msslow

Your store

345ms

Custom percentile

Below median

Faster than 48% of Custom stores

Cohort range

219–618ms

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 manifest, schemas, or transports.

Recommendations

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

Fix broken spec or schema URLs

Medium impact Low effort ×7

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

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 3 hours ago.

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 Conformance3/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.
Spec 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.

signing_keys present

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.
Validation warnings clearCore

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

Resolves the 7 spec/schema URLs declared across the manifest to confirm agents can fetch each one.

Did not resolve (7 of 7): https://ucp.dev/specs/shopping, https://ucp.dev/specs/checkout, https://ucp.dev/specs/catalog, https://ucp.dev/specs/order, https://ucp.dev/specs/fulfillment, …

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 Coverage5/5 passed

What operations can agents actually perform?

Capabilities declaredCore

Number of agent-readable capabilities under ucp.capabilities.

4 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

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.

2 handlers registered

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://146.59.63.162.sslip.io/ucp/v1.

Reachable in 329ms (HTTP 200)

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.

464 B1d5f4655f3d19a51

mentions UCP

# IdoSell UCP Storefront
> Universal Commerce Protocol (UCP) Agentic Commerce Gateway for IdoSell stores.

## Overview
- Protocol: Universal Commerce Protocol (UCP)
- Spec Version: 2026-08-25
- Discovery Endpoint: https://146.59.63.162.sslip.io/.well-known/ucp
- Capabilities: Catalog search, Product details, Cart, Checkout, Webhooks.

## Endpoints
- Discovery: https://146.59.63.162.sslip.io/.well-known/ucp
- Shopping REST: https://146.59.63.162.sslip.io/ucp/v1

View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Order Management	2026-08-25
Dev Ucp Identity Linking	2026-08-25
Catalog	2026-08-25
Checkout	2026-08-25
Discount	2026-08-25
Fulfillment	2026-08-25
Buyer Consent	2026-08-25

Technical Vitals

Technical details for this UCP endpoint
UCP Status	Verified
Endpoint	https://146.59.63.162.sslip.io/.well-known/ucp
HTTP Status	200
UCP Version	2026-08-25
Transports	REST
Last Observed	2026-09-17T05:48:43+00:00
Last Full Index	Sep 17, 2026 5:48 AM UTC

Embed your UCP Score

Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.

Live preview

Markdown

[![UCP Score for 146.59.63.162.sslip.io](https://ucpchecker.com/score/146.59.63.162.sslip.io/badge.svg)](https://ucpchecker.com/score/146.59.63.162.sslip.io)

HTML

<a href="https://ucpchecker.com/score/146.59.63.162.sslip.io"><img src="https://ucpchecker.com/score/146.59.63.162.sslip.io/badge.svg" alt="UCP Score for 146.59.63.162.sslip.io"></a>

New · Early access open

Is 146.59.63.162.sslip.io 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 146.59.63.162.sslip.io'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.