Introduction

Welcome to the meinGPT Developer Guide. With the meinGPT API, you can safely and easily build your own applications with AI, without needing additional accounts and services. Additionally, many of the powerful features from the platform, such as assistants and workflows, are also available in the API.

API Overview

The meinGPT API provides programmatic access to:

• LLM responses and Embeddings
• Assistants
• Workflow execution
• Audio transcription

Quick Start

curl -X POST "https://app.meingpt.com/api/openai/v1/chat/completions" \
-H "Authorization: Bearer $MEINGPT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "messages": [
    {"role": "user", "content": "Hello, meinGPT!"}
  ],
  "model": "gpt-4o-mini"
}'

Rate Limits

The meinGPT API has no limit on the number of concurrent (parallel) streaming requests. Instead, a token budget per minute is checked at multiple levels simultaneously:

• Per user: 125,000 tokens/minute by default
• Per organization: 250,000 tokens/minute by default (shared across all users in the organization)

All limits use a rolling 60-second window and count combined input and output tokens. A custom higher limit for an organization cannot currently be self-configured — contact us to discuss an adjustment.

Requests over the limit are not queued; they are rejected immediately with a 429 error. The response includes a Retry-After header (currently a fixed 60-second value) plus headers indicating the token limit, remaining budget, and reset time.

Error Handling

If a request can't be completed, the API returns a non-2xx HTTP status code. Common codes:

• 400 – Invalid request (e.g. unsupported parameter value, malformed input)
• 401 – Invalid or missing API key
• 403 – Model or completions API not enabled for the organization
• 429 – Rate limit reached (see Rate Limits above) - retry with backoff or switch to a different model
• 500 – Temporary error at the AI provider - retry after a short wait

Some error responses may not include a JSON body that OpenAI-SDK-based tools can parse (some third-party clients report this as "no body"). Always check the HTTP status code first rather than relying on the response body, and implement retries with exponential backoff for 429 and 500 responses.

Support

If you need help with the API, contact us at support@meingpt.com or submit a request through our support portal↗.

Best Practices

• Always handle errors properly
• Implement exponential backoff for retries
• Cache responses when appropriate
• Monitor your usage to avoid limits