Skip to content

armgit / xerj

Public Imported from GitHub
0

AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.

22.9 KB
Raw Blame
<!DOCTYPE html>
<html lang="en" data-theme="day">
<head>
<!-- ga4:begin — generated by scripts/seo/seo_head.py · do not hand-edit -->
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-Z77ETCDJYL"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'G-Z77ETCDJYL');
</script>
<!-- ga4:end -->
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>XERJ.ai — Case study: semantic analytics in one request</title>
<meta name="description" content="kNN and aggregations in a single POST /_search: a deep-research question over 130 synthetic support conversations. A correctness demo, not a benchmark.">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Big+Shoulders+Display:wght@400;700;800;900&family=Inter:wght@400;500;600;700&family=IBM+Plex+Sans:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500;700&display=swap" rel="stylesheet">
<link rel="icon" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'><rect width='100' height='100' fill='%230b0b0d'/><text x='50' y='68' font-size='60' font-family='Big Shoulders Display,sans-serif' font-weight='900' fill='%23ffc400' text-anchor='middle'>X</text></svg>">
<script src="/theme.js"></script>
<link rel="stylesheet" href="/style.css?v=cs0728">
<style>
  /* page-local: comparison series uses the validated --z-cmp token, not gray */
  .cmp-b .cmp-bar { background: var(--z-cmp); opacity: 1; }
  .cmp-bars-head .cmp-b { color: var(--z-cmp); font-weight: 700; }
  /* page-local: "one response carries" rows */
  .carry { max-width: 720px; margin-top: var(--sp-8); }
  .carry .c-row { display: flex; gap: var(--sp-4); align-items: baseline; padding: 10px 0; border-bottom: 1px solid var(--z-faint); font-family: var(--font-data); font-size: var(--fs-13); letter-spacing: var(--track-label); }
  .carry .c-row:first-child { border-top: 1px solid var(--z-line); }
  .carry .c-n { color: var(--z-accent); font-family: var(--font-mono); }
  .carry .c-what { color: var(--z-ink); }
  .carry .c-det { color: var(--z-mute); margin-left: auto; text-align: right; font-family: var(--font-mono); font-size: var(--fs-11); }
</style>
<!-- seo:begin — generated by scripts/seo/fix_heads.py · do not hand-edit -->
<link rel="canonical" href="https://xerj.org/case-studies/calltree-analytics">
<meta property="og:site_name" content="XERJ.ai">
<meta property="og:type" content="article">
<meta property="og:title" content="XERJ.ai — Case study: semantic analytics in one request">
<meta property="og:description" content="kNN and aggregations in a single POST /_search: a deep-research question over 130 synthetic support conversations. A correctness demo, not a benchmark.">
<meta property="og:url" content="https://xerj.org/case-studies/calltree-analytics">
<meta property="og:image" content="https://xerj.org/og/xerj-card.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="XERJ.ai — the search engine built for AI agents">
<meta property="og:locale" content="en_US">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="XERJ.ai — Case study: semantic analytics in one request">
<meta name="twitter:description" content="kNN and aggregations in a single POST /_search: a deep-research question over 130 synthetic support conversations. A correctness demo, not a benchmark.">
<meta name="twitter:image" content="https://xerj.org/og/xerj-card.png">
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://xerj.org/#organization",
  "name": "XERJ",
  "alternateName": "XERJ.ai",
  "url": "https://xerj.org/",
  "logo": "https://xerj.org/brandbook/xerj-mark.svg",
  "description": "A new way for AI to search for data: one local Rust binary that indexes your code, docs, specs and logs, plus Corpus Hub packs, and returns cited answers.",
  "sameAs": [
    "https://github.com/xerj-org/xerj",
    "https://x.com/xerj_org"
  ]
}
</script>
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "@id": "https://xerj.org/#website",
  "name": "XERJ.ai",
  "url": "https://xerj.org/",
  "inLanguage": "en",
  "publisher": {
    "@id": "https://xerj.org/#organization"
  }
}
</script>
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "XERJ.ai — Case study: semantic analytics in one request",
  "description": "kNN and aggregations in a single POST /_search: a deep-research question over 130 synthetic support conversations. A correctness demo, not a benchmark.",
  "url": "https://xerj.org/case-studies/calltree-analytics",
  "image": "https://xerj.org/og/xerj-card.png",
  "inLanguage": "en",
  "datePublished": "2026-07-28",
  "dateModified": "2026-08-30",
  "author": {
    "@id": "https://xerj.org/#organization"
  },
  "publisher": {
    "@id": "https://xerj.org/#organization"
  },
  "isPartOf": {
    "@id": "https://xerj.org/#website"
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://xerj.org/case-studies/calltree-analytics"
  }
}
</script>
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://xerj.org/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Case studies",
      "item": "https://xerj.org/case-studies"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Semantic analytics in one request"
    }
  ]
}
</script>
<!-- seo:end -->
</head>
<body>

<!-- nav -->
<nav class="nav" aria-label="Primary">
  <a href="/" class="brand">XERJ</a>
  <a href="/product">PRODUCT</a>
  <a href="/use-cases" class="active">USE CASES</a>
  <a href="/answers/">ANSWERS</a>
  <a href="/benchmarks/">BENCHMARKS</a>
  <a href="/blog/">BLOG</a>
  <span class="spacer"></span>
  <a href="/for-agents">FOR AGENTS</a>
  <a href="/docs/">DOCS</a>
  <a href="/playground">DASHBOARDS</a>
  <a href="https://hub.xerj.org" rel="external">HUB</a>
  <a class="nav-stars" href="https://github.com/xerj-org/xerj" rel="external" title="XERJ on GitHub" aria-label="XERJ on GitHub, 14,225 stars"><svg viewBox="0 0 16 16" width="14" height="14" aria-hidden="true"><path d="M8 0C3.58 0 0 3.58 0 8c0 3.54 2.29 6.53 5.47 7.59.4.07.55-.17.55-.38 0-.19-.01-.82-.01-1.49-2.01.37-2.53-.49-2.69-.94-.09-.23-.48-.94-.82-1.13-.28-.15-.68-.52-.01-.53.63-.01 1.08.58 1.23.82.72 1.21 1.87.87 2.33.66.07-.52.28-.87.51-1.07-1.78-.2-3.64-.89-3.64-3.95 0-.87.31-1.59.82-2.15-.08-.2-.36-1.02.08-2.12 0 0 .67-.21 2.2.82.64-.18 1.32-.27 2-.27.68 0 1.36.09 2 .27 1.53-1.04 2.2-.82 2.2-.82.44 1.1.16 1.92.08 2.12.51.56.82 1.27.82 2.15 0 3.07-1.87 3.75-3.65 3.95.29.25.54.73.54 1.48 0 1.07-.01 1.93-.01 2.2 0 .21.15.46.55.38A8.013 8.013 0 0016 8c0-4.42-3.58-8-8-8z"/></svg><span class="nav-stars-n" data-gh-stars="14225">★ 14.2k</span></a>
  <a href="https://x.com/xerj_org" rel="external" title="XERJ on X" style="display:inline-flex;align-items:center"><svg width="15" height="15" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M18.244 2.25h3.308l-7.227 8.26 8.502 11.24H16.17l-5.214-6.817L4.99 21.75H1.68l7.73-8.835L1.254 2.25H8.08l4.713 6.231zm-1.161 17.52h1.833L7.084 4.126H5.117z"/></svg></a>
  <a href="https://discord.com/invite/yetXFusXfs" rel="external" title="XERJ on Discord" style="display:inline-flex;align-items:center"><svg width="15" height="15" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M20.317 4.37a19.79 19.79 0 00-4.885-1.515.074.074 0 00-.079.037c-.21.375-.444.864-.608 1.25a18.27 18.27 0 00-5.487 0 12.64 12.64 0 00-.617-1.25.077.077 0 00-.079-.037A19.74 19.74 0 003.677 4.37a.07.07 0 00-.032.027C.533 9.046-.32 13.58.099 18.057a.082.082 0 00.031.057 19.9 19.9 0 005.993 3.03.078.078 0 00.084-.028c.462-.63.874-1.295 1.226-1.994a.076.076 0 00-.041-.106 13.1 13.1 0 01-1.872-.892.077.077 0 01-.008-.128 10.2 10.2 0 00.372-.292.074.074 0 01.077-.01c3.928 1.793 8.18 1.793 12.062 0a.074.074 0 01.078.01c.12.098.246.198.373.292a.077.077 0 01-.006.127 12.3 12.3 0 01-1.873.892.077.077 0 00-.041.107c.36.698.772 1.362 1.225 1.993a.076.076 0 00.084.028 19.84 19.84 0 006.002-3.03.077.077 0 00.032-.054c.5-5.177-.838-9.674-3.549-13.66a.061.061 0 00-.031-.03zM8.02 15.33c-1.183 0-2.157-1.085-2.157-2.419 0-1.333.956-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.333-.956 2.418-2.157 2.418zm7.975 0c-1.183 0-2.157-1.085-2.157-2.419 0-1.333.955-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.333-.946 2.418-2.157 2.418z"/></svg></a>
  <span class="theme">
    <button type="button" data-theme="day" class="active">DAY</button>
    <span class="dash">·</span>
    <button type="button" data-theme="night">NIGHT</button>
  </span>
</nav>


<nav class="uc-subnav" aria-label="Case studies">
  <a href="/case-studies">ALL CASE STUDIES</a>
  <a href="/case-studies/reference-coding">REFERENCE-CODING</a>
  <a href="/case-studies/xerj-self-audit">RUST SELF-AUDIT</a>
  <a href="/case-studies/wordpress-security-audit">WORDPRESS SECURITY AUDIT</a>
  <a href="/case-studies/calltree-analytics" class="active">SEMANTIC ANALYTICS</a>
  <a href="/case-studies/daily-dev-postgres-cdc">POSTGRES CDC + HYBRID</a>
</nav>

<div class="uc-hero">
  <div class="uc-eyebrow">CASE STUDY · SEMANTIC ANALYTICS</div>
  <h1>DEEP RESEARCH.<br><span class="accent">ONE REQUEST.</span></h1>
  <p class="uc-lead">"Of calls about wifi issues, how many are 2.4GHz vs 5GHz, and what are the key issues?" One question bundles retrieval, aggregation, labeling and evidence — normally an OLAP engine plus a vector store, with ETL between them. In XERJ it is one <code class="inline">POST /_search</code>: slice, breakdown, metrics and evidence come back together.</p>
  <div class="kicker"><span>FOR</span><span class="dash">·</span><span>AI-OVER-SUPPORT TEAMS</span><span class="dash">·</span><span>DATA PLATFORM ENGINEERS</span></div>
</div>

<!-- Hero visual: the architecture collapse -->
<section class="scene-section" style="border-top:0; padding-top:0;">
  <div class="viz-block">
    <div class="kicker"><span>GENERATED CORPUS · NOT A BENCHMARK · 130 SYNTHETIC CONVERSATIONS</span></div>
    <div class="cmp-bars">
      <div class="cmp-bars-head">
        <span></span>
        <span class="cmp-a">XERJ</span>
        <span class="cmp-b">SPLIT STACK</span>
      </div>
      <div class="cmp-bars-row">
        <span class="cmp-label">Requests per question</span>
        <span class="cmp-val cmp-a">
          <span class="cmp-bar" style="width:45%;"></span>
          <span class="cmp-num">1</span>
        </span>
        <span class="cmp-val cmp-b">
          <span class="cmp-bar" style="width:90%;"></span>
          <span class="cmp-num">2</span>
        </span>
      </div>
      <div class="cmp-bars-row">
        <span class="cmp-label">Stores to operate</span>
        <span class="cmp-val cmp-a">
          <span class="cmp-bar" style="width:45%;"></span>
          <span class="cmp-num">1</span>
        </span>
        <span class="cmp-val cmp-b">
          <span class="cmp-bar" style="width:90%;"></span>
          <span class="cmp-num">2</span>
        </span>
      </div>
    </div>
    <div class="kicker" style="margin-top:var(--sp-6);"><span>ONE RESPONSE CARRIES</span></div>
    <div class="carry">
      <div class="c-row"><span class="c-n">01</span><span class="c-what">SEMANTIC SLICE</span><span class="c-det">k=80 nearest conversations</span></div>
      <div class="c-row"><span class="c-n">02</span><span class="c-what">BREAKDOWN</span><span class="c-det">terms buckets: band, key issues</span></div>
      <div class="c-row"><span class="c-n">03</span><span class="c-what">METRICS</span><span class="c-det">csat p50 · handle-time avg, per bucket</span></div>
      <div class="c-row"><span class="c-n">04</span><span class="c-what">EVIDENCE</span><span class="c-det">3 example hits → LLM narrative</span></div>
    </div>
    <p style="margin-top:14px; font-size:12px; letter-spacing:.04em; color:var(--z-mute); font-family:var(--font-data);">SPLIT STACK = OLAP + VECTOR STORE + ETL, OR TWO ROUND TRIPS IN ONE ENGINE · SOURCES IN <a href="https://github.com/xerj-org/xerj/tree/main/docs/case-studies/calltree-analytics" rel="external">docs/case-studies/calltree-analytics &rarr;</a></p>
  </div>
</section>

<div class="pain-solve">
  <div class="pain">
    <h3>THE SPLIT-STACK TAX</h3>
    <ul><li><strong>Two systems before one answer.</strong> An OLAP engine for the columns, a vector store for the embeddings, ETL between them.</li><li><strong>No cross-system join.</strong> The semantic slice lives in one store, the metrics in the other.</li><li><strong>Two round trips even inside one engine.</strong> Run the kNN, ship the ids back to the client, aggregate with a filter.</li><li><strong>Evidence arrives separately.</strong> The example conversations the LLM narrative needs are yet another query.</li></ul>
  </div>
  <div class="solve">
    <h3>THE XERJ ANSWER</h3>
    <ul><li><strong>One index holds everything.</strong> Keyword columns, full text, and the 768-dim vector are fields of the same document.</li><li><strong>Aggregations run on the kNN slice.</strong> rc.6 computes the buckets over the retrieved top-k neighbour set, in-request.</li><li><strong>Exact buckets by design.</strong> An aggs-bearing kNN routes to the exact scan, so counts are never approximate.</li><li><strong>Evidence rides along.</strong> Example hits return in the same response; one LLM call turns them into the narrative.</li></ul>
  </div>
</div>

<div class="proof-row">

  <div class="stat">
    <div class="num">1</div>
    <div class="label">REQUEST PER QUESTION</div>
    <div class="ctx">was 2: kNN, ship ids client-side, filtered aggregation</div>
  </div>

  <div class="stat">
    <div class="num">768-D</div>
    <div class="label">VECTORS BESIDE THE COLUMNS</div>
    <div class="ctx">EmbeddingGemma via Ollama · same document as the columns you aggregate</div>
  </div>

  <div class="stat">
    <div class="num">0</div>
    <div class="label">ETL JOBS</div>
    <div class="ctx">columns, text and vectors live in one store — nothing to sync</div>
  </div>

</div>


<section class="scene-section">
  <h2 class="scene" style="font-size:var(--fs-56);">ONE REQUEST, <span class="accent">WHOLE ANSWER.</span></h2>
  <p class="wide"><code class="inline">query.knn</code> retrieves the semantic slice; the <code class="inline">aggs</code> block computes the band split, key issues, CSAT percentile and handle-time average over that slice; <code class="inline">size: 3</code> returns the evidence hits. Demonstrated live with real 768-dim vectors — XERJ stores and searches them, it does not embed, so retrieval quality is your embedding model's job (EmbeddingGemma is a stand-in for yours).</p>

  <pre class="code">curl -s localhost:9200/conversations/_search -H 'Content-Type: application/json' -d '{
  "query": { "<span class="k">knn</span>": { "field": "vec", "query_vector": [<span class="comment">/* embed("wifi issues...") */</span>],
                       "k": 80, "num_candidates": 130 } },
  "size": 3, "_source": ["band","issue","body"],
  "<span class="k">aggs</span>": { "by_band": { "terms": { "field": "band" }, "aggs": {
      "key_issues": { "terms": { "field": "issue", "size": 4 } },
      "csat": { "percentiles": { "field": "csat", "percents": [50] } },
      "aht":  { "avg": { "field": "handle_time_s" } } } } }
}'</pre>
  <p style="margin-top:14px; font-size:12px; letter-spacing:.04em; color:var(--z-mute); font-family:var(--font-data);">ONE POST /_search · RC.6</p>

  <pre class="code">"of calls about wifi issues, how many 2.4 vs 5GHz, and what are the key issues?"

retrieved 80 nearest wifi calls; aggregated in the same request:
  2.4GHz  29 (54%)  csat_p50=4.0  aht=897s  issues: channel-overlap, congestion, disconnects, legacy-device
  5GHz    25 (46%)  csat_p50=4.0  aht=924s  issues: range, disconnects, congestion

deep-research narrative (LLM over the retrieved examples):
  The key issue is that the 5GHz signal is weak in a nearby room, dropping to 2.4GHz
  and resulting in slower speeds.</pre>
  <p style="margin-top:14px; font-size:12px; letter-spacing:.04em; color:var(--z-mute); font-family:var(--font-data);">RECORDED RUN · SEEDED-GENERATOR OUTPUT · 54 OF THE 80 CARRIED A WIFI BAND; THE 26 N/A ARE FILTERED CLIENT-SIDE · 03_deep_research.py</p>
</section>

<section class="scene-section">
  <h2 class="scene" style="font-size:var(--fs-56);">WHAT THIS <span class="accent">DOES NOT SHOW.</span></h2>
  <div class="laws">
    <div class="n">01</div>
    <div class="law">
      <div class="t">EXACT SCAN, <span class="accent">NO SPEED CLAIM.</span></div>
      <div class="b">An aggs-bearing kNN always runs the exact brute-force scan: <code class="inline">num_candidates</code> is ignored, HNSW never serves it, and cost scales with corpus size × dims. Nothing here was timed.</div>
    </div>
    <div class="n">02</div>
    <div class="law">
      <div class="t">BUCKETS COUNT <span class="accent">THE SLICE.</span></div>
      <div class="b">Aggregations count only the retrieved top-k neighbour set, and <code class="inline">hits.total.value</code> echoes k — the 80 is the request parameter coming back, not a corpus match count.</div>
    </div>
    <div class="n">03</div>
    <div class="law">
      <div class="t">KNOWN <span class="accent">GAPS.</span></div>
      <div class="b"><code class="inline">significant_terms</code> over a kNN slice returns empty, hybrid (RRF) + aggs is rejected with a 400, and kNN inside <code class="inline">bool.filter</code> returns no buckets. Use <code class="inline">terms</code> in-slice, or the two-step pattern.</div>
    </div>
    <div class="n">04</div>
    <div class="law">
      <div class="t">SYNTHETIC, <span class="accent">NOT EXCLUSIVE.</span></div>
      <div class="b">The numbers are artifacts, not findings. ES/OpenSearch or Postgres + pgvector can express this shape too — what differs is cost model and operational weight, not possibility.</div>
    </div>
  </div>
</section>

<section class="scene-section">
  <h2 class="scene" style="font-size:var(--fs-56);">READ THE <span class="accent">WALKTHROUGH.</span></h2>
  <p class="wide">The question came from calltree.ai, who run AI over support interactions — a motivating party, not a customer. The walkthrough has the three runnable scripts, the recorded output and the scaling guide. XERJ on :9200 plus Ollama is the whole stack.</p>
  <div style="display:flex; gap:var(--sp-6); margin-top:var(--sp-6); flex-wrap:wrap;">
    <a href="https://github.com/xerj-org/xerj/tree/main/docs/case-studies/calltree-analytics" rel="external" class="cta" style="font-size:var(--fs-20); padding:var(--sp-4) 0; border-bottom:0; flex:1; min-width:280px;">
      <span>OPEN THE WALKTHROUGH</span>
      <span class="arrow">→</span>
    </a>
    <a href="/case-studies" class="cta" style="font-size:var(--fs-20); padding:var(--sp-4) 0; border-bottom:0; flex:1; min-width:280px;">
      <span>ALL CASE STUDIES</span>
      <span class="arrow">→</span>
    </a>
  </div>
</section>

<section class="lead-capture" id="demo">
  <div class="kicker"><span>READY?</span><span class="dash">·</span><span>REQUEST ACCESS</span></div>
  <h3>RUN IT ON<br><span class="accent">YOUR CONVERSATIONS.</span></h3>
  <p>Send us your mapping and one deep-research question. We'll send back the single-request version — kNN + aggs over your schema — with the scripts to reproduce it.</p>
  <form class="lead-form" id="leadForm" action="#" method="post" novalidate>
    <div class="lead-form-input">
      <input type="email" name="email" placeholder="[email protected]" required aria-label="Work email" autocomplete="email" />
    </div>
    <button type="submit" class="demo">SEE THE DEMO <span class="arrow">→</span></button>
    <span class="note">We only use this email to send you the binary. Ever.</span>
    <span class="ok">✓ THANKS. CHECK YOUR INBOX WITHIN 24 HOURS.</span>
  </form>
</section>

<!-- seo:footer-begin — generated by scripts/seo/fix_links.py · do not hand-edit -->
<nav class="footer-map" aria-label="Site map">
  <div class="fm-col">
    <span class="fm-h">PRODUCT</span>
    <a href="/product">PRODUCT</a>
    <a href="/architecture/">ARCHITECTURE</a>
    <a href="/benchmarks/">BENCHMARKS</a>
    <a href="/pricing/">PRICING</a>
    <a href="/security/">SECURITY</a>
    <a href="/playground">DASHBOARDS</a>
    <a href="/demo/">REAL-DATA DEMO</a>
    <a href="/aise-demo">PRODUCT TOUR</a>
  </div>
  <div class="fm-col">
    <span class="fm-h">LEARN</span>
    <a href="/answers/">ANSWERS</a>
    <a href="/compare/">COMPARE</a>
    <a href="/use-cases">USE CASES</a>
    <a href="/case-studies">CASE STUDIES</a>
    <a href="/industries/">INDUSTRIES</a>
    <a href="/blog/">BLOG</a>
  </div>
  <div class="fm-col">
    <span class="fm-h">SOLUTIONS</span>
    <a href="/solutions/">SOLUTIONS</a>
    <a href="/industries/finserv">FINANCIAL SERVICES</a>
    <a href="/industries/public-sector">PUBLIC SECTOR</a>
    <a href="/industries/healthcare">HEALTHCARE</a>
    <a href="/industries/retail">RETAIL</a>
    <a href="/use-cases/code-security-audit">AI CODE-SECURITY AUDIT</a>
    <a href="/use-cases/semantic-analytics">SEMANTIC ANALYTICS</a>
    <a href="/resources/">SALES KIT</a>
  </div>
  <div class="fm-col">
    <span class="fm-h">DOCS</span>
    <a href="/docs/">DOCUMENTATION</a>
    <a href="/docs/quickstart">QUICKSTART</a>
    <a href="/docs/install">INSTALL</a>
    <a href="/docs/migration-from-es">MIGRATE FROM ELASTICSEARCH</a>
    <a href="/docs/recipes/">RECIPES</a>
    <a href="/docs/agents/">DOCS FOR AI</a>
    <a href="/for-agents">FOR AI AGENTS</a>
    <a href="/agent-search/">AGENTIC SEARCH DEMO</a>
    <a href="/llms.txt">LLMS.TXT</a>
    <a href="https://github.com/xerj-org/xerj" rel="external">GITHUB</a>
  </div>
</nav>
<!-- seo:footer-end -->
<footer class="footer">
  <span>XERJ.AI · CASE STUDIES · V0.1</span>
  <span>SEARCH FOR THE AGENT ERA</span>
  <span><a href="/">HOME</a> · <a href="/case-studies">ALL CASE STUDIES</a> · <a href="/docs/">DOCS</a> · <a href="/playground">DASHBOARDS</a> &middot; <a href="/llms.txt">LLMS.TXT</a></span>
</footer>

<script>
  (function () {
    const root = document.documentElement;
    const form = document.getElementById('leadForm');
    if (form) {
      form.addEventListener('submit', (e) => {
        e.preventDefault();
        const email = form.querySelector('input[type=email]').value.trim();
        if (!email || !email.includes('@')) return;
        try { fetch('/lead', { method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify({ email: email, source: 'calltree-analytics' }), keepalive: true }).catch(function () {}); } catch (_) {}
        form.classList.add('sent');
      });
    }
  })();
</script>

</body>
</html>