Skip to main content
GET
Get your credit balance

Authorizations

Authorization
string
header
required

API key issued from the developer dashboard. Pass as Authorization: Bearer vq_key_...

Response

Current spendable balance for the calling key's account.

Spendable credit balance for the calling API key's account.

creditsRemaining
number
required

Credits you can actually spend right now. Deliberately the same field name that metered responses return, so one name means one thing across the API.

Derived from your live credit buckets under the same expiry rule the billing path applies, so it never promises credits a call would refuse to spend.

Example:

103039

usdRemaining
number
required

creditsRemaining in USD, at the published conversion rate (1 credit = $0.01). Provided so you do not have to hardcode the rate; GET /api/v1/api-credits/pricing is its source of truth.

Example:

1030.39

totalPurchased
number
required

Lifetime credits added to this account.

Example:

150000

totalConsumed
number
required

Lifetime credits spent by this account.

Example:

46961

asOf
string<date-time>
required

When this balance was computed. The value is live, not cached, so this is the instant the buckets were read.

bySource
CreditSourceBreakdown · object[]

creditsRemaining split by funding source, and it always sums to it. Worth reading because the sources do not behave alike: subscription credits are use-it-or-lose-it at the period end, while payg credits you bought are durable and burn last.

nextExpiry
CreditExpiry · object | null

The soonest expiry across your credits, or null if none of them expire. Poll this to avoid silently forfeiting an allowance.

plan
string | null

Active API subscription tier, or null on pay-as-you-go. Also determines your rate-limit multiplier. Briefly cached, so a subscription change made seconds ago may not be reflected yet; creditsRemaining is always live.

Example:

"business"

rateLimit
CreditRateLimit · object | null

How fast this key may call, as opposed to how much it may spend. The two ceilings are independent: holding credits does not exempt you from these, and staying under these does not pay for a call.

These are the ceilings themselves, with your plan already applied, so you can size a client BEFORE issuing a request. The X-RateLimit-* headers on every response report the same ceilings plus your live headroom, and the two agree.

Last modified on September 18, 2026