profile: drop-into-existing-pipeline recipe + cost-header read

[achris7]

Closes the two gaps the onboarding audit flagged for the GitHub org profile (both were 🟡):

• ① Integration path — the profile had a build-a-voice-turn-from-scratch quickstart but no "drop Floe into your existing pipeline" recipe. Added an "Already have a pipeline?" section: the one-line keyless base_url + Floe-key swap (OpenAI-compatible), linking to the docs integration guide (floe-labs-docs PR #69).
• ③ Cost visibility — the quickstart showed requests but never read a cost back. Added a note that each response returns X-Floe-Payment-Amount for per-call / per-task metering.

Not touched (flagged)

README:15 still says "200 API credits on signup" — this conflicts with the $2 welcome credit (email) and $3 (dashboard) seen on other surfaces. Cross-surface welcome-credit number needs one source of truth before I change any of them.

Status

Draft. No merge.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 9 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8ebfc885-5fa7-453e-92aa-87edfb00b87a

📥 Commits

Reviewing files that changed from the base of the PR and between f1b735f and ba32676.

📒 Files selected for processing (1)

• profile/README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/profile-integration-path-cost-headers

---

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

[Copilot]

Pull request overview

Adds missing onboarding guidance to the org profile README by documenting (1) how to route an existing OpenAI-compatible pipeline through Floe and (2) where to read per-call cost from response headers.

Changes:

• Documented per-response cost visibility via the X-Floe-Payment-Amount header.
• Added an “Already have a pipeline?” recipe showing how to swap base_url and API key for OpenAI-compatible SDKs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.