UCP Commerce Profile Monitor - Capabilities & Changes

Track merchant commerce declarations

Keep an inventory of the UCP interfaces your merchant or partner watchlist advertises. Collect public protocol versions, capability names and service endpoints, then compare saved observations before updating an integration plan or client report.

One result is one merchant-origin observation. The Actor reads the public /.well-known/ucp discovery profile. It reports declarations, not certification, compatibility testing or successful checkout, and never invokes advertised services.

Open in Console · First run · Output preview · Saved comparisons · Pricing

Try one merchant

Copy this input into Console's JSON editor for a single-domain check. No API key, login or proxy subscription is required.

{
  "merchantUrls": [
    "https://www.brooklinen.com"
  ],
  "maxResults": 1
}

Open Saved observations for the row and Readable run report for the overview. Coverage and stop reasons opens SUMMARY. A parsed HTTP 200 profile is present; an actual HTTP 404/410 is a billable absent observation. Blocked requests, network failures and malformed payloads produce errors without paid result rows.

Replace the sample with a public merchant root. Bare domains are treated as HTTPS; an exact discovery URL is also accepted. Product pages, query strings, authenticated URLs, localhost and private networks are rejected.

Output preview

Integration review	Fields	Meaning
Merchant and discovery path	merchantUrl, profileUrl, finalProfileUrl	Normalized requested origin, requested profile and final allowed destination
Profile presence	profileStatus, httpStatus	present for a parsed 200 profile; absent only for an actual 404/410
Advertised version	protocolVersion, supportedVersions	Current protocol and older version labels declared by the profile
Declared services	services	Names, versions, transports and public endpoints
Declared capabilities	capabilities	Names, versions, spec/schema references and extension relationships
Handler and key identifiers	paymentHandlers, signingKeyIds	Handler names, versions and optional IDs; key IDs when published
Saved changes	comparisonStatus, changedFields, previous, previousObservedAt	Field differences and prior observation
Observation time	observedAt	Retrieval time, not a merchant deployment timestamp

Protocol version is omitted for absence; signing-key IDs are omitted when not published. JSON preserves nested declarations; CSV supports a summary inventory. Payment configuration, capability configuration and public-key material are omitted. A key-material change that keeps the same ID is outside the comparison.

Review three retail profiles

{
  "merchantUrls": [
    "https://www.pier1.com",
    "https://www.allbirds.com",
    "https://www.brooklinen.com"
  ],
  "maxResults": 3
}

Each successfully observed origin can produce one row. Empty input or an empty merchant list uses these three demo merchants. Explicit URLs replace them. A result cap is an upper bound, not a promise of that many successful observations.

Save a baseline, then compare

{
  "merchantUrls": [
    "https://www.pier1.com",
    "https://www.allbirds.com"
  ],
  "maxResults": 2,
  "comparePrevious": true,
  "snapshotName": "retail-capabilities"
}

1. Run once to save new observations. Review their declaration fields and source coverage.
2. Repeat with the same snapshotName. Rows become changed or unchanged, carrying previous values and previousObservedAt.
3. Add onlyChanges: true to skip unchanged observations. It also enables comparison. A healthy repeat can save zero rows and leaves the previous observation timestamp unchanged.
4. For a client inventory in Sheets, Make or n8n, inspect the completed run's SUMMARY and dataset, then upsert by merchantUrl. Retain the run ID to replay delivery and deduplicate by run ID plus merchant origin.

History is scoped per normalized origin in maydit-ucp-profile-<snapshotName>. Failed requests, rejected payloads, failed dataset writes and zero-row spending stops preserve the baseline. Successfully saved observations can advance independently even when another merchant fails.

Run the same snapshot name sequentially. A precommit check detects an already changed snapshot; it is not an atomic compare-and-swap lock. Check historyUpdated, failedSources and baselineSkippedOnDeadline before relying on the baseline. Ordering alone and observation timestamps do not create changes. You configure schedules and downstream connections.

Input guide

Input	Purpose	Default
merchantUrls	Up to 100 public roots, deduplicated by origin	Three example merchants
maxResults	Saved observations, from 1 to 100	25
comparePrevious	Enable named history	false
onlyChanges	Skip unchanged rows; enables comparison	false
snapshotName	1–40 letters, digits, underscores or hyphens; starts with a letter or digit	default
maxRunSeconds	Own budget, from 30 to 3,600 seconds	240

The Actor reserves 25 seconds before the platform deadline. Set an Apify maximum total charge alongside the result cap.

Coverage and interpretation

• Discovery only: fetches robots.txt and the fixed profile path. No product crawl, MCP execution, cart creation, negotiation, linked-schema fetch or payment test. It does not inspect llms.txt, ACP or search visibility.
• Declared capability: advertised versions and endpoints do not prove authentication, compatibility, payment acceptance or runtime availability for your application.
• Observed absence: HTTP 404/410 describes the requested path at the time checked. It does not prove a merchant lacks all AI commerce integrations. There are no product-removal or historical-archive claims.
• Supported shapes: current array declarations and earlier service transport maps are supported. Unknown or malformed structures fail explicitly. This is a metadata parser, not a complete UCP schema validator.
• References and redirects: endpoints remain metadata and are never called. References must be public HTTPS URLs without credentials or query parameters. Up to three redirects may lead to another exact public HTTPS profile path. finalProfileUrl exposes the destination; following a redirect does not certify UCP's no-redirect hosting requirement.
• Bounded requests: sequential domains; profiles limited to 1 MiB. 429/5xx responses receive at most two retries within the deadline, respecting Retry-After. Robots exclusions and public-address checks apply to requests and redirects.

Intentional result caps can finish with status ok, with unvisited merchants reported in SUMMARY. Source failures, time exhaustion and spending limits set incomplete coverage and stop flags. An all-failed run fails. Valid unchanged-only output can be empty; consult SUMMARY before drawing a conclusion from zero rows.

Pricing

Base result rate on the FREE tier: $5 per 1,000 saved domain observations, plus the listed Actor Start charge. The Pricing tab is authoritative for your plan's current rates. Confirmed 404/410 absence and saved unchanged rows are billable. Changes-only skips and error summaries create no dataset-item charge; the start charge still applies. Platform usage charges may apply under your plan.

Troubleshooting and sources

If a merchant's public page works but the Actor fails, its profile may be blocked, malformed, oversized or unsupported. Restrictions are reported without bypass. For malformed or overlapping history, choose a new snapshot name and keep named workflows sequential.

Official UCP overview · Shopify developer announcement

This independent tool is not endorsed by UCP, Shopify or the example merchants. Open Issues with the public merchant URL, run ID and expected field. Do not include credentials, customer information or checkout details.