Skip to content

EkLine

EkLine documentation

How to measure what AI assistants and coding agents say and do with your product, and fix what they read.

EkLine is a set of AI agents for developer tool and API companies. They check what ChatGPT and Claude say about your product and whether coding agents like Cursor can build with it, then fix the docs, help center, and marketing pages those agents read, using your code, pull requests, and support tickets. Every change arrives as a pull request or draft your team approves.

  1. Measure. Journeys asks AI assistants the questions your buyers ask, gives coding agents tasks with your product, and checks every answer.
  2. Fix. Docs Agent and Marketing Agent draft changes to the docs, help center articles and marketing posts those agents read.
  3. Approve. Your team reviews each pull request or draft. Nothing merges or publishes without your approval.
  4. Run it again. Run the same journeys again and see what changed.

Read How EkLine works for each step, and what EkLine reads and writes.

Setting EkLine up for your team? Work through Set up your workspace.

Journeys

Ask AI assistants and coding agents what your buyers and developers ask, many times each, and see what they say and do.

Journeys overview

Agents

Give Docs Agent and Marketing Agent context, start work from the editor, GitHub, GitLab, Slack and more, and review what they draft.

Agents overview · Marketing Agent

Docs Reviewer

Check every docs change against your style guide in CI, VS Code, Google Docs or the CLI.

How Docs Reviewer works

AI assistants, answer engines, and crawlers now read your documentation alongside human readers. The guides below apply to any documentation site, whether or not you use EkLine.

Monitor AI traffic

Understand which AI bots read your docs, identify them in your logs, and measure their activity.

Understand AI traffic →

Prepare your docs for AI

Serve Markdown, add an llms.txt file, and control which AI crawlers can access your content.

Browse the guides →

  • llms.txt: start from https://docs.ekline.io/llms.txt, which lists this documentation by section.
  • Markdown: every page has a Markdown version at the same path ending in .md, for example https://docs.ekline.io/agent.md.
  • MCP server: https://ekline.io/api/mcp lets an agent start and follow Docs Agent and Marketing Agent sessions with a personal API key, and search these docs. See MCP clients.

Built on Potluck Docs, our open source template.