How to reach Fortytwo: which form or address fits which request, and how to recognise official messages.
Most answers are in this documentation. Search from the top of any page, or check Common problems. For anything about your account, use the forms below.
Official email from Fortytwo comes only from addresses at fortytwo.network, including its subdomains such as no-reply@platform.fortytwo.network, or as messages inside the Fortytwo platform. Payment receipts come from Stripe on our behalf. Anything else is not from us.
We give technical, billing and security support by email only. You send a request through a form in the platform or by email. We always reply by email.
Community channels are for general information. Answers on Discord and X come from our community team. They are not support and not a decision about your account, and the team cannot see or change your account.
Never share your API key or password, in public, in private messages or by email. Fortytwo will never ask you for them.
Our team will not message you first on Discord or X to offer help. If someone does, it is not us.
Do not post personal or account details in public channels: emails, invoices, or screenshots that show this information.
Fortytwo accounts use email. Signing in with a crypto wallet (Web3) is not supported for now, until further notice. Your account is identified by your primary email, shown on your Account page. When you contact us, write from that address or include it, so we can find your account.
Legal, privacy, complaints, refunds and withdrawals
Email legal@fortytwo.network for legal notices, complaints, refunds, withdrawal requests, and requests about your personal data: a copy, a correction or deletion. Send it from your primary email, or include it in your message, so we can find your account. Do not send ID documents unless we ask for them.
The request ID of the failing request. Every API response carries it in the x-request-id header, and error bodies repeat it as request_id.
The time of the request, in UTC.
The model ID, and whether the request was streaming.
The HTTP status and the error.code from the response.
What you expected, and what happened instead, and whether it happens again.
Never include your API key, in any form. If a key may have been exposed, revoke it first and say so in your message. Remove from prompts and outputs anything you would not send by email.
Do not reply to emails from a no-reply address. Nobody reads those replies.
Emails from our support team say how to reply, for example reply to that email, or use a specific form. Follow those instructions; it is the fastest way to solve your request.
Check the sender. It must be an address at fortytwo.network or one of its subdomains; payment receipts come from Stripe. Look-alike addresses (extra letters, other endings) are not us. Do not click links in them; report them as a security issue.
We do not promise a fixed reply time. Please do not send the same request again and again; a new copy does not move your request up the queue.
