Skip to content

fix: repoint docs page content + nav to .dev hosts#255

Merged
sweetmantech merged 2 commits into
mainfrom
fix/repoint-docs-content
Jun 29, 2026
Merged

fix: repoint docs page content + nav to .dev hosts#255
sweetmantech merged 2 commits into
mainfrom
fix/repoint-docs-content

Conversation

@sweetmantech

@sweetmantech sweetmantech commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

What

Follow-up to docs#254 (which fixed the OpenAPI server.url + two nav buttons). This repoints the page content (.mdx) and the remaining nav links, which still showed dead .com hosts on the live docs.recoupable.dev home page.

Why

docs.recoupable.dev (deployed) still rendered:

  • every curl/code example against https://api.recoupable.com/... (dead, 000)
  • "API Keys Management Page" links → chat.recoupable.com/keys (dead)
  • a Blog nav link → research.recoupable.com (dead)

Changes (12 files, 68 lines, host-only)

  • api.recoupable.comapi.recoupable.dev — all examples + base URLs (index, quickstart, authentication, agents, cli, mcp, content-agent, credits, workflows/*)
  • chat.recoupable.comchat.recoupable.dev — API-key links, credits successUrl
  • developers.recoupable.comdocs.recoupable.dev — self-refs + AGENTS.md App URL
  • docs.json nav: Website recoupable.comrecoupable.dev; Blog research.recoupable.com (dead) → recoupable.dev/blog (200)

Left intact (out of scope)

  • Support email agent@recoupable.com (pending the brand-email keep-vs-move decision)
  • credits.mdx "Sign in at sandbox.recoupable.com" — sandbox.recoupable.dev is 404 / not provisioned

Verification

  • Every changed line is a host swap (diff: 68 +/68 -, no other edits)
  • docs.json re-validated (json.load parses)
  • grep clean: no chat/api/developers.recoupable.com left in content; intentionally-left hosts (sandbox/research-removed/email/apex→dev) confirmed

🤖 Generated with Claude Code


Summary by cubic

Repointed docs content and nav from .com to .dev so examples and links work on docs.recoupable.dev. Fixes dead curl targets and stale nav links.

  • Bug Fixes
    • Swapped api.recoupable.comapi.recoupable.dev in all examples and base URLs.
    • Updated chat.recoupable.comchat.recoupable.dev for API Keys links and credits successUrl.
    • Replaced developers.recoupable.comdocs.recoupable.dev for self-refs.
    • Adjusted docs.json nav: Website → recoupable.dev, Blog → research.recoupable.dev.

Written for commit 19e362b. Summary will update on new commits.

Review in cubic

docs#254 repointed the OpenAPI server URLs and two nav buttons, but the page
content (mdx) and the Website/Blog nav links still showed dead .com hosts on
docs.recoupable.dev — every curl example used api.recoupable.com, the API-key
links used chat.recoupable.com, and the Blog nav pointed at the dead
research.recoupable.com.

- api.recoupable.com → api.recoupable.dev (all curl/code examples + base URLs)
- chat.recoupable.com → chat.recoupable.dev (API Keys links, credits successUrl)
- developers.recoupable.com → docs.recoupable.dev (self-refs, AGENTS App URL)
- docs.json nav: Website recoupable.com → recoupable.dev; Blog
  research.recoupable.com (dead) → recoupable.dev/blog (live)

Left intact: the support email (agent@recoupable.com, pending the email
decision) and the credits.mdx "Sign in at sandbox.recoupable.com" line
(sandbox.recoupable.dev is 404 / not provisioned).

Refs recoupable/chat#1819.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 29 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: 025aeb53-aa7a-4d3a-8ed1-119a878f2c93

📥 Commits

Reviewing files that changed from the base of the PR and between 00d7ea1 and 19e362b.

📒 Files selected for processing (12)
  • AGENTS.md
  • agents.mdx
  • authentication.mdx
  • cli.mdx
  • content-agent.mdx
  • credits.mdx
  • docs.json
  • index.mdx
  • mcp.mdx
  • quickstart.mdx
  • workflows/create-artist.mdx
  • workflows/generate-music-video.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/repoint-docs-content

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.

@mintlify

mintlify Bot commented Jun 29, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
recoup-docs 🟢 Ready View Preview Jun 29, 2026, 11:33 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 12 files

Re-trigger cubic

The research/insights site now lives at https://research.recoupable.dev (added
after this PR's first pass, which had temporarily repointed the dead
research.recoupable.com to recoupable.dev/blog). Use the real research domain.

Refs recoupable/chat#1819.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

1 issue found across 1 file (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="docs.json">

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

PR description claims the Blog anchor was changed to 'recoupable.dev/blog', but the actual code changes it to 'https://research.recoupable.dev/' instead — the opposite direction and contradicting the stated intent.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread docs.json
{
"anchor": "Blog",
"href": "https://research.recoupable.com/",
"href": "https://research.recoupable.dev/",

Copy link
Copy Markdown

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

PR description claims the Blog anchor was changed to 'recoupable.dev/blog', but the actual code changes it to 'https://research.recoupable.dev/' instead — the opposite direction and contradicting the stated intent.

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

<comment>PR description claims the Blog anchor was changed to 'recoupable.dev/blog', but the actual code changes it to 'https://research.recoupable.dev/' instead — the opposite direction and contradicting the stated intent.</comment>

<file context>
@@ -416,7 +416,7 @@
         {
           "anchor": "Blog",
-          "href": "https://recoupable.dev/blog",
+          "href": "https://research.recoupable.dev/",
           "icon": "newspaper"
         }
</file context>
Suggested change
"href": "https://research.recoupable.dev/",
+ "href": "https://recoupable.dev/blog",

@sweetmantech sweetmantech merged commit 45f3240 into main Jun 29, 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