0% platform fee — first 1,000,000 customersClaim 0% fee
Analytics

See where every dollar goes — and where every millisecond goes.

Deep-dive spend, token, and latency analytics across every model, team, key, and tag. Cost is read directly from provider headers; the dashboard updates in real time.

Get startedSee the breakdown
analytics · last 30 days

Spend overview

gemini-2.5-pro$234.00 · 45%
claude-3.5-sonnet$156.00 · 30%
gpt-4o$89.00 · 17%
gemini-2.5-flash$42.00 · 8%
Total spend$521.00
Δ vs last month+12%
real-timeprovider-pricedledger-parity
Spend visibility
Real-time

Within seconds of completion

Latency reporting
p50 / p95 / p99

Per model, per key, per tag

Cost source
Provider headers

x-nemo-request-cost — never estimated

Ledger drift target
$0.00

Daily reported-vs-ledger parity check

The breakdown

Dollars by model. Milliseconds by percentile.

The two charts engineering and finance both open first — live in the dashboard within seconds of every completion.

Spend by model · last 30 days

$521.00

gemini-2.5-pro$234.00
claude-3.5-sonnet$156.00
gpt-4o$89.00
gemini-2.5-flash$42.00

Δ vs last month +12% · every dollar maps to one ledger row

Latency · gemini-2.5-flash · 24h

TTFT · p50
180 ms
TTFT · p95
420 ms
Total · p50
980 ms
Total · p95
1 240 ms
Total · p99
2 100 ms

TTFT measured at first SSE event · click-through to request logs

Cost integrity

What you see equals what you paid

Provider-priced

Cost is read, never computed — by us or by your code

The Nemo Intelligent Proxy Router owns cost calculation. We read x-nemo-request-cost from the response headers and write that exact value to the credit ledger and the analytics rollup. No second source of truth, no estimation, no rounding.

  • Single source of truth — x-nemo-request-cost
  • Every cost number on the dashboard maps to one ledger row
  • No client-side estimation; no manual price tables
  • Daily reported-vs-ledger parity check targets $0.00 drift
cost-integrity probe · 24h

Reported vs ledger

Requests settled w/ provider cost8 408 / 8 421
Released (errors / timeouts)13
Reported spend$521.00
Credit-ledger debit$521.00
Drift$0.00
Negative-balance attempts0
provider-pricedreserve+settleparity-checked
Full analytics reference — dimensions, tags, tokens, exports
Spend by model, team, key, customer
Per-model spend with month-over-month deltas, per-key spend with budget-cap proximity, per-team spend with enforcement, per-customer spend for end-user billing.
Spend-by-tag rollups
Pass arbitrary tags (team, project, feature, environment) via the standard OpenAI metadata field. Multi-tag intersection in every chart; cardinality enforced server-side so dashboards stay fast.
Latency percentiles
p50 / p95 / p99 per model, key, tag, and time window. Time-to-first-token and total latency tracked separately, streaming-aware. Click any percentile to drill into the underlying request log.
Time-range filtering
Hourly, daily, weekly, monthly granularity plus a custom calendar range — time-zone aware (your org timezone, not UTC), persistent across the Usage Explorer and Analytics Overview.
Token breakdown
Prompt vs completion token rollups per model, cached-input token tracking where supported, per-key token-usage charts, and avg input/output tokens per request with trend.
CSV export — every report
One-click export of spend breakdowns, usage rollups, token counts, and tag groups. Server-side export for large ranges; BI-tool-friendly snake_case columns; raw per-request logs via the observability API.
FAQ

Common analytics questions

Stop reconciling spreadsheets

Real-time spend, latency, and ledger parity — on every plan

Sign up, send your first request, and the analytics dashboard fills in. No instrumentation, no schemas to define, no overnight ETL to wait for.

Get startedRead the docs