AI generation API billing and credits

Every model has a per-generation credit cost, shown on its catalog page and in GET /v1/models (creditsPerGeneration). The estimated credits for a job are reserved when it is created and the actual credits are settled on completion.

• Plan credits — included with monthly plans (for example Mini: 750 credits/mo, Growth: 4,500 credits/mo, Starter: 10,000 credits/mo — see pricing for current plans), the lifetime plan (a finite one-time balance that does not expire), and one-time packs such as the Trial Pack (3,000 credits valid 7 days, one pack per week). Unused monthly credits remain available while the plan stays active; Trial Pack credits expire at the end of their 7-day window.
• Wallet balance — pay-as-you-go, no subscription. Deposits start at $10; credit value is fixed at 1 credit = $0.01. Each deposit is valid for 30 days after it is credited and is spent oldest-first; any unused balance is forfeited after that.
• Credit balance and ledger are visible at GET /v1/workspaces/:workspaceId/credits.

Monthly plans renew by invoice and include seats (active members), concurrent job limits, storage, and queue priority. A renewal invoice with a payment link is issued before each period ends, and new period credits are granted when it is paid. See the live pricing page for current plans: free.ind.in/pricing. Plan entitlements are returned in GET /v1/plans and enforced per workspace.

The wallet is a prepaid balance for workspaces without a subscription (or as an overflow). Deposit with POST /v1/wallet/top-ups:

curl -X POST https://free.ind.in/v1/wallet/top-ups \
  -H "Authorization: Bearer fi_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "workspaceId": "<workspace-id>",
    "amountUsd": 25
  }'

• Minimum deposit: $10. Deposits are processed through the payment provider and credited on confirmation.
• Balance: GET /v1/wallet; history: GET /v1/wallet/transactions and GET /v1/wallet/deposits.
• Expiry: each deposit is valid for 30 days after it is credited. Balance is spent oldest-first, and any unused part of a deposit is forfeited when its window ends.
• Wallet payments require a successful deposit before generating (wallet_pending_minimum otherwise).

By default generations bill plan credits. Pass "paymentMode": "wallet" in POST /v1/generations to pay from the wallet instead:

{
  "workspaceId": "<workspace-id>",
  "modelId": "<model-id>",
  "paymentMode": "wallet",
  "params": { "mode": "text_to_image", "prompt": "a red fox in snow" }
}

The estimated charge (credits × $0.01) is reserved before the job starts and settled on completion. If the reserved amount can't be covered, the request fails with wallet_insufficient_balance.

A job that the workspace cannot cover with plan credits or an active wallet can be paid for with a one-time checkout. Pass "paymentMode": "direct" plus a provider:

{
  "workspaceId": "<workspace-id>",
  "modelId": "<model-id>",
  "paymentMode": "direct",
  "provider": "cashfree",
  "tosAccepted": true,
  "params": { "mode": "text_to_image", "prompt": "a red fox in snow" }
}

• The response is 201 with the job in awaiting_payment and a payment object (checkoutUrl or Cashfree paymentSessionId).
• Credits and an active wallet always win: when either can cover the job, a direct request is downgraded to that mode and the response's paymentMode reports what was actually used.
• The price is admin-configured: max(ceil(credits × (1 + markup/100)), minimum-credits) × $0.01, surfaced on the insufficient_credits error details as directCredits / directChargeUsd.
• The job starts automatically once the gateway webhook confirms the payment; abandoned checkouts expire after the configured lifetime (default 60 minutes). Resume an unpaid checkout with POST /v1/generations/:id/payment (or POST /v1/runs/:id/payment for workflow runs).
• If a paid job fails before producing output, the paid amount is credited to the workspace wallet.

Track spend per workspace with GET /v1/usage — credits used, customer cost, generations, and output bytes, filterable by date range. Subscriptions and payments are managed via POST /v1/billing/checkout, POST /v1/billing/portal, and POST /v1/billing/cancel (dashboard-first; see API reference).

• Pricing
• Code examples — wallet-backed generation