What does it mean that sandbox.pactmode.com is verified for UCP?

It means sandbox.pactmode.com 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 sandbox.pactmode.com 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 sandbox.pactmode.com use for UCP?

Our detection identifies sandbox.pactmode.com 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 sandbox.pactmode.com generated?

Our crawler fetches sandbox.pactmode.com/.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 16 hours ago.

How often is sandbox.pactmode.com 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 sandbox.pactmode.com

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

✓Verified

A86/100

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

/ 100

UCP Conformance Score

sandbox.pactmode.com is conforming and ready for agent discovery and checkout.

Agent Discovery100

UCP Conformance98

Capability Coverage55

Biggest blockers

Repair declared transport endpoints

Working

Agent Discovery is solid (100/100).

Blocking

Repair declared transport endpoints — One or more declared transport endpoints did not respond when probed.

Start Here

Repair declared transport endpoints → Fix broken spec or schema URLs

Top Priorities

Repair declared transport endpoints

One or more declared transport endpoints did not respond when probed.

High impact Medium effort

Fix broken spec or schema URLs

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

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

High impact, high effort

Repair declared transport endpoints

Incremental Gains(1)

Medium impact & effort

Fix broken spec or schema URLs

Consider Later(0)

Lower priority

No items

How you compare on Custom

Response time benchmarked against 104 Customs we monitor.

fastCustom median 300msslow

Your store

128ms

Custom percentile

Top quartile

Faster than 81% of Custom stores

Cohort range

138–586ms

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.

Repair declared transport endpoints

High impact Medium effort

One or more declared transport endpoints did not respond when probed.

Why it matters

A manifest that declares transports without working endpoints is the worst kind of broken — it looks perfect to static validators but agents hit a dead end the moment they try to use the capability. Connection refused, DNS failure, TLS errors, and 5xx responses all fall here. See the Full Check Breakdown below for the specific endpoints that failed.

UCP_PROBE_TRANSPORT_FAILED

Fix broken spec or schema URLs

Medium impact Low effort

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

Full Check Breakdown

Every signal we evaluate, grouped by category.

Functional probes ran 16 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 Conformance4/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.

No outstanding validation issues

Why it matters
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Spec & schema URLs resolve (4)Core

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

Resolved with an unexpected content-type: https://ucpchecker.com/methodology#pricing

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

What operations can agents actually perform?

Capabilities declaredCore

Number of agent-readable capabilities under ucp.capabilities.

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

No checkout capability

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.

MCP, 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.

1 handler 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.
MCP transport reachableInterop

Live reachability check against https://ucpchecker.com/mcp.

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

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.
REST transport reachableInterop

Live reachability check against https://ucpchecker.com/api/v1/check.

Host responded with HTTP 405 — 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.

/llms.txt content

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

5.3 KBc9e4570729fabb7a

mentions UCPdeclares attribution

# UCP Checker

> The independent standard for agentic commerce validation — the system of record for protocol adoption, observed continuously since day zero. Check any domain for UCP support, find the verified stores that sell what you need, search their live catalogues, and get each store's own endpoint to buy from — all programmatically.

UCP Checker validates, observes and scores stores that implement the Universal Commerce Protocol (UCP). UCP is a machine-readable manifest at `/.well-known/ucp` that exposes commerce capabilities to AI agents. Everything here is read-only: UCP Checker resolves stores and measures them, and never creates carts, checks out or takes payment. Once an agent has chosen a store, it transacts with that store's own endpoint.

## Agent discovery (ARD)

UCP Checker is an Agentic Resource Discovery (ARD v0.91) discovery service for the verified UCP storefronts in its census — the commerce Agent Finder:

- Capability manifest: https://ucpchecker.com/.well-known/ard.json (also served at the predecessor path, https://ucpchecker.com/.well-known/ai-catalog.json)
- Search (POST, JSON `{"query":{"text":"..."}}`): https://ucpchecker.com/ard/search
- Facets (POST): https://ucpchecker.com/ard/explore · Browse (GET): https://ucpchecker.com/ard/agents
- MCP server card: https://ucpchecker.com/.well-known/mcp/server-card.json
- Agent skills: https://ucpchecker.com/.well-known/agent-skills/index.json (`ucp-checker`, `ucp-agent-ready`)
- CLI: `npx ucp-check <domain>` — https://www.npmjs.com/package/ucp-check (source: https://github.com/ucpchecker/ucp-check)

Every entry is a verified, publicly listed storefront, labelled with the evidence we hold (`transactable`, `catalogued`, `resolvable` or `declared`). Search ranks lexically: rarer query words count for more, and stores below a relevance floor are not returned, so an empty result means no strong match. A query reaches its first 50 results. `score` on search results is relevance only; the UCP score is in `metadata.ucpScore`. Errors carry the spec's `errorCode` and `message`. Full reference: https://ucpchecker.com/docs#post-ard-search

## MCP Server

UCP Checker exposes a read-only Model Context Protocol (MCP) server for AI agents:

- Endpoint: https://ucpchecker.com/mcp
- Transport: HTTP (Streamable HTTP)
- Authentication: none required; signed (RFC 9421) and token callers get higher rate limits
- Schema: https://ucpchecker.com/.well-known/mcp.json
- Configuration: https://ucpchecker.com/.well-known/mcp-config
- Listed on: the official MCP Registry (`com.ucpchecker/ucp-checker`) and Smithery (https://smithery.ai/servers/ucpchecker/ucp-checker)

### Tools

- `check-domain` — Is a domain agent-ready? Returns UCP status, manifest version, capabilities, latency and AI bot access policies, as observed.
- `list-stores` — List verified UCP storefronts across every platform, best-evidenced first; filterable by platform.
- `list-categories` — Store categories with counts, for the deeply audited subset of verified stores (a way to browse, not the whole index).
- `search-all` — Search products across the verified stores whose observed catalogue matches the query; returns results grouped by store. When nothing matches well enough it answers "No strong match" instead of searching unrelated stores.
- `search-catalog` — Search one store's live product catalogue; returns titles, prices, variants and images.
- `get-product-details` — Full declared detail for one product, including variant IDs.
- `search-policies` — A store's return, shipping, refund, privacy and terms policies.
- `discover-store` — Connect to a store's own MCP endpoint and list the tools it exposes.

### Resolution flow

1. `search-all` (or `list-stores`) — which verified stores match
2. `search-catalog` → `get-product-details` — find the product and its variant
3. `check-domain` and `search-policies` — confirm the store's observed state and its policies
4. `discover-store` — see what the store itself offers, then buy through the store's own endpoint

A store missing from the index, or returning `not_detected`, has not been observed by us — it is not barred to you.

## REST API

- `POST /api/v1/check` — Force a fresh UCP check on a domain
- `GET /api/v1/status/{domain}` — Latest observed status for a domain
- `GET /api/v1/score-model` and `GET /api/v1/checks` — The score model and the check catalogue
- `GET /api/v1/schema` — JSON Schema for the API
- CLI over the API: `npx ucp-check <domain>` — exit 0 verified · 1 not verified · 2 usage · 3 API unreachable; `--cached`, `--json`, `--quiet`
- Reference: https://ucpchecker.com/docs

## Discovery

- UCP manifest: https://ucpchecker.com/.well-known/ucp
- ARD manifest: https://ucpchecker.com/.well-known/ard.json
- MCP schema: https://ucpchecker.com/.well-known/mcp.json

## RSS Feeds

- Blog: https://ucpchecker.com/rss/blog.xml
- UCP Adoption & Stability Stats: https://ucpchecker.com/rss/stats.xml

## Links

- Website: https://ucpchecker.com
- API & MCP docs: https://ucpchecker.com/docs
- Directory: https://ucpchecker.com/directory
- Leaderboard: https://ucpchecker.com/leaderboard
- Stats: https://ucpchecker.com/stats
- Methodology: https://ucpchecker.com/methodology
- CLI (npm): https://www.npmjs.com/package/ucp-check
- Blog: https://ucpchecker.com/blog
- UCP Playground: https://ucpplayground.com

View source ↗

Capabilities Detected

UCP capabilities supported by this endpoint
Com Ucpchecker Router ✓ Bound	2026-08-25
Com Ucpchecker Compare ✓ Bound	2026-08-25
Com Ucpchecker Bulk Check ✓ Bound	2026-08-25
Com Ucpchecker Domain Check ✓ Bound	2026-08-25

Technical Vitals

Technical details for this UCP endpoint
UCP Status	Verified
Endpoint	https://sandbox.pactmode.com/.well-known/ucp
HTTP Status	200
UCP Version	2026-08-25
Transports	MCP, REST
Last Observed	2026-09-17T23:04:21+00:00
Last Full Index	Sep 17, 2026 11:04 PM 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 sandbox.pactmode.com](https://ucpchecker.com/score/sandbox.pactmode.com/badge.svg)](https://ucpchecker.com/score/sandbox.pactmode.com)

HTML

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

New · Early access open

Is sandbox.pactmode.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 sandbox.pactmode.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.