Skip to content

docs: split Usage API into its own nav section - #1504

Open
CodesMcCabe wants to merge 3 commits into
mainfrom
cm/usage-api
Open

docs: split Usage API into its own nav section#1504
CodesMcCabe wants to merge 3 commits into
mainfrom
cm/usage-api

Conversation

@CodesMcCabe

Copy link
Copy Markdown
Contributor

Summary

  • Move the Usage API endpoints out from under the Admin API section in content/docs.yml so they render as a sibling section (still hidden: true) instead of nested under admin-api/.
  • Spec (usage-apihttps://admin-api.alchemy.com/v1/usage/openapi.json) already wired in content/remote-specs.json; two endpoints: GET /v1/usage/summary and POST /v1/usage/time-series.

Test plan

  • Preview the docs site and confirm the Usage API section renders separately from Admin API
  • Confirm endpoint URLs land under a usage-api slug (not doubled under admin-api/)

🤖 Generated with Claude Code

Move the Usage API endpoints out from under Admin API so they render as
a sibling section (still hidden) rather than nested under admin-api/.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@CodesMcCabe
CodesMcCabe requested a review from a team as a code owner August 5, 2026 18:35
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

🔗 Preview Mode

Name Status Preview Updated (UTC)
Alchemy Docs ✅ Ready 🔗 Visit Preview Aug 7, 2026, 6:11 PM

CodesMcCabe and others added 2 commits August 6, 2026 16:33
Give the new Usage API reference pages under /docs/reference/usage-api/, matching the Admin API docs pattern.

Co-authored-by: Cursor <cursoragent@cursor.com>
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