# EkLine

> EkLine finds what AI agents get wrong about your product and fixes what they read. It measures what answer engines say about you, traces each answer back to the pages behind it, and opens pull requests that correct them across docs, help center, and marketing.

Buyers ask Claude, ChatGPT, Gemini, or Perplexity what to use, then ask Cursor, Claude Code, Codex, or GitHub Copilot to build with it. EkLine works on both halves of that. It checks what your team and your coding agents write before it merges, and it drafts what nobody has written yet from the changes you ship. Every change arrives as a pull request your team approves; EkLine never publishes on its own.

## Docs Agent

Reads your merged changes, works out which pages they touched, and drafts the updates as a pull request. Also generates documentation from a codebase, a video, or sources you already have.

- [Overview](https://docs.ekline.io/agent/): what the Docs Agent does and how a run works
- [Getting started](https://docs.ekline.io/agent/getting-started/): connect a repository and open a first pull request
- [Create documentation](https://docs.ekline.io/agent/create/): generate guides and reference pages from a codebase or a video
- [Generate an API reference](https://docs.ekline.io/agent/generate-api-reference/): build reference pages from an OpenAPI spec
- [Write release notes](https://docs.ekline.io/agent/release-notes/): turn merged pull requests into a release note
- [Refresh documentation screenshots](https://docs.ekline.io/agent/refresh-doc-screenshots/): recapture screenshots when the UI changes
- [Prevent documentation drift](https://docs.ekline.io/agent/prevent-documentation-drift/): catch pages that a shipped change made wrong
- [Manage the knowledge base](https://docs.ekline.io/agent/manage-knowledge-base/): the sources the agent reads before it writes
- [Agent integrations](https://docs.ekline.io/agent/integrations/): the tools the Docs Agent connects to

## Docs Reviewer

Checks documentation in CI before it merges, including the documentation coding agents write. Comments on the pull request.

- [Overview](https://docs.ekline.io/reviewer/overview/): what gets checked and what a finding looks like
- [Quickstart](https://docs.ekline.io/reviewer/quickstart/): every way to run the reviewer
- [GitHub Action](https://docs.ekline.io/reviewer/quickstart/github-action/): run the reviewer on pull requests
- [CLI](https://docs.ekline.io/reviewer/quickstart/cli/): run the reviewer locally or in any CI system
- [VS Code extension](https://docs.ekline.io/reviewer/quickstart/vscode/): findings inline as you write
- [Google Docs add-on](https://docs.ekline.io/reviewer/quickstart/google-docs/): the same checks on Google Docs
- [Style guides](https://docs.ekline.io/reviewer/configuration/style-guides/): bring your own style guide and terminology
- [Automatic pull request review](https://docs.ekline.io/agent/automatic-pr-review/): review every documentation change without asking

## Integrations

- [All integrations](https://ekline.io/integrations): source control and CI (GitHub, GitLab, Bitbucket); coding agents and editors (Claude, Cursor, VS Code); documentation frameworks (Astro, Docusaurus, Fern, Gatsby JS, GitBook, Mintlify, ReadMe, Redocly); content and support (Confluence, Google Drive, Notion, Pylon, Slack); issue tracking and analytics (Jira, Linear, PostHog)
- [GitHub](https://docs.ekline.io/reviewer/integrations/github-integration/): review and enforce documentation standards in pull requests
- [GitLab](https://docs.ekline.io/reviewer/integrations/gitlab-integration/): the same checks on merge requests
- [Bitbucket](https://docs.ekline.io/reviewer/integrations/bitbucket-integration/): the same checks on Bitbucket pull requests

## Security and privacy

- [Trust center](https://ekline.io/trust-center): isolated per customer; sandboxed runs with scoped credentials; SOC 2 compliant with no training on your data; your content stays yours, in your stack; every change ships as a pull request your team approves

## Company

- [Website](https://ekline.io): what EkLine does, in full
- [Pricing](https://ekline.io/pricing): plans and what each one includes
- [Customers](https://ekline.io/case-study): case studies with numbers
- [Documentation](https://docs.ekline.io): the full product documentation site
- [Blog](https://ekline.io/blog): writing on documentation, GEO, and AI agents

## Optional

- [Documentation index for LLMs](https://docs.ekline.io/llms.txt): the docs site's own llms.txt, generated from the same source as the pages
- [Full documentation for LLMs](https://docs.ekline.io/llms-full.txt): every documentation page inlined — large, skip when context is tight
- [Abridged documentation for LLMs](https://docs.ekline.io/llms-small.txt): the same, with non-essential content removed