Skip to content

docs: remove phantom GET /api/artist-profile endpoint (never implemented)#266

Merged
sweetmantech merged 2 commits into
mainfrom
fix/remove-phantom-artist-profile-endpoint
Jul 6, 2026
Merged

docs: remove phantom GET /api/artist-profile endpoint (never implemented)#266
sweetmantech merged 2 commits into
mainfrom
fix/remove-phantom-artist-profile-endpoint

Conversation

@sweetmantech

@sweetmantech sweetmantech commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

Removes the Get Artist Profile reference page — it documents GET /api/artist-profile, an endpoint that does not exist in the api codebase and never has.

Evidence

  • recoupable/api has no such route: app/api/artist/ contains only socials/; a repo-wide grep for artist-profile finds no handler.
  • Live probe (2026-07-06): GET https://api.recoupable.dev/api/artist-profile?artist_account_id=<uuid> with a valid Bearer token returns the Next.js HTML app shell (catch-all 200), not JSON — any agent following the docs (llms.txt included this page) gets an unparseable response.
  • The data the page promises is already served by real endpoints: GET /api/artists/{id}/socials (per-platform follower_count) and GET /api/research/profile.

What changed (purely deletive, 85 lines)

  • api-reference/artist/profile.mdx — page removed
  • api-reference/openapi/releases.json/api/artist-profile path + its two exclusively-referenced schemas (ArtistProfileResponse, ArtistProfileErrorResponse) removed via surgical text edits (no reformat; file re-validated as JSON)
  • docs.json — nav entry removed (re-validated; removal also drops the page from generated llms.txt)
  • No other page cross-links the removed page (grep clean)

Per the house rule: an undocumented-but-real gap is better than a documented-but-false one.

🤖 Generated with Claude Code


Summary by cubic

Removed the phantom GET /api/artist-profile docs and links, and updated Quickstart to point to the real socials endpoint. This stops calls to a non-existent API and directs users to GET /api/artists/{id}/socials.

  • Bug Fixes
    • Deleted api-reference/artist/profile.mdx.
    • Removed /api/artist-profile and its two exclusive schemas from api-reference/openapi/releases.json (JSON re-validated).
    • Dropped the nav entry from docs.json.
    • Updated quickstart.mdx: Artist Data card now links to /api-reference/artists/socials with corrected copy.

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

Review in cubic

…ted)

The reference page documents an endpoint that does not exist in the api
codebase (app/api/artist/ has only socials/; requests to prod return the
Next.js HTML 404 page). Accuracy over symmetry: remove the page, its
OpenAPI path, its two exclusively-referenced schemas, and the nav entry.
Live profile metrics are served by GET /api/artists/{id}/socials
(follower_count per platform) and GET /api/research/profile.

Found while reading Patrick Quaggin-Smith's roster via the API (chat#1851
follow-up).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@cursor

cursor Bot commented Jul 6, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@sweetmantech, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 377df03d-a5aa-4bc5-8805-bb26432d999c

📥 Commits

Reviewing files that changed from the base of the PR and between 100a41f and b70c344.

📒 Files selected for processing (4)
  • api-reference/artist/profile.mdx
  • api-reference/openapi/releases.json
  • docs.json
  • quickstart.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/remove-phantom-artist-profile-endpoint

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.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@sweetmantech

Copy link
Copy Markdown
Collaborator Author

Follow-up commit: quickstart.mdx's Artist Data card linked to the removed page — repointed to /api-reference/artists/socials (the real endpoint). Cross-link grep is now clean repo-wide.

@cursor

cursor Bot commented Jul 6, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@sweetmantech sweetmantech merged commit 2cf8704 into main Jul 6, 2026
3 checks passed
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