Your page scores 53 out of 100 for sameness against the 2 competitors you named.

Claims only you make, that buyers weigh, and that competitors can’t easily copy.

Territory you spend prominent space on that the set also occupies. Not every line is one to delete — the question is whether it has earned the space, or whether something only you can say should be there instead.

• Commodity · 100%Table stakesHero

  retrieval/search API grounds AI agents

  • “Connect your unstructured data and give your agents accurate, cited context from your knowledge base via API or MCP”
  • “Knowledge retrieval API for AI agents”

  You say this 2 different ways.

  Inkeep and Exa all cover this territory. Buyers may need to hear it, but in your hero it spends the first impression on shared ground.

  This is grouped wrong
  They say

  • Inkeep“Deploy AI teammates that understand your data, product, knowledge, and tools”
  • Exa“The world's data for AI agents”
• Commodity · 100%Table stakesSection

  connects to many data sources out of the box

  • “Pre-built connectors for Web crawls, Zendesk, GitHub, Slack, PDFs, and more”

  Common ground with Inkeep and Exa. Say it if buyers need it — lower on the page, where it is not the thing they read first. Nobody else uses your exact words, but everyone is on the ground. Nobody else makes this exact claim, but everyone occupies the territory — lead with the specific, not the generic.

  This is grouped wrong
  They say

  • Inkeep“Query customer-specific information with Customer Intelligence”
  • Exa“Best-in-class across company search, people search, and code — not just general web queries”
• Commodity · 100%Table stakesSection

  named customers and customer proof points

  • “Trusted by category-defining startups and Fortune 500 enterprises”

  Inkeep and Exa make the same claim. It cannot set you apart, so it should not carry the section.

  This is grouped wrong
  They say

  • Inkeep“Trusted by leading teams”
  • Exa“Join 500,000 developers building AI on top of the world's information”
• Contested · 50%SharpenHero

  access via API, MCP, or SDK components

  • “via API or MCP”

  Inkeep is on this territory too (50% of the set). It narrows the field without winning it — make it specific enough that it cannot be said of them. Nobody else uses your exact words, but everyone is on the ground. Nobody else makes this exact claim, but everyone occupies the territory — lead with the specific, not the generic.

  This is grouped wrong
  They say

  • Inkeep“Open Agent Builder & Developer SDK”
• Contested · 50%SharpenHero

  accurate, cited answers from retrieval

  • “accurate, cited context”

  Shared with Exa. Sharpen it to the thing only you do here, or it reads as a claim any of you could make. Nobody else uses your exact words, but everyone is on the ground. Nobody else makes this exact claim, but everyone occupies the territory — lead with the specific, not the generic.

  This is grouped wrong
  They say

  • Exa“Highest quality search at every latency”
• Contested · 50%SharpenSection

  customer-facing AI agent deflects support work

  • “Support agent: Most support tickets ask something you've already answered”
  • “Documentation agent: Embed an agent in your documentation so users can self-serve”
  • “In-product agent: AI agents embedded directly in your application”

  You say this 3 different ways.

  Shared with Inkeep. Sharpen it to the thing only you do here, or it reads as a claim any of you could make.

  This is grouped wrong
  They say

  • Inkeep“AI assistant trained on documentation, help articles, and other content”
• Contested · 50%SharpenSection

  keeps index fresh with incremental sync

  • “Kapa detects and re-processes only what changed, and updates land in minutes”

  Contested ground: Inkeep claim it as well. The version that wins names a mechanism, a number or a scope that theirs cannot match.

  This is grouped wrong
  They say

  • Inkeep“Keep your knowledge base always up to date”
• Contested · 50%SharpenSection

  managed end-to-end retrieval pipeline

  • “Managed retrieval pipeline: Chunking, embedding, hybrid search, reranking and evals”
  • “Kapa prunes the rest to give agents context that actually matters”

  You say this 2 different ways.

  Exa is on this territory too (50% of the set). It narrows the field without winning it — make it specific enough that it cannot be said of them.

  This is grouped wrong
  They say

  • Exa“Specialized model trained to extract the most relevant excerpts from the web”

Sameness measures how much your claims overlap with the sites compared. It does not measure message quality or whether buyers prefer you.

AI-analyzed: an AI read each page on its own and grouped the claims that say the same thing. No score here was written by a model — every number is computed from those groupings in our own code, with the weights below.

Trusted by