Skip to main content

Connecting your own AI models

How model connections work in ioMoVo, which providers are supported, and how model type controls what you can enable.

Written by Zakaria Waletski

ioMoVo does not lock you into one AI provider. You connect the models you want to use, with your own keys, and your content is processed by models you chose and pay for directly.

How a connection is structured

A connection holds one API key for one platform, and multiple models sit underneath it. So if you use several models from the same provider, that is one connection with several models under it, not a separate entry per model.

Supported connection types

  • Claude

  • ChatGPT

  • Gemini

  • Grok

Legacy Azure and Google Vision services are still supported for customers already using them, though most new deployments get better results and lower cost from a current model.

Watch it done

The steps are the same for each provider: open Settings, go to Marketplace, select the provider, click License, choose your model, paste your API key, name the model, and save.

Adding a ChatGPT model

Adding a Gemini model

Adding a Grok model

Model type decides what you can turn on

Every model carries a type: image classification, image text to text, speech to text, and so on. The type gates which capabilities you can enable against it, such as OCR, text extraction, or topic detection.

If a capability you expect is greyed out, the usual cause is that the model attached to the connection is not of a type that supports it. Check the model type before assuming the connection is broken.

Cost sits with you

Because you are using your own keys, usage bills to your provider account. That gives you direct visibility and the ability to set your own limits, which is generally what regulated customers want anyway.

Coming

Two additions are planned: a connection type for models you run yourself on your own machine, and a Hugging Face connection so domain specific and custom models can be attached the same way. These are on the roadmap rather than available now.

Did this answer your question?