Skip to content

Docs: Split API reference into domain sub-routes#102

Merged
sweetmantech merged 15 commits intomainfrom
feat/docs-sub-routes
Apr 6, 2026
Merged

Docs: Split API reference into domain sub-routes#102
sweetmantech merged 15 commits intomainfrom
feat/docs-sub-routes

Conversation

@recoup-coding-agent
Copy link
Copy Markdown
Collaborator

@recoup-coding-agent recoup-coding-agent commented Apr 6, 2026

Summary

  • Splits the monolithic "API reference" tab into 5 domain-specific navigation tabs
  • Research: Artist research endpoints, artists, fans & segments, posts & comments, chat
  • Releases: Songs & catalogs, tasks
  • Content: Content creation, content agent, image generation, transcription, sandboxes
  • Social Media: Spotify, Instagram, X (Twitter), social scraping, Apify, connectors
  • Platform: Accounts, organizations, workspaces, subscriptions, admins, pulses, notifications
  • All existing MDX page paths remain unchanged — only the navigation structure in docs.json is updated

Test plan

  • Verify Mintlify deployment preview renders all 5 tabs correctly
  • Confirm all existing API doc pages are accessible from the new navigation
  • Check that no pages are missing from the navigation

🤖 Generated with Claude Code


Summary by cubic

Split the monolithic API reference into five tabs—Research, Releases, Content, Social Media, and Accounts—and refreshed the home page for faster onboarding and LLM navigation.

  • Refactors
    • Merged api-reference/introduction into / with base URL/auth and OpenAPI link.
    • Updated base URL to https://recoup-api.vercel.app/api in the root page and Quickstart examples.
    • Renamed Guides tab to Quickstart.
    • Set Social Media default to Connectors list.
    • Moved Pulses to top of Accounts (Update first).
    • Moved Artists and Fans & Segments to Releases; moved Posts & Comments to Content; set Tasks third in Releases.
    • In Research, put Chat first with Stream first.
    • Updated the home page card to Accounts.

Written for commit f1a9dc6. Summary will update on new commits.

Summary by CodeRabbit

  • Documentation
    • Reorganized documentation navigation with new top-level tabs: Research, Releases, Content, Social Media, and Platform.
    • Redistributed documentation groups across new tab structure for improved organization and discoverability.

Restructure the single "API reference" tab into 5 domain-specific tabs:
- Research: artist research, fans, segments, posts, chat
- Releases: songs, catalogs, tasks
- Content: content creation, content agent, image, transcribe, sandboxes
- Social Media: Spotify, Instagram, X, social scraping, connectors
- Platform: accounts, organizations, workspaces, subscriptions, admins

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 6, 2026

📝 Walkthrough

Walkthrough

The documentation navigation structure in docs.json has been reorganized from a single top-level "API reference" tab into five distinct tabs: "Research," "Releases," "Content," "Social Media," and "Platform," with page groups redistributed and renamed accordingly across the new tab hierarchy.

Changes

Cohort / File(s) Summary
Documentation Navigation Restructuring
docs.json
Reorganized top-level tabs from a single "API reference" to five tabs (Research, Releases, Content, Social Media, Platform). Redistributed and renamed page groups across new hierarchy; moved API documentation groups including songs/catalogs, accounts, organizations, social platforms, content creation, and notifications into their respective new tabs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • sweetmantech

Poem

🐰 Tabs reorganized with care,
Five new homes for docs everywhere!
Research, Releases, all in place,
Platform and Content find their space.
Navigation shines with polished grace! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: reorganizing the API reference documentation into domain-specific sub-routes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/docs-sub-routes

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

sweetmantech and others added 8 commits April 5, 2026 19:43
Add structured API sections, CLI/MCP cards, and a plain-text
endpoint reference so LLMs given the root URL can immediately
discover all available endpoints without navigating sub-pages.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Move base URL, authentication, API key setup, and OpenAPI spec link
into index.mdx so LLMs and users get everything on the first page.
Remove the now-redundant introduction page and its nav entry.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Make "List connectors" the default landing page for the Social Media
tab so OAuth connector setup is the first thing users see.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 issues found across 3 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="index.mdx">

<violation number="1" location="index.mdx:70">
P2: The text says "five main sections" but the CardGroup below shows six cards. Either update the count to "six" or merge Chat into the Research card to match.</violation>

<violation number="2" location="index.mdx:140">
P2: Custom agent: **Flag AI Slop and Fabricated Changes**

The research quick reference is missing 2 of 30 endpoints: `instagram-posts` and `track`. An LLM relying on this section will not discover those endpoints. Add them to the list to match the actual `api-reference/research/` directory.</violation>
</file>

<file name="docs.json">

<violation number="1" location="docs.json:37">
P2: Custom agent: **Flag AI Slop and Fabricated Changes**

Broken indentation: the `{` opening the Research group lost all indentation when the preceding Overview group was removed. Every other group object in this file is indented with 10 spaces inside `"groups"` arrays. This is sloppy AI-generated formatting that harms readability.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.

## Key Capabilities
## API Sections

The API is organized into five main sections. Use these links to jump to the right area.
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: The text says "five main sections" but the CardGroup below shows six cards. Either update the count to "six" or merge Chat into the Research card to match.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At index.mdx, line 70:

<comment>The text says "five main sections" but the CardGroup below shows six cards. Either update the count to "six" or merge Chat into the Research card to match.</comment>

<file context>
@@ -24,79 +50,118 @@ This is where record labels, musicians, and managers start to build on Recoup AI
-## Key Capabilities
+## API Sections
+
+The API is organized into five main sections. Use these links to jump to the right area.
 
 <CardGroup cols={2}>
</file context>
Suggested change
The API is organized into five main sections. Use these links to jump to the right area.
The API is organized into six main sections. Use these links to jump to the right area.
Fix with Cubic


If you are an LLM navigating these docs, here is a summary of the endpoint structure:

- **`/api/research/*`** — Artist research (search, lookup, profile, metrics, audience, cities, similar, urls, playlists, albums, tracks, career, insights, genres, festivals, web, deep, people, extract, enrich, milestones, venues, rank, charts, radio, discover, curator, playlist)
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Custom agent: Flag AI Slop and Fabricated Changes

The research quick reference is missing 2 of 30 endpoints: instagram-posts and track. An LLM relying on this section will not discover those endpoints. Add them to the list to match the actual api-reference/research/ directory.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At index.mdx, line 140:

<comment>The research quick reference is missing 2 of 30 endpoints: `instagram-posts` and `track`. An LLM relying on this section will not discover those endpoints. Add them to the list to match the actual `api-reference/research/` directory.</comment>

<file context>
@@ -24,79 +50,118 @@ This is where record labels, musicians, and managers start to build on Recoup AI
+
+If you are an LLM navigating these docs, here is a summary of the endpoint structure:
+
+- **`/api/research/*`** — Artist research (search, lookup, profile, metrics, audience, cities, similar, urls, playlists, albums, tracks, career, insights, genres, festivals, web, deep, people, extract, enrich, milestones, venues, rank, charts, radio, discover, curator, playlist)
+- **`/api/content/*`** — Content creation (create, generate-image, generate-video, generate-caption, transcribe-audio, edit, upscale, analyze-video, templates, validate, estimate)
+- **`/api/chat/*`** — Chat (chats, artist, segment, messages, messages-copy, messages-trailing-delete, create, update, delete, generate, stream, compact)
</file context>
Suggested change
- **`/api/research/*`** — Artist research (search, lookup, profile, metrics, audience, cities, similar, urls, playlists, albums, tracks, career, insights, genres, festivals, web, deep, people, extract, enrich, milestones, venues, rank, charts, radio, discover, curator, playlist)
- **`/api/research/*`** — Artist research (search, lookup, profile, metrics, audience, cities, similar, urls, playlists, albums, track, tracks, career, insights, genres, festivals, web, deep, people, extract, enrich, milestones, venues, rank, charts, radio, discover, curator, playlist, instagram-posts)
Fix with Cubic

sweetmantech and others added 6 commits April 5, 2026 19:54
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 issues found across 2 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="index.mdx">

<violation number="1" location="index.mdx:21">
P1: Custom agent: **Flag AI Slop and Fabricated Changes**

The base URL changed from the production domain (`api.recoupable.com`) to a Vercel deployment URL (`recoup-api.vercel.app`), but `authentication.mdx` and the majority of `openapi.json` endpoints still reference `api.recoupable.com`. This creates contradictory documentation — users following the homepage will hit a different host than users following the authentication guide. Either all docs should be updated consistently, or this change should be reverted to match the rest of the documentation.</violation>
</file>

<file name="quickstart.mdx">

<violation number="1" location="quickstart.mdx:11">
P1: Custom agent: **Flag AI Slop and Fabricated Changes**

The API base URL is silently changed from `api.recoupable.com` to `recoup-api.vercel.app` (a Vercel deployment URL), but the PR description claims only navigation structure was updated. This leaves the docs inconsistent — `authentication.mdx` still references `api.recoupable.com`, and many endpoint-level servers in `openapi.json` do as well. If this URL migration is intentional, it should be called out in the PR description and applied consistently; if not, this is an unintended change.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.

All API requests should be made to:

```bash
https://recoup-api.vercel.app/api
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Custom agent: Flag AI Slop and Fabricated Changes

The base URL changed from the production domain (api.recoupable.com) to a Vercel deployment URL (recoup-api.vercel.app), but authentication.mdx and the majority of openapi.json endpoints still reference api.recoupable.com. This creates contradictory documentation — users following the homepage will hit a different host than users following the authentication guide. Either all docs should be updated consistently, or this change should be reverted to match the rest of the documentation.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At index.mdx, line 21:

<comment>The base URL changed from the production domain (`api.recoupable.com`) to a Vercel deployment URL (`recoup-api.vercel.app`), but `authentication.mdx` and the majority of `openapi.json` endpoints still reference `api.recoupable.com`. This creates contradictory documentation — users following the homepage will hit a different host than users following the authentication guide. Either all docs should be updated consistently, or this change should be reverted to match the rest of the documentation.</comment>

<file context>
@@ -18,7 +18,7 @@ This is where record labels, musicians, and managers start to build on Recoup AI
 
 ```bash
-https://api.recoupable.com/api
+https://recoup-api.vercel.app/api

</file context>


</details>

<a href="https://www.cubic.dev/action/fix/violation/2e297e96-cdf5-4701-adcd-4c8a52df1987" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
    <source media="(prefers-color-scheme: light)" srcset="https://cubic.dev/buttons/fix-with-cubic-light.svg">
    <img alt="Fix with Cubic" src="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
  </picture>
</a>


```bash
https://api.recoupable.com/api
https://recoup-api.vercel.app/api
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Custom agent: Flag AI Slop and Fabricated Changes

The API base URL is silently changed from api.recoupable.com to recoup-api.vercel.app (a Vercel deployment URL), but the PR description claims only navigation structure was updated. This leaves the docs inconsistent — authentication.mdx still references api.recoupable.com, and many endpoint-level servers in openapi.json do as well. If this URL migration is intentional, it should be called out in the PR description and applied consistently; if not, this is an unintended change.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At quickstart.mdx, line 11:

<comment>The API base URL is silently changed from `api.recoupable.com` to `recoup-api.vercel.app` (a Vercel deployment URL), but the PR description claims only navigation structure was updated. This leaves the docs inconsistent — `authentication.mdx` still references `api.recoupable.com`, and many endpoint-level servers in `openapi.json` do as well. If this URL migration is intentional, it should be called out in the PR description and applied consistently; if not, this is an unintended change.</comment>

<file context>
@@ -8,7 +8,7 @@ description: "Get your API key and make your first request to the Recoup API."
 
 ```bash
-https://api.recoupable.com/api
+https://recoup-api.vercel.app/api

</file context>


</details>

<a href="https://www.cubic.dev/action/fix/violation/35af5fdd-bd50-4e61-b93e-edaa2401aa04" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
    <source media="(prefers-color-scheme: light)" srcset="https://cubic.dev/buttons/fix-with-cubic-light.svg">
    <img alt="Fix with Cubic" src="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
  </picture>
</a>

@sweetmantech sweetmantech merged commit 819e1e7 into main Apr 6, 2026
3 checks passed
sweetmantech added a commit that referenced this pull request Apr 6, 2026
- Fix section count: "five" → "six" to match actual card count
- Add missing research endpoints (track, instagram-posts) to LLM reference
- Revert base URL to api.recoupable.com for consistency with
  authentication.mdx and openapi.json

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
# Welcome to the Recoup API

Use the Recoup API to build your record label. Access artist analytics, fan segmentation, AI-powered chat, and task automation to power your music business.
Use the Recoup API to build your record label. Access artist analytics, fan segmentation, AI-powered chat, content creation, and task automation to power your music business.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Use the Recoup API to build your record label. Access artist analytics, fan segmentation, AI-powered chat, content creation, and task automation to power your music business.
Use the Recoup API to build your record label. Generate content, Access artist analytics, Manage your catalogs, AI-powered chat, and task automation to power your music business.

href="/api-reference/chat/chats"
>
AI-powered conversations with artist context. Stream responses or generate complete messages.
AI-powered conversations with artist context. Create, stream, and generate messages. Copy messages, delete trailing messages, and manage chat history.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

KISS principle

Suggested change
AI-powered conversations with artist context. Create, stream, and generate messages. Copy messages, delete trailing messages, and manage chat history.
Conversations with artist context. Create, stream, and generate messages. Copy messages, delete trailing messages, and manage chat history.

href="/content-agent"
>
Scrape profiles and comments.
AI content creation agent accessible via Slack. Generates images, videos, and captions for artists automatically.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

KISS

Suggested change
AI content creation agent accessible via Slack. Generates images, videos, and captions for artists automatically.
Content creation agent accessible via Slack. Generates images, videos, and captions for artists automatically.

- **`/api/research/*`** — Artist research (search, lookup, profile, metrics, audience, cities, similar, urls, playlists, albums, tracks, career, insights, genres, festivals, web, deep, people, extract, enrich, milestones, venues, rank, charts, radio, discover, curator, playlist)
- **`/api/content/*`** — Content creation (create, generate-image, generate-video, generate-caption, transcribe-audio, edit, upscale, analyze-video, templates, validate, estimate)
- **`/api/chat/*`** — Chat (chats, artist, segment, messages, messages-copy, messages-trailing-delete, create, update, delete, generate, stream, compact)
- **`/api/artists/*`** — Artist management (list, create, segments, socials, socials-scrape, profile)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this item first in the list as it's likely the first endpoint they need to hit.

sweetmantech added a commit that referenced this pull request Apr 6, 2026
- Update intro text to highlight content generation and catalogs
- KISS: remove "AI-powered" from Chat card description
- KISS: remove "AI" from Content Agent card description
- Move /api/artists/* to first in LLM quick reference

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
sweetmantech added a commit that referenced this pull request Apr 6, 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.

2 participants