AI credits
How prepaid AI credits work in the Sinera Platform, from balance and holds to charges, releases and the credit ledger.
AI credits are prepaid balance that your organization spends when it uses AI features in Sinera apps. The Credits screen at platform.sinera.io shows the balance, how it is split, and every change to it.
Preview
The credit model is a proposal
The rules on this page describe a design that has not been approved for launch. Adding credits depends on a payment provider that is not connected yet (see Plans and billing). Details such as refund terms, expiry and timeout handling are still open and may change.
What credits are, and what they are not
- Credits pay for AI work done inside Sinera apps, such as requests made through Sinera App or the Sinera agent.
- Credits belong to an organization wallet, unless a wallet is sponsored for one member.
- Credits are not SIN and are not a token. You cannot send them to a wallet address or trade them. SIN is a separate planned token. See Tokenomics.
- Sinera decides what a request costs on its servers. Your browser never sets the amount charged, the model, or the price.
Read your balance
The Wallet panel shows two headline numbers.
| Figure | Meaning |
|---|---|
| Available | Credits you can spend now. |
| On hold | Credits reserved for requests that are still running. |
Below them, Credit types splits the balance into buckets, each with its own held amount.
| Bucket | Where the credits come from |
|---|---|
| Subscription credits | Credits included with a plan. |
| Recharge credits | Credits you added with a payment. |
| Promotional credits | Credits granted as a promotion. |
| Sponsored credits | Credits sponsored for an individual member. |
If a bucket has an expiry date, the panel shows "Credits expire on" with the date. A new wallet reads "No credits in this wallet yet".
People who can manage billing also see Sponsored member wallets, one row per member with status, expiry, on-hold and available credits.
How a request uses credits
Credits are never taken blindly. Each AI request follows the same path, and every step is recorded.
| State | What happened | Effect on credits |
|---|---|---|
| Quoted | Sinera checked your permission and set a maximum cost for the request. | None. |
| Reserved | You have enough credits, so that maximum is held. | Moves from Available to On hold. |
| Dispatched | The request was sent to the AI provider. | Held credits stay held. |
| Settled | The result and its real usage were verified. | You are charged the actual usage, never more than the held maximum. The unused part of the hold is released. |
| Released | The request was refused or cancelled before it was sent. | The whole hold returns to Available. |
| Reconciling | The request was sent but the outcome or usage is unknown, for example after a timeout. | The hold stays while Sinera checks, then it settles or is released. |
Credits are held before any provider is called, so a request cannot spend more than you have. A request settles once only, so retries do not charge twice.
Which failures are not charged
| Event | Billing result |
|---|---|
| Not authorized, invalid input, or over budget before sending | Not charged. The provider is not called. |
| Not enough credits | Rejected before sending. Not charged. |
| Error after the hold but before the provider was called | Hold released. Not charged. |
| Same request sent twice with the same key | The first result is returned. No second hold or charge. |
| Timeout after sending | Not assumed free. It goes to Reconciling. |
| You cancel a streaming answer | Verified usage so far is charged. If usage is unclear, it goes to Reconciling. |
| Provider finished but you received nothing | Refund depends on the terms, which are not final. A refund is a separate entry. |
A hold in Reconciling cannot last forever. When the review ends, Sinera settles it if there is evidence of use, or releases it to you if usage cannot be verified.
Credit ledger
The Ledger lists every change to the wallet, newest first. Each row shows date, type, credit type, a description, the amount and the balance available after the change.
| Type | Meaning |
|---|---|
| Credit added | Credits granted, for example after a confirmed payment. |
| Charge | Credits spent on usage. |
| Funds held | A hold placed for a running request. |
| Hold released | A hold returned to your balance. |
| Refund | A charge given back. |
| Credit reversed | Credits taken back, for example after a payment reversal. |
| Balance adjusted | A manual correction. |
| Transfer received, Transfer sent | Credits moved between wallets. |
Use Filter by type to narrow the list and Load older to fetch earlier entries. A new wallet reads "No credit activity yet". A failed read shows "Ledger could not be loaded" with Try again.
The ledger is the source of truth for your balance. Entries are never edited or deleted. A refund, reversal or correction is added as a new entry, with a reason and the identity of whoever approved it, so you can trace any balance back to its events.
Add credits
The Add credits panel lets you choose an amount in USD and continue to a payment provider's page. Credits are added once the payment is confirmed. Today it answers "Payments are not connected yet" and nothing is charged. See Plans and billing.