One credit balance across Kendr.
Your Kendr wallet is shared across Cloud, Desktop, and API usage. Add a prepaid credit package when you need it, see the price before checkout, and review completed requests and purchases from your account.
How Kendr credits work
The same account balance is available in the web app, Kendr Desktop, and your API integrations.
Different models and capabilities can use different amounts. Check the Models screen for current rates.
A completed request records its credit charge in your usage history. Failed work is not charged as a successful request.
Credits added by a completed paid package purchase never expire. Promotional credits can have a grant-specific expiry, shown in wallet activity; Kendr spends expiring lots before non-expiring purchased lots.
Open Billing & credits or the account overview. The displayed wallet balance is the source of truth for new requests.
One 5% markup for model usage
Kendr applies one fixed 5% markup to the configured provider cost for model usage. The same rate applies to exact model aliases and Kendr managed routing; the selected Kendr Route does not change the percentage.
| Model path | Markup policy | What to use in your product |
|---|---|---|
| Exact model alias | Provider cost + 5% | Current rates from the model catalog and the settled kendr_usage receipt. |
| Kendr managed routing | Selected provider cost + 5% | The routing receipt for the selected alias plus the settled kendr_usage charge. |
Search, media, knowledge-base, meeting, and other non-model capabilities can have their own published unit rates. Do not infer those prices from the model markup. For every completed request, the integer microcredit charge in the returned usage record is the settlement source of truth.
Plans and credit packages
Kendr offers 30-day passes and prepaid wallet top-ups. Both use the same credit balance for actual settled usage across the web, desktop app, and API. A pass releases its credits weekly; unused weekly credits expire at the reset, and the pass does not renew by itself.
| Pass | Price per 30 days | Weekly credits | Credits per pass |
|---|---|---|---|
| Plus | $10 | 1,250 | 5,000 |
| Pro | $25 | 3,125 | 12,500 |
| Max | $80 | 11,250 | 45,000 |
| Superman | $150 | 23,500 | 94,000 |
Pay-as-you-go top-ups start at 350 credits per USD. The complete volume schedule is 400 credits per USD from $10, 450 credits per USD from $50, and 500 credits per USD from $100.
Verified students and staff of approved institutions can also use the School plan: a $5 pass for 30 days (list price $20) that grants a fresh allowance of credits every week. Weekly credits reset each week rather than rolling over, and the pass is renewed by hand rather than billed as a subscription. Sign in with your institution email and activate it from the School plan page; institutions apply at kendr.org/institutions.
| Available top-up | Credits | USD rate |
|---|---|---|
| Top-up 1750 | 1,750 | $5 at 350 credits / USD |
| Top-up 4000 | 4,000 | $10 at 400 credits / USD |
| Top-up 10000 | 10,000 | $25 at 400 credits / USD |
| Top-up 50000 | 50,000 | $100 at 500 credits / USD |
Top-up prices are set per country, so the amount you see depends on your billing country. The Billing screen shows the active package names, credits, currency, and final price available to your account before you pay.
Each package has its own price per supported currency. Kendr resolves your currency from your billing country, which you can set on the Billing screen. When Kendr cannot bill in your local currency, prices are shown and charged in the default currency instead — the currency displayed is always the currency charged.
Package availability and pricing can change. Always rely on the amount, currency, taxes, and payment details displayed in your Kendr checkout before confirming.
How to add credits
- 1Sign inGo to kendr.org/login and verify the email address that owns the wallet.
- 2Open Billing & creditsFrom your account navigation, select Wallet & credits, or open kendr.org/app/billing.
- 3Choose a packageCompare the number of credits and displayed price. Select the package that fits your expected usage.
- 4Complete secure checkoutReview the payment amount and complete the Razorpay checkout. Do not refresh or close the page while the payment is being confirmed.
- 5Confirm the balanceAfter successful confirmation, Kendr adds the credits to your wallet and refreshes the displayed balance.
Understand what uses credits
Credit usage depends on the Kendr capability you run. Model calls can be based on input, cached input, and output tokens; searches, media analysis, knowledge-base work, and other surfaces can have their own displayed cost.
- Open Models to compare the current input and output rates for available model aliases.
- Use the model catalog at runtime because enabled aliases, capabilities, and displayed rates can change.
- Review the estimate shown before a request when the product provides one. Some requests temporarily reserve enough balance to finish safely.
- Open Usage to see request status, model, token volume, credits charged, and date.
- Use Purchases to see package orders, credit amount, payment amount, status, and date.
Use the estimate and final Kendr usage record rather than trying to calculate a provider-specific bill yourself. The usage record is the source of truth for completed API calls.
Kendr Notetaker AI credit usage
Kendr Notetaker AI uses a refundable reservation before a bot joins. The reservation covers the expected meeting duration, a safety buffer, meeting capture, and the paid-transcription fallback. Kendr settles it from signed provider usage when the call ends and releases the unused amount.
Charged from the provider's actual billable capture seconds, including billable time before a failed call ends when the provider reports it.
Native Meet, Zoom, or Teams captions add no transcription charge. If captions are unavailable or empty, only the selected paid fallback's actual transcription seconds are charged.
The final text transcript is sent to the configured Kendr model. Input, cached-input, and output tokens are charged through the normal model-usage path.
Final Kendr credits equal capture credits plus any fallback-transcription credits plus the actual minutes-and-tasks model credits.
Kendr asks the capture worker to use native meeting captions first. Webex and calls whose captions fail use the configured paid fallback. Raw audio is not sent to the minutes model.
A definite failure before recording releases the full reservation. If a provider response is ambiguous, Kendr keeps the reservation while reconciling the same idempotent bot request. A failure after recording settles any signed billable usage and releases the remainder.
What happens when the balance is low
- If the wallet cannot cover a required reservation, the request stops before chargeable execution and reports that more credits are needed.
- Add a package from Billing & credits, confirm the new balance, and then retry the task.
- For API integrations, treat HTTP 402 as an account-action state. Do not retry it in a tight loop.
- A request that fails after a temporary reservation should release that reservation rather than appear as a completed charge.
Purchase status and payment questions
| Status | What to do |
|---|---|
| Completed or paid | Refresh Billing & credits. The purchased credits should appear in the wallet. |
| Pending | Wait for the payment confirmation and refresh Purchases. Avoid starting the same payment repeatedly. |
| Failed | No credits were added. Check the payment message, then begin a new checkout if you still want the package. |
| Payment succeeded but credits are missing | Keep the payment reference and contact Kendr support with your account email, package, amount, approximate time, and order reference. Never send full card details. |
Billing in an API integration
API traffic uses the same shared wallet. There is no second API-only balance.
Read customer billing summary
curl https://api.kendr.org/api/me/billing/summary \ -H "X-Kendr-Session: $KENDR_SESSION"
List current model rates
curl https://api.kendr.org/v1/models \ -H "Authorization: Bearer $KENDR_API_KEY"
- Use the model catalog at runtime because availability and rates can change.
- Read returned usage fields for the authoritative charge on a completed request.
- Use idempotency keys on chargeable model requests so safe retries do not become separate logical operations.
- Alert an account owner before the balance becomes too low for normal traffic.
Common questions
Do credits expire?
Purchased credits never expire. Promotional credits, including starter, referral, or periodic grants, may expire according to the policy shown when that grant is issued. Kendr spends expiring lots before non-expiring purchased lots.
Is there a separate API subscription?
No. API requests use the same Kendr wallet as the web and desktop experiences.
Can I see exactly what was charged?
Yes. Open Usage for request-level token and credit information, and Purchases for package payment history.
Should I share my payment details with support?
No. Share the Kendr order or payment reference, package, amount, time, and account email. Never send a full card number, security code, password, or one-time sign-in code.