docs(kai): add Kai Pricing and Limits page

[KaroEverling]

Jira issue(s): n/a — Linear AI-3627, AI-3738

Kai goes GA on 15 September 2026 and starts consuming PPU credits. Today the docs say nothing about it: no page in kai/ mentions PPUs, credits, billing or cost, and the Time credits table in Project Limits has no Kai row.

Changes:

• New page kai/pricing — how Kai is billed, where project spend is tracked, how Organization Admins set project and per-user limits
• Nav entry under Kai, sidebar regenerated via npm run gen:sidebar
• Two screenshots in public/kai/

---

@davidesner — draft, needs your eyes on the facts before it goes further. Specific things I could not verify:

1. Screenshots are mockups, not product. CLAUDE.md says doc screenshots must be captured against a logged-in browser and never fabricated. Both images here are renders of a copy mockup, standing in until keboola/ui#8172 is on canary. Must be replaced before merge.

2. There may be a guardrail against this page. CLAUDE.md, Docs revamp process: "don't document pricing / in-app Kai-toggle / semantic layer". Possibly scoped to an earlier revamp — please confirm.

3. Unverified facts:

• The Settings → Usage path for a user's own percentage (from AI-3460, not seen built)
• That a custom per-user limit survives a change to the default
• That "other users" see the page read-only, vs only specific project roles

4. Deliberately left out:

• Organization budget — designed in AI-3738 but not built, so not documented
• The default per-user limit value — still pending @petr.hunka on AI-3627
• Cost-per-conversation tables — parked until the Model A/B conversion is settled
• Two image slots for Project Consumption and the 80% chat indicator, pending real captures

Kai is also still missing from the Time credits table in management/project/limits. Happy to add that row here or in a separate PR.

[vercel]

@KaroEverling is attempting to deploy a commit to the Keboola Engineering Team on Vercel.

A member of the Team first needs to authorize it.

[KaroEverling]

Correction to point 3 in the description: I listed Settings → Usage as an unverified path. There is no such path, and it is not on the page — it dropped out when the section was restructured into Kai Project Consumption and User Usage in Chat.

The only navigation paths the page states are Settings → Kai Agent → Kai spend limits and Settings → Kai Agent, both for the admin settings.

That leaves an open question rather than an error: where does a user see their own usage as a percentage? The page currently says only that an indicator appears in the chat panel at 80%. If there is a numeric view somewhere, it should be named here; if there isn't one, the 80% indicator is the only feedback a user gets before being stopped.

The remaining unverified facts in point 3 still stand.

[KaroEverling]

Sequencing note: #1104 (Kai chat controls) should merge before this one.

It leaves the Rate Limits section in kai/getting-started untouched, because the beta caps it describes are correct until 15 September. Once this PR lands and /kai/pricing/ exists, that section should be replaced with a pointer to it, so limits are documented in one place rather than two.

[keboola-pr-reviewer-bot]

Verdict: needs_human (risk 3/5) · profile connection-docs

Escalating: this documents Kai's unshipped GA billing, a gate-1 unshipped-feature failure.

Concerns:

• src/content/docs/kai/pricing.md: Documents unshipped Kai GA (15 Sep 2026); implementing UI keboola/ui#8172 unmerged.
• src/content/docs/kai/pricing.md: Prose states future rollout date: 'generally available on 15 September 2026'.
• public/kai/kai-spend-limits.png: Screenshots are mockups of unbuilt UI, not real product captures.

Suggested reviewers: @keboola/docs

[davidesner]

Superseded by #1105.

This PR was opened from a fork branch (KaroEverling:docs/kai-pricing), which we can't push follow-up commits to from the main repo. #1105 is the same work continued on a branch in keboola/connection-docs — your commit bb2e1e7 is carried over unchanged and still attributed to you, with the billing-wording follow-ups on top.

Nothing is lost here; please review #1105 instead. Sorry for the shuffle.