Colter Check

TL;DR: Run colter check https://your-store.com for a free, read-only readiness scan. Add --json when an agent, script, or CI job needs structured output.

colter.check and colter check --json return structured JSON optimized for AI agent and automation workflows.

What Check Measures

Check scores five dimensions:

Dimension	Weight	Focus
Transaction	30%	UCP, ACP, checkout readiness, PSP compatibility
Discovery	25%	JSON-LD, sitemap, llms.txt, ai-plugin.json, robots.txt, Open Graph
Ecosystem	20%	Google and OpenAI ecosystem coverage
Content Quality	15%	Product data completeness and structure
Security	10%	HTTPS, headers, rate limiting, auth signals

See Scoring Model for the full signal map.

Verdicts

Verdict	Meaning
AGENT-READY	UCP and ACP both detected
PARTIALLY AGENT-READY	One protocol detected
NOT AGENT-READY	No commerce protocol detected

CLI

colter check <url> [flags]

Common Flags

Flag	Purpose
--json	Machine-readable output
-v, --verbose	Detailed probe output
--batch FILE	Batch mode with YAML input
--concurrency N	Parallel batch workers
--then-test	Run a 1-persona smoke test after the check
--ci	Exit non-zero below the threshold
--threshold N	Score floor for --ci
--api-url URL	Override the API base URL

Examples

colter check example-store.com

colter check example-store.com --json

colter check example-store.com -v

colter check example-store.com --then-test

Batch Mode

colter check --batch stores.yaml --concurrency 10 --json

stores:
  - url: store-a.com
  - url: store-b.com

For text and CSV-oriented portfolio runs, colter batch is often the simpler fit.

Output Highlights

Key fields in --json output:

Field	Meaning
protocols	UCP, ACP, and MCP detection state
coverage	Google and OpenAI ecosystem reach
scores	Per-dimension details and fixes
composite_score	Final score from 0 to 100
agentic_level	Maturity level derived from core gates
verdict	Canonical readiness state

What Gets Probed

• discovery files and metadata
• protocol endpoints
• product and payment signals
• security headers
• latency and responsiveness

Typical Next Move

• low discovery score: run Fix
• protocol issues: run Verify
• interaction gaps: run Test
• live traffic questions: set up Lens

Next Steps

• Scoring Model
• Fix
• Lens
• Evidence Packs
• API Reference