canonical: https://jentic.com/apis/rybbit.com/rybbit

# Rybbit Analytics API

Rybbit open-source web analytics API. Provides endpoints for retrieving site analytics data including overview metrics, sessions, events, users, goals, funnels, and performance data. The API exposes 7 endpoints secured with bearer authentication.

## For AI agents

Programmatically get high-level analytics metrics, get time-series analytics data. Covers 7 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Get high-level analytics metrics
- Manage analytics data programmatically
- Integrate Rybbit Analytics API into automated workflows
- Query and filter Rybbit Analytics API records by parameters
- Monitor Rybbit Analytics API operational status and events

## Use cases

### Analytics Operations

Use the Rybbit Analytics API to perform analytics operations programmatically. The API provides 7 endpoints covering core functionality including get high-level analytics metrics, get time-series analytics data, get dimensional analytics breakdown.

Example prompt: Call GET `/api/sites/{site}/overview` to get high-level analytics metrics

### Automated Overview Management

Automate overview operations by combining multiple Rybbit Analytics API endpoints. Agents can get time-series analytics data and then get dimensional analytics breakdown in a single workflow.

Example prompt: Call GET `/api/sites/{site}/overview-bucketed` to get time-series analytics data, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rybbit Analytics API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'get high-level analytics metrics', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/sites/{site}/overview` | Get high-level analytics metrics |
| GET | `/api/sites/{site}/overview-bucketed` | Get time-series analytics data |
| GET | `/api/sites/{site}/metric` | Get dimensional analytics breakdown |
| GET | `/api/sites/{site}/live-user-count` | Get count of active sessions |
| GET | `/api/sites/{site}/sessions` | Get paginated list of sessions |
| GET | `/api/sites/{site}/sessions/{sessionId}` | Get session details with events |
| GET | `/api/sites/{site}/session-locations` | Get aggregated session locations for map visualization |

## Key resources

- **Overview** — Site overview metrics
- **Sessions** — Session analytics

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/rybbit.com/rybbit/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Rybbit Analytics API by hand means handling its bearer token, attaching it to each request to api.rybbit.com, and managing your own retries. Through Jentic you install once, import the Rybbit Analytics API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Rybbit puts the site id in the URL path (`/api/sites/{site}/...`), so a rule can pin your agent to one site: it can read that site's overview, metrics, and sessions and nothing else. You choose the operations it may call, so it reads only the endpoints you allow.
- **Credential handling:** Your Rybbit Analytics API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get high-level analytics for a site' or 'count live users', and Jentic returns the matching Rybbit Analytics API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Rybbit Analytics API use?

The Rybbit Analytics API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get high-level analytics metrics with the Rybbit Analytics API?

Yes. Use the GET `/api/sites/{site}/overview` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rybbit Analytics API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get high-level analytics metrics through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get high-level analytics metrics'. Jentic returns the matching Rybbit Analytics API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rybbit Analytics API have?

The Rybbit Analytics API exposes 7 endpoints covering overview, sessions operations.

### Can I limit what my agent is allowed to do with the Rybbit Analytics API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use with the Rybbit Analytics API. The site id lives in the URL path (`/api/sites/{site}/...`), so you can pin the agent to a single site and let it read only that site's overview, metrics, sessions, live user count, and session locations. You also choose exactly which of the read endpoints it may call, and your stored bearer token is injected only for those calls.