/api/v1/messagesText generation
Send text, images and documents, call functions and built-in tools, and get the Oppermind native response.
Read endpoint guidance{ } Oppermind Developer API
Learn the implemented v1 contract for text generation with images, documents and tools, plus image and video generation, then use the existing Developer console for keys, usage, billing, webhooks and team access.
One request
Keep API keys server-side. Send a bearer key, JSON content and a stable idempotency key for retryable operations.
curl https://oppermind.com/api/v1/messages \
-H "Authorization: Bearer $OPPERMIND_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: request-2026-09-02-001" \
-d '{"model":"oppermind-lato-1","max_tokens":1024,"messages":[{"role":"user","content":"Summarise this plan for an executive audience."}]}'Store opmd_sk_... only on your server. Keys are shown once in the Developer console.
stream: true is rejected with OPMD_MODEL_005. Requests can be up to 31 MB with up to 2000 messages, output defaults to 16384 tokens and goes up to 128000, and each key can send 120 requests per minute. Every text response reports its charge in billing.charged_aud. Video responses are synchronous and proxy downloads remain authenticated.Stable v1 surface
Use the same authentication and reliability conventions across every endpoint.
/api/v1/messagesSend text, images and documents, call functions and built-in tools, and get the Oppermind native response.
Read endpoint guidance/api/v1/chat/completionsUse an existing Chat Completions client by changing the base URL and the model.
Read endpoint guidance/api/v1/responsesSend stateless Responses API requests with input items and function calls.
Read endpoint guidance/api/v1/filesUpload a document once and reference it by file_id in any text request.
Read endpoint guidance/api/v1/imagesGenerate image results with authenticated delivery.
Read endpoint guidance/api/v1/videosCreate synchronous video results and retrieve them securely.
Read endpoint guidanceProduction integration
Idempotency keys are retained for 24 hours. Deprecations include headers and a minimum 180-day runway.
Reuse the same Idempotency-Key of 8 to 255 characters for the same logical operation.
Read the guideHandle structured OPMD_* errors, 429 responses and authenticated media URLs.
Read the guideRead X-API-Version, Deprecation and Sunset headers; monitor the changelog.
Read the guideGuided learning
Start with a secure key and finish with retries, usage controls, version tracking and a tested integration.