Skip to content

Adds Fumadocs coverage for the Usage feature - #115

Closed
MSami625 wants to merge 35 commits into
mainfrom
token-usage
Closed

Adds Fumadocs coverage for the Usage feature#115
MSami625 wants to merge 35 commits into
mainfrom
token-usage

Conversation

@MSami625

Copy link
Copy Markdown
Collaborator

What Changed?

Adds Fumadocs coverage for the Usage feature:

  • New page: docs-fumadocs/content/docs/monitoring/usage.mdx — overview, metrics, filters, drill-down, data freshness/history, pricing overrides, and ops notes
  • Adds Usage as the first item under Monitoring in the sidebar (monitoring/meta.json)
  • Links Usage from intro.mdx (Core capabilities + Key guides)
  • Adds Usage pricing CLI section to reference/cli-commands.mdx (seed-rates, diff-rates, recompute, sync-litellm, env tuning)
  • Updates feature-contributors.json and search index

No application code changes in this commit.

Why?

The Usage feature was implemented in the app but had no user-facing documentation in Fumadocs. This fills that gap so reviewers and customers can understand how Usage works (metrics, drill-down, entitlements, pricing overrides, and ops) in the same style as other docs (Metrics, Calls, etc.).

How to Test?

cd docs-fumadocs && npm run ci:check

Then locally:

npm run dev
  1. Open http://localhost:3000/docs/monitoring/usage/
  2. Confirm Usage appears first under Monitoring in the sidebar
  3. Spot-check internal links (workspaces, integrations, configuration, CLI commands)
  4. Open /docs/intro/ and confirm the Usage link under Key guides
  5. Open /docs/reference/cli-commands/ and confirm the Usage pricing section

Release Label

  • major - breaking change, next release bumps major version
  • minor - backward-compatible feature, next release bumps minor version
  • fix - backward-compatible bug fix, next release bumps patch version
  • No label (defaults to patch release)

If you do not have permission to apply labels, mention the intended release label here and a maintainer will set it.

Checklist

  • [ x] I have read the CONTRIBUTING.md guide.
  • [ x] My code follows the project's style guidelines.
  • [ x] I have added tests that prove my fix is effective or my feature works.
  • [ x] I have updated documentation where needed.

MSami625 and others added 30 commits August 7, 2026 19:02
…on to clear cache before seeding pricing rates
…sage pricing routes; enhance usage snapshot billability checks
…eamline cost calculations for pending usage deltas
@greptile-apps

greptile-apps Bot commented Aug 18, 2026

Copy link
Copy Markdown

Too many files changed for review (162 files, 100 file limit).

Bypass the limit by tagging @greptile-apps to review.

@MSami625 MSami625 closed this Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant