CanAgentUse

CanAgentUse products

WooCommerce PluginPublish UCP discovery and agent-ready commerce signals from WooCommerce without rebuilding checkout.View product Shopify PluginAdd UCP discovery, storefront metadata checks, and controlled cart-to-checkout flows for shopping agents.View product AgentReady CIScan commits and PRs, publish reports, and choose which agent-readiness failures should block merges.View product

CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

UCP ValidatorUCP Playground

MCP Playground

Connect to hosted MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

MCP Playground

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

A2A Playground

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

Agent Website Viewer

Tools / UCP Validator

UCP Validator

Validate a website's Universal Commerce Protocol manifest, discovery endpoint, commerce capabilities, payment handlers, and launch issues.

Limit: 5 validations per 60 minutes.

Manifest

Parses and validates the UCP profile shape.

Capabilities

Maps checkout, catalog, cart, order, and payment support.

Launch checks

Finds blockers, warnings, and next fixes.

What this UCP validator checks

Discovery, conformance, and commerce checks in one report.

Discovery

Fetches the expected /.well-known/ucp endpoint or validates pasted JSON.

Commerce metadata

Extracts services, capabilities, payment handlers, and signing keys.

Deployment

Checks robots access, unsafe metadata, and optional read-only probes.

Universal Commerce Protocol validation

What is the UCP Validator?

The UCP Validator checks the public Universal Commerce Protocol profile that agents look for at /.well-known/ucp. It reads the profile, validates the required commerce metadata, and points out the issues that can stop agents from discovering services, payment handlers, capabilities, or signing keys.

What the validator checks

  • Fetches /.well-known/ucp from the submitted origin or validates pasted profile JSON.
  • Checks that the profile has a top-level ucp object, version data, services, and payment handlers.
  • Reviews capabilities, supported versions, spec URLs, schema URLs, and reverse-domain names.
  • Flags public metadata that should not ship, including private hosts, tokens, raw card data, and private key material.
  • Reports robots.txt and llms.txt signals so teams can see whether agents can reach the profile.

Before publishing UCP support

Use the validator to catch missing services, malformed payment handlers, unsafe URLs, and signing-key mistakes before agents start reading the profile.

After a failed agent checkout test

Run the profile through the validator first. If discovery or capability metadata is wrong, the checkout flow will usually fail later.

During AI commerce readiness work

Keep the UCP profile clear, fetchable, and well described. Search engines and AI systems need machine-readable commerce metadata because a human checkout page is not enough.

UCP Validator vs UCP Playground

Use the UCP Validator when you need to check discovery and profile quality. Use the UCP Playground when the profile is good enough to run catalog, cart, and checkout calls against a connected storefront.