Frequently Asked Questions

The Zeodyn Score™ is a composite metric from 1 to 100 that measures how ready your website is for AI agent commerce. It evaluates six dimensions of the Agent Commerce Stack™ covering discovery, structured data, commerce data, protocol support, security, and performance.

The Zeodyn Score™ uses a weighted geometric mean to aggregate six dimension scores. Unlike a simple average, geometric aggregation ensures that weakness in any single dimension pulls the overall score down — you cannot compensate for a critical gap in one area with strength in another. Fail gates within each dimension cap scores when fundamental requirements are not met. Full details are on the Methodology page.

We recommend scanning after every significant deployment or content change. On paid plans, watched sites are automatically re-scanned weekly, so you always have current data without manual effort.

A low score typically indicates gaps in structured data, missing agent commerce protocols, or security issues. Check the dimension breakdown in your scan results to see which areas need attention. The recommendations section provides specific, actionable steps ranked by impact. Focus on high-priority items first — particularly any that trigger fail gates.

Fail gates are critical sub-checks within each dimension. When a fail gate triggers (e.g. no HTTPS, robots.txt blocks all AI agents), the dimension score is capped regardless of how well other sub-checks perform. This non-compensatory mechanism ensures that fundamental requirements cannot be bypassed. Fixing a fail gate often produces the largest score improvement.

Yes. Every scan includes recommendations ranked by priority and impact. Implementing high-priority recommendations — such as adding JSON-LD structured data, enabling agent-friendly robots.txt rules, or adopting commerce protocols — typically produces measurable score improvements. The Zeodyn Score™ is designed so that improving your score means genuinely becoming more ready for AI agent commerce.

Pro (£19/month) includes unlimited scans, 10 monitored sites with weekly re-scans, trend charts, PDF export, AI-enhanced recommendations, 1,000 API calls/month, and 1 webhook. Growth (£49/month) adds unlimited API calls, batch scanning (up to 500 URLs), team workspaces (up to 5 members), competitive benchmarking, 5 webhooks with all event types, and custom threshold alerts. See the pricing page for the full comparison.

You can cancel your subscription at any time from your account settings. Your paid features remain active until the end of your current billing period. After cancellation, your account reverts to the Free tier.

Yes. Your scan results are private to your account (and your team, if you have a workspace). We do not sell, share, or publish scan data. Scan results are retained for 30 days on the free tier and for the duration of your subscription on paid plans. See our Privacy Policy for full details.

Yes. Zeodyn™ infrastructure is hosted in Azure UK South (London). All scans originate from UK-based servers. This means response times measured in scan results reflect latency from UK data centres.

On Pro and Growth plans, watched sites are automatically re-scanned every seven days. Each re-scan produces a full Zeodyn Score™ with dimension breakdown, and the data is added to your trend charts. If the score changes, you receive an email notification and a webhook event (if configured).

When a watched site’s score changes after a re-scan, Zeodyn sends you an email notification with the old score, new score, and which dimensions changed. On Pro and Growth plans, a score_change webhook is also fired.

Zeodyn publishes machine-readable files to help AI agents understand our platform: /llms.txt, /agent.json, and /openapi.json. These describe our public API and capabilities. Your private scan data is never included in these files and is only accessible through authenticated API calls. Agents can also interact with Zeodyn natively via the MCP server or A2A endpoint.

The MCP server at /api/mcp lets AI agents interact with Zeodyn using structured tool calls over JSON-RPC 2.0. It exposes 8 tools including scan_website, compare_sites, and get_plans. Use it when your agent framework supports MCP natively.

The A2A endpoint at /api/a2a implements Google’s Agent-to-Agent protocol. Your agent sends natural language messages like “Scan https://example.com” and Zeodyn detects the intent, executes the action, and returns structured results. Use it when your agent prefers conversational interaction over structured tool calls.

Use the REST API for traditional programmatic integration (CI/CD, monitoring, scripts). Use MCP if your AI agent framework supports the Model Context Protocol natively. Use A2A if your agent prefers natural language interaction. All three provide access to the same capabilities and require the same API key authentication.