Skip to main content
Answers to the problems people run into most. If yours is not here, contact support.

​
Account and sign-in

Email support@fortytwo.network from your primary email, the address you sign in with.
Wallet (Web3) sign-in is not supported. Sign in with email.
By your primary email. Write from it, or include it in your message. Your primary email is on your Account page.
If you have not verified your email yet, verify it first: an unverified account cannot send API requests. Otherwise contact support. If you cannot sign in, email support@fortytwo.network from your registered email.
Use the export or delete options in the platform where they are available. Otherwise email legal@fortytwo.network.
Fortytwo accounts are for people aged 18 or older.

​
API

Check that you copied the whole key and that it was not revoked. A key is shown only once: if you lost it, create a new key in the platform and revoke the old one.
Revoke it in the platform now and create a new one. If you see usage you don’t recognise, contact support.
You sent more requests per minute or per hour than your tier allows. Wait for the number of seconds in the Retry-After header, then try again. Your limits are on the Tier and limits page.
Too many requests are running at the same time, or the network is busy. We also limit how many requests can run at the same time. This limit is not published, and it can change with the load on the network while we scale. Under high load you can get a 429 even when you are within your per-minute and per-hour limits. Wait for the Retry-After time and try again. Sending fewer requests at the same time helps.
A temporary problem on our side. Wait a short time and retry. After upstream_error or upstream_timeout, part of the first request may already be charged, and each retry is charged as a new request. Check API status on the platform Home page.
Check API status first. If it continues, use Contact support, topic API errors and latency. Include the time (UTC), the model, the error code and the request ID if you have one. Never include your key.
Check the model name. The current models are listed in the platform and on Models.
Your balance is used up. Buy credits on the Credits page and try again.
The account’s Monthly spend limit was reached. Raise or remove it on Credits, under Usage limits. It also resets on the 1st of the month.
This key’s Spend limit was reached. Raise it in API keys → Edit, or use another key.
A payment you made is disputed with your bank, so the credits from it are on hold and the rest of your balance is not enough to run requests. Add credits with another card on the Credits page. If you disputed the payment by mistake, ask your bank to withdraw the dispute.
The request has a field or a value the API does not accept. The API rejects unknown fields instead of ignoring them. Remove fields your tool or library adds that are not in the API reference, and check the values. If you send an earlier reply back in messages, remove its reasoning, reasoning_details and refusal fields.
You sent content the model does not accept, such as audio, video or a file. Send text, and images where the model accepts them.
The Content-Type header is missing or wrong. Send Content-Type: application/json.
The request did not finish uploading in time. Check your connection, or send less data — for example, send images by URL instead of inside the request.
The request or one of its images is too large. Send smaller images, or fewer of them.
No. Call it from your own server and keep the API key there. Browsers block the call, and a key in a web page can be stolen.
Start with Get access and Quickstart. The community may also help here, as general information.

​
Models

AI answers can be wrong. Please tell us through Feedback, type Models.
Use Report a security issue, area Model behavior and AI safety.

​
Limits and tiers

Use Request upgrade, not Support.
Upgrades are reviewed by our team. Send a request. An upgrade can take effect from the start of the next month or later.
Use the upgrade form and choose Enterprise API terms.

​
Billing and credits

Check the card or try another one. After a failed payment, Auto-reload turns off: turn it back on in Credits. Still stuck? Contact support, topic Billing and credits.
Wait a few minutes and refresh the Credits page. Still missing? Contact support, topic Billing and credits, with the date and amount.
Contact support first; it is usually the fastest way. If you dispute the payment with your bank, the credits from that payment are put on hold and the card can’t be used on Fortytwo until the bank decides. The rest of your balance stays available. Contacting us first does not affect your rights.
Stripe emails a receipt to your primary email after each purchase. You can also open Credits → Top-up history and press View on the purchase.
Purchased credits do not expire. Unused purchased credits are refunded when you close your account, minus any outstanding charges. For refunds and withdrawals, email legal@fortytwo.network.
For billing and account questions, contact that service first.

​
Safety

Use Report a security issue. Do not post it publicly. If you cannot use the form: security@fortytwo.network.
Do not click links or share anything. Check the sender domain. Report it through Report a security issue or to security@fortytwo.network, and tell a moderator.
Do not share it. Fortytwo never asks for it. Report the account to a moderator.

​
Other

Last modified on October 3, 2026