Skip to content

docs: normalize legacy plan names to current tiers#36

Merged
karlwaldman merged 2 commits into
mainfrom
chore/plan-name-normalization
Jun 21, 2026
Merged

docs: normalize legacy plan names to current tiers#36
karlwaldman merged 2 commits into
mainfrom
chore/plan-name-normalization

Conversation

@karlwaldman

Copy link
Copy Markdown
Member

Replaces legacy plan/tier names in customer-facing SDK docs and the QA issue-generator script with the current billing tiers (from GET /billing/plans).

Changes

  • docs/index.md — Paid Plans section: replaced legacy Exploration $15 / Production Boost $45 / Reservoir Mastery $129 with current tiers:
    • Developer $19/mo (10K)
    • Starter $49/mo (50K, webhooks)
    • Professional $99/mo (100K, webhooks + WebSocket streaming)
    • Scale $299/mo (1M)
  • CREATE_QA_GITHUB_ISSUES.sh — QA blocker note: "Production Boost access" → "Professional plan ($99/mo) access".

Docs/strings only. No functional code, paths, or Python source changed. No version bump.

🤖 Generated with Claude Code

Replace legacy tier names (Exploration / Production Boost / Reservoir
Mastery) in customer-facing docs and the QA issue-generator script with
the current billing tiers: Developer ($19/10K), Starter ($49/50K,
webhooks), Professional ($99/100K, webhooks + WebSocket streaming),
Scale ($299/1M). Docs/comments only; no functional code changed.

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

coderabbitai Bot commented Jun 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@karlwaldman, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 15 minutes and 36 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 611382e0-d59f-4271-b822-3213709b59dd

📥 Commits

Reviewing files that changed from the base of the PR and between ca7a267 and aa28451.

📒 Files selected for processing (4)
  • CREATE_QA_GITHUB_ISSUES.sh
  • README.md
  • docs/index.md
  • oilpriceapi/streaming/client.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/plan-name-normalization

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.

Replace "Reservoir Mastery" in the README streaming section and the
reject_subscription ConnectionError message with current billing
language: "Professional plan ($99/mo) or higher" (streaming gates at
Professional+). The error string keeps the "Subscription rejected"
prefix so the existing streaming unit test still matches.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@karlwaldman karlwaldman merged commit 785b385 into main Jun 21, 2026
6 checks passed
@karlwaldman karlwaldman deleted the chore/plan-name-normalization branch June 21, 2026 17:27
karlwaldman added a commit that referenced this pull request Jul 3, 2026
* docs: normalize legacy plan names to current tiers

Replace legacy tier names (Exploration / Production Boost / Reservoir
Mastery) in customer-facing docs and the QA issue-generator script with
the current billing tiers: Developer ($19/10K), Starter ($49/50K,
webhooks), Professional ($99/100K, webhooks + WebSocket streaming),
Scale ($299/1M). Docs/comments only; no functional code changed.

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

* docs: normalize remaining streaming plan-name references

Replace "Reservoir Mastery" in the README streaming section and the
reject_subscription ConnectionError message with current billing
language: "Professional plan ($99/mo) or higher" (streaming gates at
Professional+). The error string keeps the "Subscription rejected"
prefix so the existing streaming unit test still matches.

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

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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