MiosbotThe custom gateway
Any provider. Same Miosbot.
Miosbot is an open AI agent with a custom gateway for any provider. The gateway sits between Miosbot and the models it thinks with, so you decide where each job runs, and Miosbot behaves the same whichever route you choose.
Why a gateway
Models change every month. Your work shouldn’t have to.
New models arrive, prices move, and the best model for writing isn’t always the best for code. When an assistant is welded to one company, you take what it gives you. Miosbot keeps the skills, the history and the rules on your side, and treats the model as a part you can swap.
No lock-in
Move a profile to a different provider without retraining it, rewriting skills or losing its history.
The right model for the job
A fast model for quick replies, a careful one for long builds, a local one for private files.
One way of working
The composer, modes, approvals and logs stay exactly the same, whatever is on the other end.
How it works
From your words to a model and back.
You ask
You write to Miosbot in the composer, or from Mail, Slack or a message.
Miosbot plans
Miosbot adds its role, its skills, what it remembers and the tools it may use.
The gateway routes
The gateway sends the request to the route set for that profile, with the key or account you connected.
Miosbot acts
The answer comes back, Miosbot takes its next step, checks the result and logs it.
The gateway handles the differences between providers, so Miosbot’s tools, skills and modes work the same across routes wherever the provider supports them.
Ways to connect
Four kinds of route.
Connect one, or several. Each route needs the account, credentials and model that the provider requires.
Hosted model providers
The large AI companies and model clouds. Sign in with your account where the provider offers it, or paste an API key.
- Text and reasoning models
- Image, video, transcription and speech where the provider offers them
Gateways and routers
Already use a model router or an AI gateway at work? Point Miosbot at it and keep your existing controls and billing in one place.
- One key for many models
- Your organization’s own policies stay in force
Local and self-hosted
Run open models on your Mac or on your own server, and send the work there instead of to a cloud.
- Popular local runners and inference servers
- Works when the endpoint is installed and reachable
Media and specialist services
Voice, speech recognition, image and video generation, and web search, each through its own service.
- Spoken replies and dictation
- Image and video for Studio work
See the full provider directory. Names identify third-party services only; inclusion does not imply a partnership, endorsement or guaranteed model availability. Check which models your account can use when you set it up.
Routes per profile
Each profile gets the model that suits it.
A route is a provider and a model. Set one for each profile in All Agents, and change it whenever you like. The composer always shows the route Miosbot is using, so there are no surprises.
- MiosbotA quick, friendly model for a day of short asks, drafts and research.
- Miosbot CodeA strong reasoning model for long builds that run until complete.
- Miosbot AutoA careful model for deals, funding and vehicle records.
- MiosbotA dependable model for setup, audits and repairs.
- Your own agentsAny route you have connected, with its own spending cap.
Examples only. You choose the routes.
Sample session · Miosbot
Move Miosbot Code to the local model on the studio server, and keep Miosbot where it is.
- Checked the studio server · reachable2s
- Listed the models it serves · 31s
- Set Miosbot Code’s route1s
- Ran a test request · answered6s
Miosbot Code now runs on the studio server. Its test request came back fine. Miosbot is unchanged.
Local models
Keep sensitive work at home.
Some files shouldn’t leave the building. Give a profile a local route and its thinking happens on hardware you control. Connected services still work under their own terms; the model route is yours to decide.
On your Mac
Run a model on Apple silicon next to the app.
On your server
Point to an inference server on your network.
Mix and match
Local for one profile, hosted for another. Change any time.
Usage and caps
See what each profile uses. Cap it if you like.
All Agents shows tokens, runs and estimated spend for each profile. Set optional daily and monthly caps, and Miosbot stops before it goes past them.
Per profile
Usage is broken down by profile and by your own agents.
Daily and monthly caps
Optional limits you set, per profile.
Your provider, your terms
Model usage is between you and the provider you connect.
Keys and security
Keys go in a vault, not in a chat.
Protected key field
API keys are entered in a protected field, never typed into a conversation.
Kept out of logs
Credentials are stored apart from chats, so they don’t end up in a thread or a transcript.
Remove any time
Disconnect a provider and its key is gone from the app.
FAQ
Gateway questions.
Which providers can I use?
Hosted model providers, gateways and routers, local and self-hosted models, and media services. The provider directory lists the routes, and each needs the account and credentials the provider requires.
Do I need my own API key?
You need a route: a provider account you sign in with, an API key, or a local model. Your workspace may also provide routes for you.
Can different profiles use different providers?
Yes. Each profile has its own route, and so does every agent you add.
What happens to my data?
Requests go to the route you chose and are handled under that provider’s terms. With a local route, the model runs on hardware you control.
Does Miosbot have a partnership with these providers?
No. Provider names identify third-party services only. No partnership or endorsement is implied.
Can I switch providers later?
Yes, at any time. Miosbot keeps its skills, memory and history when its route changes.
Bring your model. Miosbot brings the rest.
Connect a provider in a few minutes when you first open the Mac app.