Skip to main content
Analytics shows how people and AI apps use your endpoints: how many requests came in, who sent them, which apps they used, what topics they asked about, and how well searches and answers performed. To open it, click Overview under Analytics in the sidebar, or go to app.raily.ai/dashboard/access-overview. The page has three tabs: Every number covers the Organization you have selected in the sidebar. Activity from other Organizations in your Account, including child Organizations, is not included. Switch Organizations to see theirs.

Choose the time range and filters

The controls at the top right apply to every card on the page.
  • Time range. Pick Today, 7 days, 30 days, 90 days, or 1 year, or click Custom to choose your own dates. The default is 7 days. Raily remembers your last choice when you come back.
  • Latest request · 7d. Shows the 7 days ending at your most recent request, instead of the 7 days ending today. Use it when an endpoint has been quiet for a while and the regular ranges come up empty. Hover the button to see the dates it covers.
  • Filter. Narrows the Usage and Content tabs to:
    • Endpoint: one endpoint, or All endpoints.
    • Request status: Success (200), Client error (400), or Server error (500).
    • User: one user or API key. Start typing to search the users who were active in the selected range.
    Click Apply. The Filter button shows how many filters are on.
  • Refresh reloads the numbers.
Your time range and filters carry over when you switch between Usage and Content, so you can look at one endpoint or one user on both tabs. Quality keeps the time range only. Most cards compare the selected range with the period right before it, for example “vs prev 7 days”.
Hover any card title or label with a dotted underline to see what it counts.

Usage

Usage is the traffic view. Use it to check adoption, see which AI apps your audience prefers, and spot slow or failing requests. A rising Zero-result rate usually means people are asking about things your Sources don’t cover, or that a search setting is too strict. The Content tab shows which topics those questions are about. Some requests don’t record timing or token counts. When that happens, the card says how many requests its numbers are based on.

Content

Content shows what people ask about. Raily groups similar questions into topics automatically. Use it to learn what your audience wants, see which topics are growing or fading, and find gaps in your content. The Topics table also has a row for requests that didn’t fit any topic. This usually means topics haven’t been set up for that kind of question yet, so lower is better.

Quality

Quality shows how well searches and answers are doing, based on automatic scoring of real requests.
  • Retrieval success rate: how often searches found relevant content.
  • Answer success rate: how often chat answers passed their checks. Shown when your endpoints have chat answers to score.
  • Output policies: the share of compliant images in results. Shown only for Accounts with image output policies.
  • Quality over time: the same rates across the range.
For what each score means and how to dig into a weak one, see Evals.

Next steps

Evals

Look into individual scores and the searches behind them

Access

Manage who can sign in to your endpoints

Users

See and manage the users of your endpoints

AI Endpoints

Expose your data to AI agents through authenticated endpoints