Lattis

Create a dedicated 'API Limits & Quotas' documentation page at lattis.dev/docs that specifies: (1) requests-per-minute/hour limits per API key or tier, (2) whether limits vary by free vs paid plans, (3) burst allowance policies, (4) bulk/batch endpoint availability for scoring multiple sites, and (5) any throttling behavior for high-volume use cases like 200+ client site dashboards.

Add documentation covering webhook/notification integrations: whether Slack webhooks are supported, if a Zapier integration exists, and how users can configure custom webhook URLs for score change notifications.

Create a dedicated changelog or release notes page that documents scoring methodology updates, model version changes, and their effective dates so buyers can correlate score shifts with Lattis releases rather than debugging their own code.

Add technical documentation explaining the crawler architecture: whether JavaScript is executed, what rendering engine is used (if any), and specific timeouts for dynamic content. This is critical for buyers with client-side rendered documentation to understand if they need SSR/prerendering.

Add a dedicated MCP protocol specification page or section to docs.lattis.dev that explicitly states: (1) which MCP protocol version(s) are supported, (2) whether the 2025-03-26 spec is targeted or if both versions are supported, and (3) streaming capabilities (HTTP SSE vs non-streaming JSON-RPC). Consider adding this to the server-card.json or as a /.well-known/mcp/metadata.json endpoint for programmatic discovery.

Create documentation or an FAQ section explaining how users can dispute or annotate specific findings in their reports, including whether there's a way to mark findings as false positives, add explanatory notes for accessibility implementations like aria-label attributes, or prevent specific findings from recurring in future scans.

Create a dedicated privacy policy, data retention policy, or security/trust page that specifies retention periods for crawled page content, generated embeddings, and user email addresses, plus documents any self-service deletion or data export capabilities.

Create a dedicated methodology or FAQ page explaining how the AI Visibility Score is calculated, including the specific weightings of sub-components (crawlability, semantic structure, etc.) and whether the final score is a weighted sum or simple average.

Add a dedicated section with benchmarked percentage reductions for common site types (Next.js marketing sites, docs sites, e-commerce), including methodology. The current 'characteristic, not measured' disclaimer undermines buyer confidence in the 97.5% figure.

Add explicit documentation clarifying: (1) whether llms.txt is required or recommended for scoring, (2) how robots.txt relates to llms.txt (separate, complementary, or alternative), and (3) what constitutes minimum viable implementation for users who want to maximize their score with least effort.

Clarify whether there's a subscription monitoring tier with scheduled re-crawls (daily/weekly) or if all re-crawls are strictly per-crawl $5 charges. If scheduled re-crawls are only 'coming' as stated in chunk [8], make this explicit on the pricing page.

Add explicit documentation clarifying whether the hosted MCP server supports triggering new crawls (lattis_analyze or similar) and retrieving historical score data, or confirm it is read-only current data only.

Create a dedicated pricing page or FAQ entry that explicitly addresses: (1) whether sites over 5,000 pages are supported, (2) if there are any plans for subscription-based ongoing monitoring for large sites, and (3) how customers with 50,000+ page sites should think about coverage (multiple crawls, enterprise options, etc.). Currently the 'no subscription' messaging conflicts with buyer expectations for ongoing monitoring at scale.

Create a documentation page or FAQ entry that explicitly explains how the 'industry average' benchmark is calculated (global index vs. category-scoped), and whether users can filter benchmarks by company size, category, or other dimensions.