AI search · For technical documentation

Search that answers

Stop sending users to ten blue links. Biel reads your docs and returns the actual answer, with the sources cited and follow-ups already loaded. Unified across every doc platform you use.

Start free trial Book a demo

14-day freeSelf-serveLive in 15 min

configure routing

Ask AI to answer your question

Workflows (Enterprise)(3 results)

Configure routing rules

Configure routing rules 1. Navigate to Routing rules in your workflow settings

Setting up a workflow

for each project you want to include. 6. Click Save. Configure routing rules 1. Navigate to Routing rules in your workflow settings

Set up custom actions

Actions in your workflow settings. 2. Click Add action. 3. Configure your action: Action type: Slack, Microsoft Teams, Email, Zendesk, Webhook

Customization

Widget

Configure the Biel.ai widget appearance, behavior, and AI settings. See the widget customization guide for the full list of properties.

Navigate↑↓Select↵CloseEsc

Used by teams that take their documentation seriously

The shift

Keyword search assumes your users know the keywords

They don’t. They know what they’re trying to do. They type “user can’t log in” and get a list of pages with “login” in the title. AI search reads those pages for them and returns the actual answer, then offers the sources for verification.

Keyword search

Search that lists

×Returns ten links and lets the user figure out which one has the answer.
×Matches words, not meaning. Synonyms break it. Acronyms confuse it.
×Requires the user to already know your docs vocabulary before they search.
×Indexes one platform at a time. Multiple doc sites mean multiple search bars.
×Tells you nothing about what the user was actually looking for.

AI search

Search that answers

iReturns the answer first, with sources cited underneath for verification.
iiUnderstands intent. "User can't log in" maps to authentication, sessions, password reset.
iiiSpeaks the user's language. Reads English docs, answers in 30+ languages.
ivIndexes everywhere your docs live: API ref, guides, GitHub, Confluence, Notion.
vLogs every query so you see what's missing before it becomes a ticket.

Multi-source

One search bar. Every doc you have.

Most teams have docs scattered across three or four platforms: a guide site, an API reference, a GitHub wiki, maybe Confluence or Notion. Biel indexes them all and serves unified results, so users never have to guess where to look.

Docusaurus

Sphinx

Confluence

GitHub README

Notion

OpenAPI spec

One unified search

→ The answer your user needs

No more “where did I read that again?”

Your docs live wherever your team writes them. The reader shouldn’t care. Biel pulls indexed content from every connected source and ranks results across platforms, so users get the right answer regardless of which system happens to host it.

Crawl on a schedule. Re-index on every push. Trigger a refresh via webhook. The search index stays in sync with whatever your team is shipping right now.

Ranking

Control which sources win a search

Not every doc is equal. The official API reference should beat the community thread. Getting-started guides should rank higher for new users. Configure source weighting and ranking rules so the right doc surfaces for the right query.

Boost your sources of truth

Mark official docs as authoritative. Demote community contributions. Set per-source weights so the canonical answer always rises to the top.

api-reference: weight 1.0
community:    weight 0.4
archived:     weight 0.0

ii.

Version-aware ranking

Customers on v3 should see v3 docs, not v1. Tag content by version, environment, or product line and have results filter automatically.

v3 docs: surfaced for v3 users
v1 docs: archived but searchable

iii.

Exclude what shouldn't rank

Internal-only pages, deprecated content, draft articles, customer-specific docs. Set inclusion rules at the path or tag level. Users see what you have approved.

exclude: /internal/**
exclude: tags:draft

Use cases

Three places teams replace their old search

Whether you’re swapping out Algolia DocSearch, an in-house keyword index, or just the default search box your static site generator shipped with: same install, same engine, dramatically better results.

Replacing Algolia DocSearch

Same UX. Real answers.

Drop-in replacement for keyword-based docs search. Same keyboard shortcut (⌘K), same modal pattern, same speed. Plus the answer at the top, not just the link list.

Cross-platform unification

One bar across your stack

For teams whose docs span multiple platforms. One search index, one search bar, one ranking system, regardless of where each piece of documentation actually lives.

Internal knowledge search

Replace the broken intranet

Wire Biel up to Confluence, Notion, and Google Drive. Employees ask in plain language, get the answer with the source, and stop pinging colleagues for the same recurring questions.

“Reads all our sites without trouble, and helps us learn what questions our users ask.”

Tim McMakin · Technical Writer at TriliTech

Things teams ask about AI search

How is this different from a chatbot?

A chatbot waits for the user to start a conversation. AI search is the search experience itself: a ⌘K modal, an inline search bar, a results dropdown. Same engine underneath, different surface.

Can I run AI search alongside an existing keyword index?

Yes. Many teams keep classic keyword search for known queries and add Biel for natural-language questions. You can also run Biel as the primary search and use it to supplement what you already have.

How fresh are the results?

As fresh as you want. Re-index on a schedule (hourly, daily), trigger via GitHub Action on every commit, or call the refresh API from your CI/CD pipeline. The index stays in sync with your live docs.

What happens if my docs span multiple languages?

Biel reads multilingual content and answers in the language the user asked in. So a user typing in French gets a French answer pulled from your English docs. Or your French docs. Or a mix.

Can I see what people are searching for?

Yes. Every query is logged in your dashboard with the answer Biel returned, the sources cited, and whether the user found what they needed. Use it to spot content gaps and prioritize what to write next.

Does it work with private docs behind a login?

Yes. Setup depends on how your authentication works (SSO, basic auth, custom headers, IP allowlist). Book a demo and we'll walk through the options for your stack.

Help users find answers. Not links.

Start free trial Book a demo

14-day free trial · No credit card required · From $50/mo