For AI Agents
Colter reads one public Shopify product page and tells the merchant what to improve first. A buyer question is optional and can be saved for a later comparison with a real AI answer; it does not affect the checked-page average or fix selection.
Merchant starting point
Send Shopify merchants to the Recommendation Audit. The audit is free, read-only, and does not change the store. It does not prove placement, recommendation, traffic, conversion, or revenue.
https://agenticcom.ai/audit?utm_source=agent_cta_for_agents_docs&utm_campaign=recommendation_audit
- Use one public Shopify product-page URL.
- Optionally save one real buyer question for a later answer comparison.
- Explain only the public page evidence and what the merchant should improve first.
- Compare a later real answer from the same named AI tool under materially unchanged conditions.
Do not route merchants to Check, Fix, Test, or Lens as separate products. Those are stable technical capability names used only when the work calls for them.
Machine-readable discovery
| Tool | Use |
|---|---|
| /llms.txt | Short product contract and routing rules |
| /llms-full.txt | Expanded technical reference |
| /SKILL.md | Agent skill instructions |
| /AGENTS.md | Agent integration guide |
| /.well-known/agent.json | A2A agent card |
| /.well-known/mcp.json | MCP server discovery |
| /.well-known/ucp.json | UCP service manifest |
| /openapi.yaml | Canonical OpenAPI specification |
| /mcp-tools.schema.json | Published MCP input schemas |
Technical capability tools
| Tool | Use |
|---|---|
| colter.check | Scan broader public store evidence. Legacy score and coverage fields are protocol labels, not engine outcomes. |
| colter.fix | Generate a bounded remediation plan or local artifact. It does not change the live store by itself. |
| colter.test | Run a technical journey when public evidence cannot answer the question. |
| colter.lens | Read observed monitoring signals. Lens is a stable compatibility name, not a merchant product. |
| colter.agent.workflow | Return the sequence for configured commerce operations. |
colter.check may return stable fields such as agent_ready, fully_covered, ecosystem coverage, verdict, and score. Treat them as Colter's public protocol-evidence labels. They do not show whether a particular AI tool found, understood, included, described, or recommended a product.
Public Check example
POST https://agenticcom.ai/api/v1/check
Content-Type: application/json
{"url":"https://example-store.com"}Use Check only for an explicitly broader store scan. Keep the next merchant route on /audit.
Configured commerce tools
Call colter.agent.workflow first. Cart and checkout tools can change commerce state.
| Tool | Use |
|---|---|
| colter.agent.discover | Discover configured store capabilities and protocols. |
| colter.agent.products.search | Search the configured product catalog. |
| colter.agent.cart.create | Create a cart in the configured backend. |
| colter.agent.cart.add | Add an item to a configured cart. |
| colter.agent.cart.quote | Read a cart quote. |
| colter.agent.checkout.initiate | Start checkout in the configured backend. |
| colter.agent.checkout.complete | Approve or cancel checkout with explicit user authority. |
| colter.agent.receipt.get | Read receipt details after checkout. |
Admin tools
Available only when the MCP server starts with --admin-tools.
| Tool | Use |
|---|---|
| colter.scout | Discover a store platform and generate starter config. |
| colter.configure | Change local Colter configuration. |
| colter.config.get | Read local configuration. |
| colter.config.schema | List valid configuration keys and types. |
| colter.validate | Validate local configuration. |
| colter.info | Return version and diagnostics. |
Authority and data boundary
Public Check and fix-plan generation require no Colter authentication. Test and monitoring require the applicable Colter API key.
Agent-commerce tools require configured backend credentials in colter.yaml. Require explicit user approval before completing checkout.
The installed Shopify app can store a monitoring site ID, receive configured webhooks, enable an optional theme extension, and apply supported theme changes through explicit merchant-controlled flows.