Skip to main content

​
Create a key

  1. Sign in at platform.fortytwo.network.
  2. Open Credits and press Buy credits. Every request is charged to this balance — see Pricing.
  3. Open API keys and press Create key (New key if the account already has keys).
  4. Copy the key. It is shown only once.
Use a separate key for each integration. Usage is reported per key, and a key can be disabled or revoked on its own.

​
Send the key

Send the key in the Authorization header of every request. A request with a body also needs Content-Type: application/json. Keys start with sk-ft-v1-.
Keep the key in an environment variable. The examples in these docs read it from FORTYTWO_API_KEY.
The API does not accept cross-origin requests from a browser. Call it from your server, and keep the key there. A missing, malformed, unknown, disabled, revoked or expired key returns 401 invalid_api_key.

​
Key and account settings

​
Spend limits

  • Both limits are checked when a request starts. A request that is already running finishes and is charged, so spend can end above a limit by the cost of the requests in progress. Each running request can cost up to a maximum-length request for its model.
  • A key over its Spend limit gets 429 billing_limit_exceeded. Any key on an account over its Monthly spend limit gets 402 account_spend_limit_reached.
  • Buying credits does not clear either error. They clear when the limit resets, or when the limit is raised or removed.
  • A Monthly spend limit of $0 blocks all new requests. Changing the limit does not reset the month’s spend.

​
Track usage

Both keep 12 months of history. Prompts and responses are not shown.
Last modified on October 3, 2026