AI API infrastructure
for production workloads.

Omev recognises your business task, routes it between our own models and checks the result against your requirements. Grow repetitive AI workloads with a routing policy built around your cost per accepted output — not just the cheapest token.

For SaaS companies and platforms whose AI bill is now a line item finance asks about.

$5 free credit · 10 days · no card  ·  OpenAI-compatible  ·  No migration

Your AI bill grows every time your product grows.

Usage-based pricing means your cost of goods scales with your own success. Every new customer, workspace and feature adds calls you pay for. Most software gets cheaper per unit as it grows; this does not, so every point of growth arrives with its own bill attached.

More customers
More AI-backed features
More calls per customer
Higher AI bill
Lower gross margin

Frontier models earn their price — on hard work

For reasoning, code, agents and anything customer-critical, the best models are worth every cent. Keep them there. The problem is not the frontier model. It is everything else that routes through it by default.

The volume that scales fastest is repetitive

The work that grows with usage is well specified, schema-shaped and high volume. Clear input, clear output, no room for interpretation. Those jobs rarely need your most expensive model — and if you have already moved some of them onto a cheaper tier, you have made this argument yourself.

ClassificationStructured extractionTranslationProduct copyMetadataCopy variantsSummarisation

The cheapest response is not always the cheapest result

A low token rate can hide the cost of checks, cleanup and retries. Omev recognises the task, selects its own models and validates against your client profile. Routing is optimised around the total cost of an output that meets your criteria, not just the first response.

Every job priced above the level it needed comes out of your margin — one call at a time.

What our customers say.

“AI generation can get expensive pretty quickly. So around six months ago, we added Omev AI to a few parts of our infrastructure in Outrank. The results have been on par with the leading models we use, while helping us reduce generation costs. We keep the same quality bar, but the economics are simply better. We still use different models for different parts of the product, and Omev AI is now one of them.”
Eugene Zolotarenko
Eugene Zolotarenko
Outrank
View on LinkedIn →
“I wanted to test omev.be as part of the AI/SEO workflow rather than just playing with it in a chat interface. What I liked was that it’s actually exposed as an OpenAI-compatible API, so integrating it into an existing application was straightforward. I’m still early enough that I wouldn’t claim any SEO/business results yet, but from a developer perspective the experience was surprisingly frictionless. The fact that the output is designed around specific SEO tasks rather than generic AI responses makes the integration more practical.”
GrumpyGene
GrumpyGene
Building RefreshRadar
View on X →

Why Omev AI

Your task. Your criteria. Our execution.

OpenRouter, LiteLLM or a direct model API can be part of your stack. Omev takes on the model selection, client rules and result checks for the business tasks you send us.

Omev AI

Execution tailored to your workload.

  • Recognises the business task in each request
  • Applies your acceptance criteria and client profile
  • Selects an Omev model or sequence for that task type
  • Checks the result against your requirements
  • Repairs or falls back between our own models when checks fail
  • Uses production results to improve cost per accepted output

Available to every registered customer. Routing runs between our own models.

OpenRouter / LiteLLM

Model and provider selection, availability, cost controls and fallbacks. They also support capabilities such as automatic routing or configurable guardrails.

Your team assembles the business workflow and defines how a result is accepted for each client.

Direct model API

Call a model using the provider's generation and output controls. Your team builds the surrounding task logic, client profiles, validation and recovery workflow.

Measure cost per accepted output.

Total execution cost ÷ results that meet your criteria. Include generation, checks, repairs and retries when comparing routes.

Benchmark My Workload →
Compare the routing capabilities

Routing itself is not exclusive to Omev. See the official documentation for OpenRouter Auto Router, LiteLLM routing and LiteLLM guardrails. Our offer is the managed, client-specific task workflow described above.

See the Omev AI routing workflow →

Built around your requirements

Same task. Different client. Different AI behavior.

The product facts stay the same. Switch the client profile to see how the requirements, processing steps and output change.

Same request and source facts

Write a product description

  • Ridge bottle
  • 750 ml
  • Stainless steel
  • Screw-top lid
  • 280 g
  • Matte graphite

A factual marketplace listing with exact product attributes.

Client acceptance criteria

  • 120–160 words
  • JSON schema
  • Exact product attributes
  • No exaggerated claims
  • Amazon listing style

How Omev handles this profile

  1. 01Structured product draft
  2. 02Attribute and schema checks
  3. 03Repair any mismatched fields

Omev selects the model or sequence from our own models. Repair and fallback run on our side when checks fail.

Checks: Description length · Required JSON fields · Source attributes · Unsupported claims

Example output · JSON

The Ridge bottle combines a 750 ml capacity with a stainless steel body, a screw-top lid and a matte graphite finish.

View full example
{
  "name": "Ridge bottle",
  "description": "The Ridge bottle combines a 750 ml capacity with a stainless steel body, a screw-top lid and a matte graphite finish. Its listed weight is 280 g. These specifications give shoppers a straightforward way to compare the bottle with other options.\n\nChoose by the details that matter to you: capacity, material, lid type, weight or finish. The 750 ml figure describes the stated capacity, while stainless steel identifies the body material. The screw-top design describes the closure, and matte graphite identifies the finish.\n\nProduct details are kept together so you can review them before making your choice. If you are comparing several bottles, use the same fields for each one and check the Ridge specifications against your preferences. Explore the listing to decide whether Ridge belongs on your shortlist.",
  "attributes": {
    "capacity": "750 ml",
    "material": "stainless steel",
    "lid": "screw-top",
    "weight": "280 g",
    "finish": "matte graphite"
  }
}

Illustrative client profiles and outputs. Your policy is built from your requests and agreed criteria.

After you register

From your real requests to a route built for you.

Register with your work email. We follow up personally to start with your workload; Omev runs the analysis, routing and checks automatically. This onboarding is available to every registered customer.

  1. 01

    Share your real work

    Register and share a sample of production requests. Omev automatically groups them by task type and establishes your current models and cost baseline from the information you provide.

    Your tasks and baseline

  2. 02

    Define good. Benchmark it.

    Agree the required facts, format, voice and quality criteria. Omev benchmarks its own models and sequences against those requirements and your current output.

    Criteria and measured results

  3. 03

    Connect your tailored route

    Omev builds your routing policy and provides an OpenAI-compatible endpoint. Start with one task type; model selection, validation, repair and fallback run on our side.

    Your policy and endpoint

  4. 04

    Improve with real usage

    Omev collects cost, latency, validation and retry telemetry. Production results feed automatic routing improvements measured against your acceptance criteria.

    A policy informed by real results

Benchmark My Workload →

Starts with registration and a personal follow-up.

Keep frontier models for the hard stuff.
Stop overpaying for the rest.

You do not need to leave OpenAI, Claude or Gemini. Keep them on the work where frontier-level intelligence changes the answer, and send the repetitive, high-volume share of your traffic to Omev instead. Within that workload, Omev automatically selects from our own models, applies your client profile and checks the output against your criteria.

Keep on your current provider

  • Complex reasoning and multi-step decisions
  • Coding and agentic workflows
  • Open-ended prompts with no fixed shape
  • Decisions where being wrong is expensive — moderation, eligibility, anything a customer can appeal
  • Anything where frontier-level intelligence is the product

Route to Omev

  • Structured extraction into a fixed JSON schema
  • Classification and tagging against a fixed taxonomy, where a wrong label is cheap to correct
  • Translation and localisation passes
  • Titles, metadata and other short fields
  • Product, listing and catalogue descriptions
  • Rewriting, summarising and reformatting at volume
  • Bulk content generation from a brief

Start with one task type. Keep the rest of your stack.

After the benchmark, connect that workload to your OpenAI-compatible endpoint. Omev handles model selection, validation, repair and fallback between our models. Your team connects the calls you choose and checks compatibility with your integration in the API docs.

Benchmark My Workload →

Find the use case you run at scale.

Choose the repeated workflow where volume—not difficulty—drives the bill. Each page shows the work, the unit economics and the safest way to test it.

Text runs self-serve on your API key. Image and video access is enabled per account — video is in early access, and failed image generations are not billed.

What is the repetitive share of your bill actually costing you?

You know your monthly spend, so start there — no token arithmetic required. Enter what you spend, pick what runs that work today, then drag the share of it that is repetitive.

Current spend
$10,000
Routable workload
$6,000
Estimated new bill
$6,375
Potential annual impact
$43,500
$3,625 a month, at 60% off the routed portion.
Benchmark My Workload →

An estimate, not a quote. It prices the routed share against the matched Omev tier at list price on one representative request shape — 3,000 input and 2,000 output tokens, an assumption rather than a measurement — leaves the rest of your bill exactly where it is, and ignores any discount you have negotiated. If that work already runs on a light model, the gap is far smaller: against GPT-5.6 Luna on the same shape it is about 2%, and Luna can be cheaper on output-heavy prompts. In that case, use the benchmark to decide on total cost per accepted output rather than the rate card alone. This is arithmetic on the numbers you typed in, not a measurement of your prompts. The only figure worth acting on is the one you get from running 20 to 50 of your own production prompts through both.

Add acceptance rate and review time to the estimate →

Built for companies already running AI in production.

Omev is for you if

  • You already call the OpenAI, Claude or Gemini APIs from production code
  • AI is part of your product or your operations, not an experiment beside them
  • Your AI spend is a line item finance now asks about
  • A large share of your calls are repetitive and well specified
  • You run text, images or video at volume — thousands of calls a day, not dozens
  • You can name the one task type you would move first

Probably not for you if

  • Your prompts and outputs cannot be used to train our models — that use is mandatory here, with no opt-out
  • You need SOC 2, ISO 27001 or a contractual SLA to clear your own security review — we hold none of them today
  • Every request genuinely needs frontier-level reasoning or open-ended judgement
  • Your AI bill is small enough that a day of engineering costs more than a year of the saving

None of those are hedges. Training on customer content is a condition of using the Service, not a setting, so a workload that cannot live with it should stop here rather than find out after integration. And on a small bill the saving is real in percentage terms and trivial in absolute ones — tens of dollars a month, against a day of engineering and a security review. Optimise it when the integration pays for itself. We would rather say so than sell you a benchmark that cannot.

Typical customers

SaaS products with high-volume AI featuresSEO, GEO and content platformsE-commerce, marketplaces and product cataloguesLocalisation and translation platformsSocial media and creative automation toolsAI writing, rewriting and humanisation productsImage and video generation productsAudience intelligence and customer research toolsText analysis, review intelligence and moderation platformsAgencies automating repeatable client delivery

OpenAI-compatible integration

Your existing stack. Omev's routing and checks.

Connect the agreed workload through an OpenAI-compatible endpoint. Your client profile, model selection, output validation and repair logic run on our side. Your team tests the supported parameters and decides which traffic to send.

Built on our own models

Omev AI is not a wrapper and not an API reseller. The output you pay for is produced by two models we fine-tuned ourselves, trained on our own SEO corpus and served on our own GPU infrastructure. Where we use commercial vendor APIs, we use them in accordance with their terms of service. On top of our models we run our own routing, task contracts and output validation, which is what turns a raw model call into a finished SEO task.

What that means in practice

You are not buying access to someone else's API. There is no third party account opened in your name, no provider keys or credits resold to you, and no provider endpoint proxied through us. Our API is compatible with the OpenAI SDK at the protocol level only, so your existing client works without changes. Where external capacity is used inside our routing layer, it is our own infrastructure decision under our own contract, at our price and within the vendor's terms of service, invisible to you, the same way any online service relies on infrastructure vendors.

How we operate

Omev AI is a business to business product with public pricing, a live service and a working support channel. Our Terms of Service, Privacy Policy, Acceptable Use Policy, Billing and Cancellation terms, AI and Customer Content policy and the list of subprocessors are published on this site. NSFW, face swap and deepfake use is prohibited by our Acceptable Use Policy. We do not make claims about models we do not run.

We don't keep a list of banned niches.

If your vertical keeps getting refused, hedged or quietly watered down by a general-purpose model, that is a category policy talking — not a technical limit. Ours is written around conduct, not subject matter.

What we don't do

We do not maintain a blocklist of industries, topics or client types. We do not decide that your market is too commercial, too competitive or too unglamorous to write about, and we do not refuse a brief because of the sector it came from.

You are the publisher. You know your market, your regulator and your audience better than a content filter does.

What is genuinely out of bounds

  • Anything unlawful, deceptive or fraudulent
  • Sexual content that is unlawful, and non-consensual intimate material
  • Impersonation, deepfakes and face swaps
  • Fabricated citations, reviews or endorsements passed off as true
  • Personal data on self-service plans, and credentials or payment secrets anywhere
  • Standing in for a doctor, lender, employer or court in a decision about a person

These are conduct rules, not topic rules, and they are published in full — read the Acceptable Use Policy. One obligation sits with you rather than us: where the law requires it, you must disclose that content was generated by AI.

Already on OpenAI, Claude or Gemini?

See which high-volume workloads you can move to Omev, what the published rate difference becomes at your scale and how to switch one production route without rebuilding the stack.

Or price your own token volume against every model, or browse all alternatives.

See what's inside before you sign up.

No black box. Your key, your live credit and every task you run — plus a playground that hands back working code. Click through the real screens.

cabinet.omev.be

Dashboard

How much is left and where it went.

Your balance

Credit left

$99.60

Tasks & cost

Tasks, last 7 days

21

$0.32 · spent in this period

Your API key

Your key

sk-U77…RPJQ

The full key is shown only once, when it is issued.

Quick start

curl https://llmapi.omev.be/v1/chat/completions \
  -H "Authorization: Bearer sk-U77…RPJQ" \
  -H "Content-Type: application/json" \
  -d '{"model":"omev-lite","messages":[{"role":"user",
       "content":"Write a meta description for a page about running shoes"}]}'

Put your full key in place of the mask and run the call.

The Omev dashboard, rebuilt from the real screens. Switch tabs for Usage and the Playground.

A key and $5 credit on signup

Issued the moment you confirm your email — no review queue, no card.

Spend and tasks, in the open

Credit left, tasks run and cost per model — not a monthly surprise.

A playground that returns code

Pick an example, send it, and copy the working call in your language.

Transparent pricing. Two plans, no surprise invoices.

Personalised routing is available on both plans. Start with $5 of free credit, use published token rates or agree an individual contract.

Pay as you go

$10min top-up

Self-serve. Top up by card and spend what you use.

  • ✓Token pricing — full rates below
  • ✓Personalised task routing and result checks
  • ✓Top up by card from $10
  • ✓Topped-up credit valid 30 days
  • ✓No monthly fee, no seat fee, no commitment
  • ✓$5 free credit · 10 days · no card
Start Free →

Enterprise

Custom

For teams that need individual terms.

  • ✓Custom volume and rate limits
  • ✓Per-finished-task pricing available by contract
  • ✓Individual contract and Enterprise DPA
  • ✓Dedicated support channel
  • ✓Invoicing and negotiated terms
Request a Quote →

What counts as a task? One finished production action — the kind you'd otherwise do by hand or clean up after a general model. One request in, one ready-to-use result out.

For example, one task = one product description · one string set translated into a locale · one meta title & description · one set of catalogue attributes extracted · one post repurposed into its formats · one batch of image prompts.

Pay as you go bills the tokens a task consumes, at the rates below. Pricing per finished task instead is an Enterprise arrangement, set by contract.

Token rates

No tiers by request volume. No seat fees. Pay exactly for what you use — top up by card from $10; credit stays valid for 30 days after top-up.

Omev Lite

High volume

The repetitive share of your pipeline

Input$0.15 / 1M tokens
Output$1.25 / 1M tokens
  • ✓Titles, metadata and other short constrained fields
  • ✓Classification and tagging against a fixed taxonomy
  • ✓Structured extraction into a fixed JSON schema
  • ✓Translation and localisation passes
  • ✓Product, listing and catalogue descriptions
  • ✓Bulk rewriting, summarising and reformatting
  • ✓Image and creative prompt generation

Omev Pro

Most Popular

Reasoning-heavy and long-context work

Input$0.625 / 1M tokens
Output$5.00 / 1M tokens
  • ✓Content plans, briefs and outlines
  • ✓Long-form drafting that has to hold an argument together
  • ✓Long-context work across several source documents
  • ✓Editorial and quality review passes
  • ✓Tasks with several constraints that depend on each other
  • ✓Anything where the answer needs judgement, not just shape

Those are the rates, not a quality claim. We publish no benchmark scores of our own — a score on someone else's prompts tells you nothing about yours. Send us 20 to 50 of your production prompts and judge the output against what you run today.

Images and video

Image products are priced per delivered image. Choose direct 1K, async 1K or direct 2K/4K for the workflow; failed requests are not billed.

Direct response

Omev Image Lite

$0.0192
per delivered image · 1K (1024×1024)

A 1K image returned inline in the same response. Best for product flows where someone is waiting.

71% below Google Standard

Async bulk

Omev Image Jobs

$0.021
per delivered image · 1K output

Queue bulk 1K work, then poll or take a callback. Best for catalogue and scheduled generation.

38% below Google Batch

Higher resolution

Omev Image Pro

$0.024
per delivered image · 2K or 4K

Direct 2K or 4K generation in an OpenAI-compatible images response shape.

2K/4K direct · no 1K comparison

The 1K comparisons use Google's published Gemini 3.1 Flash Image rates — $0.067 for Standard and $0.034 for Batch. Lite is compared with Standard; asynchronous Jobs with Batch. Pro generates 2K/4K images, so it is not presented as a cheaper version of a 1K product.

Choose the delivery shape and output size the workflow needs.

Lite returns a 1K image inline when someone is waiting. Jobs queues 1K work for a catalogue or scheduled run; result URLs stay available for 48 hours and aspect ratios cover auto, 1:1, 3:2 and 2:3. Pro returns 2K or 4K images directly when the finished asset needs more resolution.

4–12 seconds

Omev Video Lite

$0.039
per generated second
4–12 seconds

Omev Video Standard

$0.079
per generated second
16–30 seconds

Omev Video Long

$0.129
per generated second

Start from text or an image. Choose the tier by clip length.

Lite and Standard cover 4–12 seconds. Long covers 16–30 seconds. The current offer confirms text or an existing image; resolution, audio, output shape and delivery are confirmed when early access is enabled for the account.

Get image & video access →

USD · Image and video access is enabled per account · Failed image generations are not billed · Confirm video failure billing during setup

Questions before you route

Cost & billing

Is Omev billed per token or per task?+
Per token on the self-serve plan. Pay as you go is billed on the published token rates — $0.15 in and $1.25 out per million on Omev Lite — with the full rate card in the pricing section. Pricing per finished task instead, so a fixed number of results is a number you can put in a client invoice, is an Enterprise arrangement set by contract.
How do I know my monthly cost before I commit?+
Run your real prompts on the $5 free credit, read the exact per-task cost in the dashboard, then multiply by your volume. The savings calculator on this page will get you an order of magnitude before that, from your current bill and the share of it that is repetitive. There is no monthly fee to commit to on Pay as you go — you top up from $10 and spend what you use.
What do I get with the free trial?+
$5 of credit, valid 10 days, no card required. Enough to run your own production prompts through both models and compare the output, the cleanup and the cost against your current provider.
How can it be so much cheaper than the big APIs?+
Two reasons, neither of them magic. The models are fine-tuned for content-shaped work rather than general-purpose reasoning, and we serve them on our own GPUs, so you are not paying for capability your metadata job never uses. The rate-card advantage is clearest against current balanced models: Omev Pro is $0.625 in / $5.00 out per million tokens, against $2.00 / $12.00 for GPT-5.6 Terra. For economy-tier work, Omev Lite is $0.15 / $1.25. If you currently use GPT-5.6 Luna at $0.20 / $1.20, the token rates are close; move a small slice and compare cost per accepted output, cleanup and retries. The OpenAI-compatible route lets you prove the production advantage before expanding it.
Can I keep my existing OpenAI code?+
Omev provides an OpenAI-compatible endpoint for your agreed workload, so you can reuse your existing SDK integration. Test the supported parameters and response handling before routing production traffic. Within your personalised policy, Omev manages model selection, client rules and result checks on its side.

Routing & migration

Do I need to replace OpenAI, Claude or Gemini?+
No, and we would not recommend it. Frontier models earn their price on reasoning, coding and agentic work. The case for Omev is the repetitive, high-volume layer underneath — descriptions, metadata, translations, captions, tagging, classification, bulk rewrites, catalogue imagery — where a frontier model is being paid premium rates for a job that was never hard. Keep your existing providers and route that slice.
Which workloads actually suit this?+
High-volume work with a known shape and a well-specified prompt: product and catalogue descriptions, category and metadata text, translations and locale variants, social captions and variants, bulk rewriting, structured extraction into a fixed JSON schema, and image generation at catalogue scale. Two caveats we would rather state than have you discover. Classification suits this where the taxonomy is fixed and a wrong label is cheap to correct — not moderation, eligibility or anything a regulator will read. And route by task type rather than by a random percentage of traffic, so one product surface keeps one voice instead of two.
Can we start with only part of our traffic?+
Yes. Start with one task type and a representative sample, benchmark it against your acceptance criteria, then decide how much traffic to send. The endpoint is OpenAI-compatible, and your existing providers can stay connected for the work you keep with them.
Can you benchmark our workload before we integrate?+
Yes. Register and we follow up personally to collect a representative sample, your current output and cost baseline. Omev groups requests by task type and benchmarks its own models against the acceptance criteria we agree with you. Compare the full execution cost, including checks, repairs and retries, per accepted output before connecting production traffic. This onboarding is available to every registered customer.
What happens if Omev is unavailable?+
Omev handles validation, repair and fallback between its own models within your routing policy. An outage of the whole Omev service is a different case: your team can keep an independent provider connected as a service-level fallback. Adding Omev for one workload does not require removing your existing providers.

Quality & output

How is the output different from a general model?+
Omev executes the task against your client profile: required facts, output format, voice and other agreed acceptance criteria. It selects its own models or sequence, validates the result and uses repair or fallback when checks fail. The relevant comparison is whether your real outputs meet your requirements, and their total execution cost, not a general claim that one model is better than another.
Do you support structured output for pipelines?+
Yes. Your client profile can specify a JSON schema or another agreed delivery format, such as Markdown. Omev checks the result against that structure as part of the task workflow. The format is defined for your workload rather than forcing every client into the same response shape.
What happens when an output is wrong or broken?+
Omev checks the result against your agreed criteria and automatically runs repair or fallback between its own models when checks fail. Report any remaining quality issue with the request reference so it can be reviewed against your client profile. These outcomes also inform routing improvements.
Do you restrict what topics or niches we can write about?+
We do not keep a blocklist of industries, topics or client types, and we will not refuse a brief because of the sector it came from. The Acceptable Use Policy is written around conduct rather than subject matter: no unlawful or deceptive use, no unlawful sexual content or non-consensual imagery, no impersonation or deepfakes, no fabricated reviews or citations presented as true, and nothing that stands in for a doctor, lender, employer or court deciding about a person. Where the law requires it, disclosing that content is AI-generated is your obligation as the publisher. Read the Acceptable Use Policy →
How do you keep routing changes aligned with our quality requirements?+
Your acceptance criteria remain the reference for validation and routing improvements. Omev uses production outcomes, including validation results, repairs, retries, cost and latency, to assess the policy against your workload rather than optimising for a cheaper first response alone.
Do you generate images and video too?+
Yes. Image Lite returns a 1K image directly, Image Jobs queues 1K bulk work, and Image Pro returns 2K or 4K images in an OpenAI-compatible response shape. Video is early access: Lite and Standard cover 4–12 seconds, Long covers 16–30 seconds, and each can start from text or an existing image. Resolution and audio are confirmed during setup.
How is image and video generation billed?+
Images are priced per delivered image: direct or async 1K starts at $0.0192, while Image Pro generates 2K or 4K. Failed image requests are not billed. Video is billed per generated second: Lite is $0.039, Standard is $0.079 and Long is $0.129. Confirm video failure billing during access setup.
Do we have to choose a model for every task?+
No. In your personalised routing policy, Omev recognises the task type and selects from its own models or model sequences using your client profile. Lite suits repeatable, constrained work; Pro covers more involved drafting and review. The benchmark establishes the route for your requirements.

Scale

Are there rate limits?+
No public throttling — your pipeline runs at your throughput. Higher plans get priority rate limits, and Enterprise sets custom limits by contract.
What if our volume spikes?+
No public throttling means your pipeline does not stall at the worst moment. On Pay as you go a spike is simply more tokens against your balance, so watch the balance rather than a quota. Enterprise sets custom volume and rate limits by contract.
Should we cache or deduplicate requests on our side?+
If your pipeline repeats identical requests and can reuse the same result, deduplicate or cache them before sending. On Pay as you go, repeated processing consumes tokens; per-finished-task billing is an Enterprise arrangement. Omev optimises execution within the requests you send.

Data & Enterprise

Is Omev a wrapper around ChatGPT or Claude?+
No. Omev runs its own models and automatically routes between them; it is not a catalogue of third-party models or a proxy to ChatGPT or Claude. The routing includes your task type, client profile, acceptance criteria, validation, repair and fallback. OpenAI compatibility describes the integration format, not the underlying model provider.
Do you train on our data?+
Yes, always, and we say so plainly. Every request you send helps train, evaluate and improve our models — that mandatory loop is part of why the price is what it is. There is no opt-out: if that use is not acceptable to you, do not use the Service. Raw content is kept no longer than 24 months, then deleted or irreversibly anonymised. Do not submit personal data on self-service plans, credentials or payment details, ever; Enterprise personal-data processing runs under a signed DPA. Read the AI & Customer Content terms →
Can Omev be customized to our specific task types?+
Yes, personalised task routing is available to every registered customer, not only Enterprise. Share your real requests and requirements. Omev groups the tasks, benchmarks its own models and builds a client-specific policy covering output format, brand rules, validation and recovery. Enterprise remains the option for individual commercial terms, dedicated support and contracted service targets.
Do you offer a white-label option?+
Yes, on Enterprise. Your brand, your domain, your client-facing keys and usage reports. Agencies and SaaS teams resell finished tasks under their own name while Omev runs the models, routing and validation behind the scenes.
Can you hold the latency our product needs?+
For Enterprise, yes: we size capacity to your workload and fix response-time targets (p95) in the contract, with a dedicated support channel. On standard plans there is no public throttling, and your live latency is visible in the dashboard, so you can measure us on your own traffic before you commit.
Does the output keep improving for our use case over time?+
Omev uses real production telemetry — cost, latency, validation outcomes, repairs and retries — to automatically improve your routing policy against the agreed acceptance criteria. The objective is a lower total cost per accepted output for your workload, while keeping your requirements as the reference.

Test it on your own prompts, not on our claims.

Register with your work email. We follow up personally to benchmark your real requests against your criteria and current costs. Start with one task type and a routing policy built for your workload.

Benchmark My Workload →

$5 free credit · 10 days · no card  ·  Keep your current provider connected