> ## Documentation Index
> Fetch the complete documentation index at: https://developers.jup.ag/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Analytics

> Understand your traffic, performance, cost, and origin, per team and per API.

Analytics show your traffic, performance, cost, and origin for a team and per API.

## Period and granularity

A timezone-aware period picker controls the range, and your choice persists as you move between pages. The time bucket scales with the range:

| Range | Bucket |
| :- | :- |
| Up to 1 hour | 1 minute |
| Up to 1 day | 15 minutes |
| Up to 7 days | 6 hours |
| Up to 30 days | 12 hours |
| Over 30 days | 1 day |

Analytics cover the last 6 months.

## Overview

The overview shows headline KPIs, each with a period-over-period trend:

| KPI | What it shows |
| :- | :- |
| Total requests | Requests in the period. |
| Errors and error rate | Responses with a 4xx or 5xx status, and that count as a percentage of total requests. |
| Latency (p50 / p95 / p99) | Median, 95th, and 99th percentile response time. |
| Credits consumed | Credits used in the period. |

Charts on the overview cover requests, latency, credits over time, status-code distribution, geographic distribution, and top paths.

<video autoPlay loop muted playsInline src="https://mintcdn.com/jupiter/arcA2CXzcFJzBqWS/static/images/portal-analytics-overview.mp4?fit=max&auto=format&n=arcA2CXzcFJzBqWS&q=85&s=396f3578c6d5462a40f8a323f59ba745" aria-label="Analytics overview dashboard showing KPIs and charts" />

## Per-API breakdown

For each API, see latency (p50 / p90 / p99) and request and error counts. Use it to find which API drives your traffic, errors, or latency.

![Per-API analytics breakdown showing latency percentiles and request and error counts](https://mintcdn.com/jupiter/arcA2CXzcFJzBqWS/static/images/portal-analytics-per-api.png?fit=max\&auto=format\&n=arcA2CXzcFJzBqWS\&q=85\&s=e7540b2dd655b934447694e328c15d7e)

## API-specific analytics

Some APIs have deeper analytics beyond the overview. Common metrics include volume, success rate, latency by phase, top token pairs, and fees collected.

<video autoPlay loop muted playsInline src="https://mintcdn.com/jupiter/arcA2CXzcFJzBqWS/static/images/portal-analytics-swap.mp4?fit=max&auto=format&n=arcA2CXzcFJzBqWS&q=85&s=43c67aab5fbbe6f5f08fe1880d20f1c4" aria-label="Swap API analytics: volume, success rate, latency by phase, top token pairs, and fees collected" />

> [!TIP]
>
> If there are specific metrics you need for your integration, [reach out to us](https://discord.com/channels/897540204506775583/910250162402779146) and we can help.

## Firewall analytics

Firewall analytics show rule outcomes over time and how often each rule matched. See [Firewall](https://developers.jup.ag/docs/portal/firewall.md) for the rules behind them.

## Related

> [card] [Request Logs](https://developers.jup.ag/docs/portal/logs.md)
>
> Drill from a trend into the individual requests behind it.

> [card] [Firewall](https://developers.jup.ag/docs/portal/firewall.md)
>
> The rules behind firewall analytics.

> [card] [Plans and Pricing](https://developers.jup.ag/docs/portal/plans.md)
>
> How credits map to cost.

> [card] [Rate Limits](https://developers.jup.ag/docs/portal/rate-limits.md)
>
> The limits your request volume runs against.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.