Getting started

This path takes a self-service user from registration to the first API request. If your organisation is being connected by Omev, use the access and key supplied during the managed setup; the API steps below are the same.

1. Create a self-service account

1. Open seochat.omev.be and select Start free trial.
2. Enter your work email and describe how you use AI. Company details and expected monthly volume are optional.
3. Complete the browser check and submit the form.
4. Open the email from Omev. It contains a sign-in link and a six-digit code; either method works.
5. After verification, the cabinet creates the account and shows the initial API key.

The self-service trial includes USD 5 of credit for 10 days and does not require a payment card. Image generation is not enabled automatically.

2. Save the key

Copy the full key directly into your password manager or secret-management system. For the initial key, the Keys screen may provide one additional Show the key once action. After that remaining display is used, only a mask is available. A key created later in an organisation screen must be copied during creation.

Never put a key in browser-side JavaScript, a mobile application, a public repository, a screenshot, or a support message. The examples below assume the key is stored on the server as OMEV_API_KEY.

3. Check what the key can use

curl -sS https://llmapi.omev.be/v1/models \
  -H "Authorization: Bearer $OMEV_API_KEY"

Build only against the documented public omev-* names returned for your key. Image products appear only after their separate access has been enabled.

4. Send the first text request

curl -sS https://llmapi.omev.be/v1/chat/completions \
  -H "Authorization: Bearer $OMEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "omev-lite",
    "messages": [
      {"role": "system", "content": "Follow the requested format carefully."},
      {"role": "user", "content": "Summarise this text in five bullets: ..."}
    ],
    "temperature": 0.2,
    "max_tokens": 500,
    "stream": false
  }'

The answer is in choices[0].message.content. See Models for Python, model selection, streaming and structured JSON.

5. Test an exact request in Playground

Open Playground in the web cabinet when you want to test the same JSON body your application will send. You can paste an existing curl command or build a request in the form. Playground shows the response, token counts, duration, request body, and code examples for curl, Python and NodeJS.

Playground verifies the technical compatibility of a future API call. It is not a production queue or an alternative interface for ongoing AI work. Use Chat separately when you need to evaluate answer quality on representative future API requests.

The key in copied code is masked. Replace the mask with OMEV_API_KEY or a reference to your secret manager before running the example outside the browser.

6. Review usage and cost

Self-service accounts use Dashboard, Usage, Journal and Billing in the web cabinet. Recent calls can take a few minutes to appear.

Corporate customers also receive access to usage.omev.be after the organisation and first approved owner are provisioned. The owner can invite additional people without asking Omev to enter every email manually.

7. Continue safely

• Use separate keys when the cabinet and your role allow it and separate control is useful.
• Set output limits, timeouts and a small maximum number of retries.
• Retry 429, temporary 5xx responses and transient network errors with increasing delay. Do not repeat an unchanged 400, 401, 403, 404 or 413 request.
• Validate structured output in your own application.
• Keep request identifiers and key masks in logs, never complete keys or confidential prompts.

For access questions or an unresolved problem, contact support@omev.be. Include the account email, approximate time and timezone, endpoint, public model, status, request identifier when available, and a sanitised example.