Most analytics integrations stop at aggregate numbers; this one hands over session IDs and the activity trail behind them, and adds a semantic search over user journeys so a long trail comes back as the relevant few chunks instead of flooding the context window. The screenshot and HTML tools let you look at the page a user was on while reading what they did on it.
A server that connects an agent to a Umami analytics account: site stats and metric breakdowns, live visitor counts, and the individual sessions behind the numbers.
- The websites in your Umami account with their IDs, which every other call needs
- Headline stats for a site — pageviews, visitors, bounce rate
- Metric breakdowns by URL, referrer, browser or country
- Pageview time series at an interval you choose
- The live count of active visitors
- Session IDs for an event or a period, and the full activity trail for one session
- Semantic search across many user journeys, returning only the chunks relevant to your question
- A screenshot and the raw HTML of a page, so behaviour can be read against what was on screen
A Umami analytics account with API access. Most calls take a website ID, so get_websites comes first. The journey search embeds text locally with an open-source sentence-transformer model from Hugging Face, so that tool pulls a model down on first use.