Skip to main content
LaoZhang API is prepaid: you top up a balance in the console, and usage is deducted from that balance.

​
Top up your balance

  1. Sign in to the LaoZhang API console.
  2. Open the top-up page and choose one of the payment methods it shows.
  3. After the payment completes, confirm the new balance in the console before sending production traffic.
The payment processor handles your card or payment details. LaoZhang API does not store full card numbers or complete payment credentials.

​
Pricing and billing

  • Usage is billed by model, endpoint, token, request, media unit, or another unit shown in the console.
  • Prices, available models, rate limits, billing units, and credit rules may change, and emergency upstream changes may take effect immediately.
  • Do not use an upstream provider’s public price to predict a LaoZhang API bill. Budget with the model and pricing catalog, current console pricing, and representative call logs.

​
Enterprise payment, contracts, and invoices

For enterprise payment, contracts, invoices, volume usage, or custom quotes, contact the site owner or support. The documentation does not publish fixed discount tiers or thresholds. Provide:
  • company or team name;
  • expected models and endpoints;
  • estimated monthly usage or budget range;
  • contract, invoice, and payment requirements;
  • account email and desired activation date.
Email: hi@laozhang.ai Telegram: @laozhang_cn Do not send bank details, complete tax records, payment evidence, contracts, or other sensitive information in a public chat. Use a formal channel confirmed by the site owner or support.

​
Refunds and balance adjustments

Refunds follow section 6 of the Terms. Purchased credits and paid fees are generally non-refundable once purchased or consumed. A refund or balance adjustment may be reviewed where:
  • applicable law requires it;
  • LaoZhang API permanently discontinues a relevant paid service before credits can reasonably be used;
  • a material service failure caused by LaoZhang API prevents normal use for a significant period.
Eligibility, amount, payment-rail availability, fees, and timing are decided in an individual review. The documentation does not promise fixed processing times or fees. Refunds are not provided for violations of the Terms, abuse, fraud, sanctions or region restrictions, chargeback abuse, user integration errors, unsupported use cases, upstream-provider restrictions, or dissatisfaction with model output.

​
What to provide for a refund or invoice request

  • account email or username;
  • transaction time, amount, currency, and payment evidence;
  • related model, endpoint, call time, and error information;
  • reason for the request and expected resolution;
  • contract or invoice details required for enterprise purchasing.
Do not send complete API keys, passwords, or unrelated request content. For call issues, provide only redacted errors, timestamps, models, and request identifiers.