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.
Each grant or purchase expires 30 days after it is added. Kendr spends the credits closest to expiration first.
Open Billing & credits or the account overview. The displayed wallet balance is the source of truth for new requests.
Plans and credit packages
The standard packages below are prepaid wallet top-ups. The Billing screen shows the active package names, credits, currency, and final price available to your account before you pay.
| Package | Credits | Listed price | Best for |
|---|---|---|---|
| Starter 1500 | 1,500 | US$5 | Trying Kendr and light search or model usage. |
| Growth 3500 | 3,500 | US$10 | Regular individual work and mixed capabilities. |
| Scale 11000 | 11,000 | US$25 | Heavier activity and ongoing projects. |
| Enterprise 50000 | 50,000 | US$100 | Production-scale teams and higher-volume usage. |
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.
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://kendr.org/api/me/billing/summary \ -H "X-Kendr-Session: $KENDR_SESSION"
List current model rates
curl https://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?
Yes. Each credit grant or purchase expires 30 days after it is added, and Kendr uses the credits closest to expiration first.
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.