docs: repoint AGENTS.md endpoints and branding to .dev domains

[sweetmantech]

Why

The .com→.dev migration (chat#1819) shipped to prod 2026-06-30. chat.recoupable.com and developers.recoupable.com are DNS-dead, but AGENTS.md (which every agent session loads as CLAUDE.md) still documented them — an agent session hit NXDOMAIN following these hosts verbatim.

Companion to recoupable/skills#75 (merged), which swept the same dead hosts out of the skills repo.

What

API Endpoints:

Old	New
chat.recoupable.com/api (dead)	chat.recoupable.dev/api
recoup-api.vercel.app/api (alive, not canonical)	api.recoupable.dev/api
developers.recoupable.com (dead)	docs.recoupable.dev (+ note /llms.txt, /llms-full.txt)

Branding: agent@recoupable.dev (brand email moved to the .dev apex per #1819, Resend-verified), chat.recoupable.dev, recoupable.dev.

CLAUDE.md is a symlink to AGENTS.md, so both are covered by the one edit.

Verification

• chat.recoupable.dev, api.recoupable.dev, docs.recoupable.dev, recoupable.dev all return 200
• docs.recoupable.dev/llms.txt + /llms-full.txt return 200
• chat.recoupable.com / developers.recoupable.com are NXDOMAIN

🤖 Generated with Claude Code

---

Summary by cubic

Repointed AGENTS.md to .dev domains to match the .com→.dev migration, preventing NXDOMAIN errors during agent sessions and standardizing on the canonical API host.

• Bug Fixes
  • Endpoints: Chat → https://chat.recoupable.dev/api, API → https://api.recoupable.dev/api, Docs → https://docs.recoupable.dev (LLM files: /llms.txt, /llms-full.txt).
  • Branding: support email → agent@recoupable.dev, app → https://chat.recoupable.dev, site → https://recoupable.dev. CLAUDE.md is covered via symlink.

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 54 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: 0145943a-ffa0-4b57-8a1d-c48f7518f4da

📥 Commits

Reviewing files that changed from the base of the PR and between 6c89de6 and b49d7aa.

📒 Files selected for processing (1)

• AGENTS.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/dev-domain-refs

---

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 1 file

_{Re-trigger cubic}