IN ENGLISH · API DOCS

Service credit: the API success-rate commitment

For each vendor family and each month of the Persian (Jalali) calendar in Tehran time, from Azar 1405 on, the success rate of requests through the gateway is measured. Only the failures that were ours count in this rate, not a vendor's own outage or error. The target is 99.5%. When a month's rate is under the target, a percentage of what your wallet paid for that vendor's calls in that month is credited to your wallet. Our team reviews each month's figures before anything is paid, and the credit is paid within 5 days of the month's end, with no request from you. The commitment is about success rate: not latency, and not output quality.

Last updated:

[01]SERVICE CREDIT

The credit tiers

Credit by the month's success rate
The month's success rateCredit
Under 99.5%Credit:10% of that month's spend on that vendor
Under 98%Credit:15% of that month's spend on that vendor
Under 95%Credit:20% of that month's spend on that vendor
Under 90%Credit:25% of that month's spend on that vendor
  • A rate exactly at a threshold is not under it. The published rate has two decimals and is always rounded down.
  • The percentage applies to what your wallet paid for that vendor's calls made in that month, less the refunds of those calls. Usage paid by a plan's credit or by gift credit is not counted.
  • The credit can be spent on every model, does not expire, and cannot be withdrawn or refunded.
[02]SERVICE CREDIT

How it is measured

  • A month is a Persian (Jalali) calendar month in Tehran time, from the first instant of its first day to the end of its last. The commitment starts with Azar 1405; months before it are not covered.
  • Success and failure are read as on the status page: a success is a 2xx; a failure is a 5xx or a request with no response. A 4xx caused by the request (a malformed body, an unknown model, your own rate limit, an empty wallet) is neither a failure nor in the denominator.
  • The credit rate counts only the failures that were ours: an error of the gateway itself or of our own servers and routes, and a vendor error caused by our own account with that vendor (our credit or quota there ran out, our key or account there was revoked or suspended, or we hit our own rate limit there). A vendor's own outage or error, while our account with it is in good standing, is neither a failure nor in the denominator, and neither is a request whose connection the vendor itself broke or refused. A cut made by our own timer (our deadline, such as the wait for the first reply) is counted as our failure. So the credit rate is successes ÷ (successes + our failures). On this page an eligible request is one in the credit rate's denominator.
  • The service credit page shows both rates for each vendor and each closed month: the success rate (the status page's) and the credit rate. The credit rate decides the tier and the credit.
  • An account needs at least 100 eligible requests to that vendor in the month, and must be active when the credit is paid.
  • A vendor family with fewer than 1,000 eligible requests from all customers in the month is not assessed, and the page says so.
[03]SERVICE CREDIT

Payment

  • After a month closes, our team reviews its figures (each vendor's rate and each account's credit), and the credit is paid to the wallet after that review, within 5 days of the month's end. You do not have to ask.
  • Until a month has been reviewed, no credit of it is shown. A row that is pending is a credit that will be paid as things stand.
  • The commitment with its current figures, and each vendor's rate in the closed months, are on the service credit page; your own credits are in the dashboard's service credit history and in GET /v1/sla/credits.
[04]SERVICE CREDIT

Reading your credits: GET /v1/sla/credits

GET /v1/sla/creditscurl
curl "https://1xai.ir/v1/sla/credits?limit=50" \
  -H "Authorization: Bearer 1xai-..."
  • The answer: active (the commitment is in force now), total_paid_toman (the sum of this page's paid rows) and credits, newest month first.
  • Each row is one month and one vendor: period (the Jalali month, YYYY-MM), provider, rate_pct, status_rate_pct, eligible_requests, ok_requests, spend_toman, credit_pct, credit_toman, state (paid or pending), paid_at and wallet_transaction_id.
  • In each row, rate_pct, eligible_requests and ok_requests are the credit rate's (see How it is measured), and credit_pct follows from that rate; the status page's rate for the same month and vendor is status_rate_pct.
  • credit_toman is spend_toman × credit_pct ÷ 100, rounded down.
  • A month that owes you nothing has no row. The payment's transaction is in GET /v1/wallet/transactions with kind gift.
  • Credits belong to the paying account and are computed on the whole company's wallet spend, not per workspace, so a company workspace key gets 403 with code forbidden on this route.

1xAi is an independent gateway. It is not affiliated with, endorsed by, or a reseller for OpenAI, Anthropic, Google, DeepSeek, xAI, Moonshot AI, Z.ai, Alibaba Qwen, MiniMax or Tencent Hunyuan. Requests are relayed upstream rather than answered by models of our own, so each provider's own usage policies apply to what their models will and will not do, and their model availability is theirs to change. Current reachability is published on the status page.