New: manage Sliplane from your terminal with the CLI →
Documentation
Inference (Private Beta)

Limits & Errors

Request size limits, unsupported features, and error responses of the Inference API.

Private beta: Email support@sliplane.io to request Inference access for your team.

Request limits

EndpointMaximum request body
/v1/chat/completions32 MiB
/v1/responses32 MiB
/v1/embeddings4 MiB, up to 128 inputs
/v1/audio/transcriptions25 MiB, including the file and form fields
/v1/systemone12,000 bytes, 1–32 questions

Unsupported features

  • Responses: stored state (store must be false), background requests, saved prompts, and uploaded file references. Send the conversation history with each request. Tools must be function or custom tools executed by your client.
  • Embeddings: streaming and token ID inputs.
  • Transcription: streaming and confidential keys.
  • Decisions: images, streaming, and extra request fields.

Errors

Errors use the OpenAI error format:

{
  "error": {
    "message": "API key spend limit reached.",
    "type": "invalid_request_error",
    "param": null,
    "code": null
  }
}

type is invalid_request_error for 4xx responses and server_error for 5xx responses.

StatusMeaning
400The request body or parameters are invalid
401The key is missing, invalid, deleted, or lacks the inference scope
404The model is unknown or not available on this endpoint or for this key
413The request body exceeds the limit
429The key reached its spend limit
502The model returned an invalid response
503The service is temporarily unavailable
504The model did not respond in time

Retry 502, 503, and 504 with backoff.

Streaming errors

Once a stream has started, the HTTP status stays 200. Errors after that point arrive as an event in the stream.

How is this guide?

On this page