How TripTended Assistant Credits Work

By the TripTended team · Product rules checked October 30, 2026

An assistant task can finish before its credit usage is settled. If your available balance has fallen while a request says Checking usage, first distinguish the amount reserved for that request from the amount finally charged. Starting the task again will not resolve that distinction.

This guide helps you read one request alongside your allowance balance, work through an illustrative calculation and prepare a useful support note. You need access to the workspace’s Plans & billing page and the request you are checking. Use the pricing page for current plan allowances, or the trial guide for trial eligibility and expiry.

1. Record the workspace and allowance period

Open Plans & billing in the workspace where you made the request. Record the displayed period end, the time of your check and these three figures together:

• Available: credits still available in the current allowance period.
• Used: credits charged after any recorded credit returns.
• Reserved: credits held for work in progress or awaiting a usage check. A reservation reduces what is available while it remains open.

For a metered allowance, the relationship is:

Available = allowance granted − used − reserved.

Check the allowance that applies to that workspace and period. Do not substitute another workspace’s plan, an earlier trial allowance or the first day of a calendar month for the period you are reviewing. Subscription payments, new Trip allowances and assistant credits are different measures; a dollar subscription amount is not a credit balance.

If the page says Loading…, Unavailable, Not metered or No active allowance, record that message instead of writing zero. Where offered, Retry credits reloads credit information. It does not run the assistant task again.

2. Match the request before interpreting its charge

Under Assistant usage, match the request title and displayed UTC timestamp with the task you meant to inspect. Then read its credit label separately from the task’s result. A saved draft can exist while usage is still being checked; a completed task does not by itself prove that its credit charge is final.

The table shortens the labels; the page also displays each amount. Refresh usage reloads the credit summary and recent history. It does not create another assistant request.

The list contains up to 20 recent requests, and visibility depends on your access. It is not a complete statement of every request in the current allowance period. Do not add only the visible rows and assume their sum must equal the workspace’s Used total. A workspace owner can help check a history-visibility question; retain the discrepancy if the records you can see are insufficient.

3. Reconcile a fictional reservation and settlement

The following is an arithmetic exercise, not a customer record, a task-price estimate or a promise about how many requests a plan supports. Assume one allowance period with 100 credits granted, no other balance movements and one task holding 10 credits. Other settled requests have already used 12.4 credits.

The task adds 3.2 to Used, and its 10-credit reservation closes. The remaining 6.8 becomes available again within that same period. This is the unused part of a hold, not another allowance grant or a cash refund. Do not subtract both the original 10-credit reservation and the final 3.2-credit charge after settlement.

Now change just one assumption: the request still says 10 reserved · Checking usage. You do not yet have the 3.2-credit settlement in that version of the exercise, so the available balance remains 77.6. Record the pending state rather than predicting the final charge.

Real requests vary. Use observed settled usage when building an assistant workload budget, and keep pending or estimated entries identified separately. A reservation is not a fixed price for a task type.

4. Handle a pending check, failure or later return

For managed assistant tasks with missing usage, TripTended retains the reservation while it checks for the missing information. If usage is still missing after the required checks, it can settle at the authorized reserved amount and label the charge Estimated. The checks depend on completed reconciliation work, so elapsed time alone is not proof that settlement has occurred.

If later usage supports a lower charge, the system records a credit return against the original period. Read the displayed charge and returned-credit note together; do not move the return into a new period in your own calculation or interpret it as a refund of your software subscription payment.

After a failed, stopped or uncertain task, check both the saved result and the actual usage label. A No credits charged entry is evidence of that request’s waiver; a spinner, error message or stop action is not. Cancellation need not stop provider work immediately. If the result is unclear, use the draft recovery guide to inspect saved work before deciding whether another request is needed.

If an amount still cannot be explained, preserve the request and period details below. Avoid repeated new generations as a way to test the balance: each new request is separate work and makes the original discrepancy harder to isolate.

5. Keep a note someone else can reconcile

Copy this suggested note into your private workspace notes. Fill in observed values; write “not visible” or “not yet settled” where appropriate. Keep screenshots within your approved support channel and remove client details that are unrelated to the credit question.

Workspace and allowance period/end:
Checked at (date, time and timezone):
Request title, UTC time and reference if available:
Task result/status observed:
Available / used / reserved at the same check:
Usage label, amount and any estimated/returned note:
Expected calculation and the unexplained difference:
Next action, responsible person and follow-up time:

For the fictional pending example, the balance line would read “77.6 / 12.4 / 10”; the usage line would read “10 reserved · Checking usage.” The next action would be to refresh that request’s usage later, not report a final 10-credit charge. If the label later changes, append the new observation and its time so the earlier calculation remains understandable.

For an unresolved account question, contact the TripTended team with this note. Never include passwords, session cookies or API keys. Credit accounting does not confirm a supplier booking, a traveler payment or a Trip Ready decision; those require their own evidence and review.

Prepared with AI assistance and edited against TripTended’s documented billing rules and current implementation. The calculations are fictional; this article does not report a live customer account test.

Continue with the workflow guides, current pricing and allowances, or TripTended overview.