Skip to content
LLMFLUX

Account

Billing and credits

Use the dashboard for the currently configured plans, limits and enabled payment methods.

Configured plans

Open Billing to see actual plan prices and supported checkout options. Prices and limits are configuration-backed; this guide deliberately does not hard-code them. Plans may enforce spend windows independently of your positive account balance.

Payment confirmation

The server creates a pending payment and verifies it with the configured payment gateway. A browser redirect or client-side success message does not credit an account. Confirmed payments are credited once inside a database transaction with a row lock and status guard.

KHQR/ABA and Binance checkout integrations exist in the backend, but only enabled and correctly configured methods are available. Do not assume either method is always enabled. Do not retry checkout creation repeatedly if a payment is already pending.

Transaction history

The authenticated payment-history endpoint returns up to the 50 newest account transactions, including transaction ID, amount in USD, credited tokens, real status, creation time and paid time when available. History export and invoice routes require the same account session. View history through the dashboard rather than sharing session cookies or calling account endpoints with an inference API key.

Student and startup grants (Launchpad)

Students, educators, researchers, and early-stage startups can apply for Launchpad credit grants at the Launchpad portal. Grants are credits on your LLMFlux account — amounts and expiry are set by the review team, never chosen by applicants. Track your application status there; only public reviewer messages are shown to applicants. Full eligibility, the application flow and what happens after approval are on the Launchpad grants guide. See also the marketing pricing for paid plans.

Balance and support

Credits shows your account balance. A zero balance causes inference to return 402 quota_exhausted. A streaming request holds back at most the smaller of the configured reserve cap and half your balance while it runs, and the gateway returns whatever that request did not bill when it ends. If payment confirmation is delayed, retain your transaction ID and contact Support; never include API keys in a support message.