Annual Plans Can Be Purchased
Choosing yearly billing on the Plans tab now carries that choice through to checkout. Selecting a yearly plan previously opened a monthly checkout, so the annual price shown on the card was not the one you were offered at payment.
The interval you picked is also preserved if you come back from checkout, so the page you return to matches the plan you were looking at.
Returning From Checkout Reflects What Actually Happened
The billing page now confirms a completed purchase from your subscription itself rather than from the address you were returned to. Closing the tab, refreshing, or a slow confirmation no longer produces a message that disagrees with what was charged.
If confirmation is still in progress, the page says so and keeps checking instead of guessing.
Usage and Credit Are Reported Honestly
Billing overview no longer shows a starter credit balance or compute allowance while those figures are still loading or could not be retrieved. Unavailable figures are now named as unavailable, with a way to retry, rather than being displayed as a real balance or as zero.
Subscription management stays available even when usage figures cannot be loaded.
Token and Cost Totals Are Counted Once
Trace totals for tokens and cost are now attributed once per completion.
Everstack records a span for the request it handles and a span for the provider call underneath it, and both carry the same usage figures. Trace-level totals previously summed both, which inflated the tokens and cost reported for a single completion, with the largest effect on agent runs where the pattern repeats each turn.
Distinct provider calls are still added together, so retries, fallbacks and multi-turn agent runs continue to accumulate as you would expect. Traces that report usage in other ways are unaffected.
Totals shown for existing traces will decrease. This corrects the reported figure. It does not change what you were billed.
Provider Credentials Are Checked When You Save Them
Provider credentials are now checked against the shape that provider expects when you save them, so a mistyped or truncated paste is caught at setup with a message naming the expected format, instead of surfacing later as failed requests.
Credentials for providers with a custom base URL are accepted as-is, since a proxy or gateway can legitimately use a different format.