Skip to main content
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.

​
Read this first

  • 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.

​
About sign-in

You sign in with Google or with your email (an email link or a password). If you sign up with Google, the email of your Google account becomes your primary email, and you can also sign in with an email link to that address. 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.

​
How to contact us

Most requests start at platform.fortytwo.network . Sign in first, then use the forms below. The forms already know who you are, so we can help faster.

​
Support: account, API, billing, credits, errors

  1. Sign in at platform.fortytwo.network.
  2. Open the account menu (your name at the bottom of the sidebar; on a phone, open the navigation menu first) and choose Get help, then Contact support.
  3. Pick a topic: Billing and credits, API keys and access, API errors and latency, Tier and limits, Account, or Other.
  4. Describe the problem: what happened, what you expected, and the steps to reproduce it. See What to include.
  5. Press Send message. We reply by email.

​
Higher limits or a tier upgrade

  1. Sign in at platform.fortytwo.network.
  2. Open the account menu, choose Tier and limits and press Request upgrade. Request upgrade is also on the Account page (account menu → Account settings).
  3. In Request type, keep Tier upgrade. The form shows your current tier.
  4. Press Submit request. Our team reviews every request. An upgrade is not guaranteed, and it can take effect from the start of the next month or later.
Need more than the highest tier? In the same form, set Request type to Enterprise API terms.

​
Security issue

  1. Sign in at platform.fortytwo.network.
  2. Open the account menu and choose Get help, then Report a security issue.
  3. Choose the area and describe the issue with steps to reproduce. Remove API keys, secrets and other people’s personal data.
  4. Press Submit report.
Do not post security issues on Discord, X or any public place. Our Vulnerability Disclosure Policy explains what to expect.

​
Ideas, feedback and small bugs

  1. Sign in at platform.fortytwo.network.
  2. Open the account menu and choose Feedback.
  3. Pick a type (Idea, Bug, Models, Docs, Billing, Other) and write your feedback.
Feedback helps us improve the platform. If something blocks your work, contact support instead.

​
Fortytwo Harbor: on-premises or private cloud for your organisation

  1. Go to fortytwo.network and press Deploy on-premises or Explore Harbor. You can also go straight to harbor.fortytwo.network .
  2. Fill in the form: your name, work email, organisation and what you need.
  3. Our team replies by email to arrange a call.
Already signed in to the platform? Use the upgrade form and set Request type to On-premises deployment. 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.

​
When the platform form is not an option

Use these addresses only if you cannot use the forms above:

​
What to include

  1. 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. In Logs, select the request: its details show the Request ID.
  2. The time of the request, in UTC.
  3. The model ID, and whether the request was streaming.
  4. The HTTP status and the error.code from the response.
  5. 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.

​
When we email you

  • 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.
Last modified on October 7, 2026