What if users can find anything in your docs, and you understand everything they need?

🐤Canary is open-source project just for that!

Search works, only when users know the "keyword"

Typical search experience looks like this:

...litellm_model_cost_map -> use deployment_cost...Router - Load Balancing, Fallbacks

😢

Set BudgetsBudgets, Rate Limits

Setting Team BudgetsBudgets, Rate Limits

😊

And this leads to bunch of support questions like:

👤 hi there! how can i set limit for api cost?

we already have docs for that. (readthemanual.com/budget-and-rate-limits) 👤

With Canary ↓

Search results are not always easy to digest

As documentation grows, users often need to read multiple sections and pages to get questions answered. This can be very time-consuming and frustrating.

feature_a: option_1, option_2, option_3, option_4, option_5...Reference - config.yaml

...feature_ais really good. there's 999 ways of doing...What is Feature_A?

...to configure options for feature_a, you shoud do this and that...Tutorial - Configuration

・・・

With Canary ↓

Understand users through their interactions with the docs

We're still working on Search & Ask analytics, which will help you gain insights into what users are searching and asking for. In the meantime, you can use other feedback components we provide to collect information,

like this 👇.