docs: update billing usage terminology

[TheFactoriousDROID]

Diff stats

File	+	-	Rationale
docs/pricing.mdx	23	23	Replace billing terminology with Rate Limits for plan caps, Usage Limits for configurable cost controls, and Factory Standard Credits for billing units.
docs/reference/analytics-api.mdx	11	11	Describe credit consumption while preserving existing /tokens and billable_tokens API identifiers.
docs/reference/cli-reference.mdx	1	1	Make /cost description unit-neutral.
docs/guides/power-user/token-efficiency.mdx	1	1	Avoid implying /cost only reports raw token usage.
docs/changelog/release-notes.mdx	19	19	Align historical billing, limit, multiplier, and preserved-token wording with current terminology.

What

Standardize billing terminology

• Uses Factory Standard Credits where the copy refers to the billing unit formerly surfaced as Billable Tokens.
• Uses Rate Limits where the copy refers to Factory-imposed plan/product caps, fallback behavior, Droid Core pools, provider throttling, or rate-limit notifications.
• Uses Usage Limits where the copy refers to self-imposed cost controls that prevent credit spend from moving too fast, including global/user/admin-configured limits.
• Uses broader usage or consumption where the copy is discussing spend/activity in general and does not need to name the unit.
• Uses Model Multiplier / Multiplier for model pricing multipliers rather than token multipliers.

Preserve valid token wording

This PR intentionally preserves token when it refers to non-billing concepts:

• Raw LLM/model accounting: input tokens, output tokens, cache read/write tokens, thinking tokens, context token limits, and token usage breakdowns such as Mission Control worker-level raw usage.
• Public API/schema identifiers: /tokens, billable_tokens, input_tokens, and output_tokens remain unchanged because they are existing contract names. The prose now explains billable_tokens as Factory Standard Credits consumed.
• Auth and security: API tokens, OAuth tokens, bearer tokens, GitHub tokens, SCIM tokens, and secret-scanning examples remain unchanged.
• Intentional rename history: release notes now say Billable Tokens renamed to Factory Standard Credits because that entry is documenting the rename itself.
• Unrelated product language: design tokens and benchmark token usage remain unchanged where applicable.

Keep this PR focused

• Drops Japanese docs changes for this pass so reviewers can evaluate the English public-facing terminology clearly.

Risk / impact

• Docs-only change; no product behavior or API contracts change.
• Low reader-facing risk: the main nuance is that some API identifiers still include tokens, because they are public contract names. The surrounding prose now explains their current billing meaning.
• No security or privacy-sensitive content added.

Testing

• python3 ~/.factory/skills/apply-pr-standards/scripts/validate-pr-files.py
• git diff --check
• cd docs && fnm exec --using v22.22.0 npx -y mintlify@4.2.529 validate
• cd docs && fnm exec --using v22.22.0 npx -y mintlify@4.2.529 broken-links --check-redirects

[mintlify]

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

Project	Status	Preview	Updated (UTC)
factory	🟢 Ready	View Preview	May 9, 2026, 12:43 AM

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