OppermindDocs
Try Oppermind
Sign inTry Oppermind

{ } Oppermind Developer API

Build with Lato.
Ship with confidence.

Learn the implemented v1 contract for text, image and video generation, then use the existing Developer console for keys, usage, billing, webhooks and team access.

Take the API quickstart Open Developer console

One request

Your first Lato API result.

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 '{"input":"Summarise this plan for an executive audience."}'

Store opmd_sk_... only on your server. Keys are shown once in the Developer console.

Current contractstream: true is rejected with OPMD_MODEL_005. Video responses are synchronous and proxy downloads remain authenticated.

Stable v1 surface

Text, image and video.

Use the same authentication and reliability conventions across every endpoint.

Production integration

Design for retries and change.

Idempotency keys are retained for 24 hours. Deprecations include headers and a minimum 180-day runway.

Idempotency

Reuse the same 8–255 character Idempotency-Key for the same logical operation.

Read the guide

Errors and limits

Handle structured OPMD_* errors, 429 responses and authenticated media URLs.

Read the guide

Versioning

Read X-API-Version, Deprecation and Sunset headers; monitor the changelog.

Read the guide

Guided learning

From first request to production.

Start with a secure key and finish with retries, usage controls, version tracking and a tested integration.

Take the production course Open the real Developer console