Skip to content

docs(TSP-1321): document action-based billing for eval runs#696

Draft
claude[bot] wants to merge 1 commit into
mainfrom
docs/TSP-1321
Draft

docs(TSP-1321): document action-based billing for eval runs#696
claude[bot] wants to merge 1 commit into
mainfrom
docs/TSP-1321

Conversation

@claude

@claude claude Bot commented Jun 24, 2026

Copy link
Copy Markdown

Summary

  • Adds a new Billing for eval runs section to the Evals page (/build/agents/build-your-agent/evals) explaining that each evaluator Check costs 1 action, with a cost table, notes on the cost breakdown modal, the Actions column for UBB customers, and how legacy credit-billed customers are charged
  • Updates the FAQ on the Evals page from "How are credits calculated for evaluations?" to "How are eval runs billed?" to cover both billing models
  • Updates the Runs section description to note the Actions column available to UBB customers
  • Adds a sentence to the Understanding Actions section on the Plans page (/admin/subscriptions/plans) referencing eval runs as an action-consuming activity, with a cross-link to the new billing section

Linear issue

https://linear.app/relevance/issue/TSP-1321/

Adds a billing section to the Evals page explaining that each evaluator
Check costs 1 action, covers the cost breakdown modal, the Actions column
for UBB customers, and how credit-billed customers are charged. Updates
the plans page to reference eval runs as an action-consuming activity.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@claude claude Bot added the docs-drafter Documentation drafted by Claude label Jun 24, 2026
@linear

linear Bot commented Jun 24, 2026

Copy link
Copy Markdown

TSP-1321

@mintlify

mintlify Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
relevanceai 🟢 Ready View Preview Jun 24, 2026, 2:26 AM

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

@github-actions

Copy link
Copy Markdown
Contributor

🎯 Vibe check

Reviewed: 2 files (2 with issues, 0 clean)

Scores

Dimension Score What's holding it back
🟡 Consistency 6/10 British spellings ("Cancelling", "cancelled") in plans.mdx headings and body; bold label inside a callout in evals.mdx; "organization" lowercase on one line where the rest of the page uses "Organization"; "here" as link text.
🟢 Technical clarity 9/10 Both pages are well-structured and accurate. Minor: the Scenario results table labels the cost column "Credits" without clarifying whether new-billing users see the same label or "Actions".
🟢 Non-technical clarity 9/10 Billing concepts explained with concrete examples; evals concepts introduced before instructions begin.
🟡 Structure 7/10 The top Warning in plans.mdx is four paragraphs with bold text and a link — violates the single-short-paragraph callout rule. The Info callout in evals.mdx uses a bold label ("Rollout Status:") which is also prohibited.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. Scores are a single overall judgment about the whole PR — not per file.

Overall vibe: Both files are substantively solid — the billing explanation in plans.mdx is clear and well-organized with good examples, and evals.mdx is a genuinely thorough feature reference. The main drag is a handful of mechanical style violations (British spellings, callout formatting rules) and one real contradiction on the pricing change date that needs resolving before this ships.

🔧 Issues (8)
  • admin/subscriptions/plans.mdx:8 — Date "As of 1 September 2025" contradicts admin/subscriptions/new-pricing.mdx:7 which says "As of 8 September 2025". One of these is wrong.

  • admin/subscriptions/plans.mdx:14 — Link text "here" violates the descriptive link text rule. Change to something like: [read the pricing changes FAQ](/admin/subscriptions/new-pricing).

  • admin/subscriptions/plans.mdx:157 — Heading ## Cancelling your subscription uses British spelling. American English: ## Canceling your subscription. Same issue at line 353 (old billing tab).

  • admin/subscriptions/plans.mdx:167 — "you've cancelled successfully" → "canceled". Same at lines 364–365 (old billing tab) and line 371.

  • admin/subscriptions/plans.mdx:159 — "if you are an organization admin" uses lowercase "organization". The rest of the page (e.g. lines 81, 82, 305) uses "Organization" (capitalized product term). Change to "if you are an Organization admin".

  • build/agents/build-your-agent/evals.mdx:8<Info> callout opens with the bold label **Rollout Status**:. CLAUDE.md prohibits bold labels inside callouts. Remove the label — the callout type already signals "note this". Just start with the sentence: "Evals is rolling out progressively, starting with Enterprise customers…"

  • build/agents/build-your-agent/evals.mdx:245**Credits** | Credits consumed for this scenario in the Scenario results table. For customers on new billing, the platform uses "Actions" and "Vendor Credits" — "Credits" is legacy terminology. Consider adding a parenthetical or a note clarifying what this column shows on each billing type, or verifying whether this UI label actually differs per billing plan.

  • admin/subscriptions/plans.mdx:7–15 — The <Warning> callout contains four paragraphs, bold text, and an embedded link. CLAUDE.md requires callouts to be a single short paragraph with no bold labels or multi-line content. See component suggestions below.

🧩 Component suggestions (2)
  • admin/subscriptions/plans.mdx:7–15 — The <Warning> callout violates the single-short-paragraph rule. Trim it to one sentence that states the core action required (e.g., "Our billing model changed in September 2025 — use the tabs below to find guidance for your plan."), then move the rollover detail, the old-vs-new-billing distinction explanation, and the FAQ link into a short prose paragraph immediately after the tabs open. This also fixes the "here" link text issue.

  • build/agents/build-your-agent/evals.mdx:7–9 — Once the bold label is removed (see Issues), this callout reads fine as a single-paragraph <Info>. No further change needed — just drop **Rollout Status**: from the start.

⚠️ Contradictions (1)
  • admin/subscriptions/plans.mdx:8 says the pricing change happened "As of 1 September 2025"; admin/subscriptions/new-pricing.mdx:7 says "As of 8 September 2025". Both pages are describing the same event. Align the date.
🔋 Credit usage
Item Count
Files reviewed 2
Context pages read 2
Total lines processed ~1,045

Files read: admin/subscriptions/plans.mdx (413 lines), build/agents/build-your-agent/evals.mdx (416 lines), admin/subscriptions/new-pricing.mdx (190 lines), build/agents/build-your-agent/build-overview.mdx (26 lines)

@jordanc-relevanceai jordanc-relevanceai marked this pull request as draft July 1, 2026 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-drafter Documentation drafted by Claude

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant