fix: repoint remaining .com refs missed by api#719

[sweetmantech]

What

Follow-up to api#719 — three .com references that sat outside its touched-domain test suites (recoupable/chat#1819 deferred §A items).

• lib/apify/sendApifyWebhookEmail.ts — the "Recoup Chat" CTA link in the LLM email-generation prompt was a hardcoded https://chat.recoupable.com/?q=… (dead). Now interpolates getFrontendBaseUrl() (→ chat.recoupable.dev in prod), reusing the same centralizer as the other email links (DRY).
• lib/mcp/tools/registerGetApiKeyTool.ts — the MCP tool description (shown to the LLM) + JSDoc pointed at the dead api.recoupable.com / developers.recoupable.com → api.recoupable.dev / docs.recoupable.dev.
• lib/catalog/getCatalogsHandler.ts — JSDoc legacy-endpoint reference → api.recoupable.dev.

Verification

• tsc --noEmit: no errors in the changed files.
• vitest run lib/apify lib/catalog lib/composio: 236 passed / 50 files.
• grep: no recoupable.com added in the diff.

Not included

Brand-email (@recoupable.com → @recoupable.dev) and sandbox.recoupable.com refs are tracked separately on #1819 (email pending the sending-domain decision; sandbox deferred — no live .dev target).

🤖 Generated with Claude Code

---

Summary by cubic

Fix dead links by switching remaining recoupable.com references to .dev and routing the Recoup Chat CTA through getFrontendBaseUrl(). This prevents broken email CTAs and outdated MCP tool/docs URLs.

• Bug Fixes
  • Updated the email CTA in sendApifyWebhookEmail to use getFrontendBaseUrl() instead of a hardcoded chat.recoupable.com (resolves to chat.recoupable.dev in prod).
  • Updated MCP tool description and JSDoc in registerGetApiKeyTool to api.recoupable.dev and docs.recoupable.dev.
  • Updated legacy endpoint reference in getCatalogsHandler JSDoc to api.recoupable.dev.

^{Written for commit 52e3958. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api	Ready	Preview	Jun 30, 2026 12:08am

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 10 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5508cff2-af42-4022-b51a-85681748c437

📥 Commits

Reviewing files that changed from the base of the PR and between 0e0bac0 and 52e3958.

📒 Files selected for processing (3)

• lib/apify/sendApifyWebhookEmail.ts
• lib/catalog/getCatalogsHandler.ts
• lib/mcp/tools/registerGetApiKeyTool.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/repoint-com-followup

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

Architecture diagram

sequenceDiagram
    participant Email as Email Service (Resend)
    participant Webhook as sendApifyWebhookEmail
    participant LLM as LLM Email Generator
    participant Config as Config/Env
    participant MCP as MCP Tool Registry
    participant Docs as Documentation Site
    participant API as API Route Handler

    Note over Email,API: NEW: Domain Reference Updates Across Components

    alt Email Webhook Flow
        Webhook->>Webhook: Compose email prompt with CTA link
        Webhook->>Config: CHANGED: Call getFrontendBaseUrl()
        Config-->>Webhook: Returns chat.recoupable.dev (current env)
        Webhook->>LLM: Generate email with CTA: {baseUrl}/?q=...
        LLM-->>Webhook: HTML email body
        Webhook->>Email: sendEmailWithResend()
    end

    alt MCP Tool Registration Flow
        MCP->>MCP: Register "get_api_key" tool
        Note over MCP: Description references:<br/>CHANGED: api.recoupable.dev<br/>CHANGED: docs.recoupable.dev
        MCP-->>LLM Agent: Tool description with new domain
        Note over LLM Agent: Agent uses description to construct<br/>HTTP requests to api.recoupable.dev
    end

    alt Catalog Listing Flow
        API->>API: GET /api/catalogs?account_id=...
        Note over API: JSDoc references legacy endpoint<br/>CHANGED: api.recoupable.dev
        API->>Database: selectAccountCatalogs()
        Database-->>API: Account catalogs
        API-->>Client: Response byte-identical to legacy endpoint
    end

Loading

<sub>Auto-approved: Updates dead .com URL references to .dev equivalents across three files, with no logic changes.

Re-trigger cubic</sub>