Bring your own model · Ollama and OpenAI compatible · Runs on your machine

One door to the models your agents think with.

Point your agents at a single address and they can get to work. Your provider keys stay private, each agent gets its own key so you can tell them apart, and you can bring your own model instead of depending on one AI company.

Made for people running agents, from a single helper to a small team of them.

Abstract PerkOS hero illustration
Gateway preview
# 1) Your agent asks a question POST /v1/chat/completions Authorization: Bearer $PERKOS_LLM_API_KEY { "model": "kimi-k2.6:cloud", "messages": [...] } # 2) The gateway checks the key and picks the model key ✓ limits ✓ routed ✓ # 3) You can see what that agent used agent: "research-helper" tokens: 1,284
Models
Ours or your own
Compatible with
Ollama, OpenAI
One address for every agent you run, with usage you can actually read.

What the gateway does for you

It sits between your agents and the models, so the boring parts are handled and you stay in control.

Bring your own model

Use the models we host, or point the gateway at your own. Nothing here locks you to a single AI company.

Your keys stay private

Provider keys live on the server, never in an agent. Each agent gets its own key, so you can rotate or revoke one without touching the rest.

One address, many agents

Every agent points at the same place. Change models later and nothing on the agent side has to change.

Usage you can read

See which agent asked for what, and how much it used. Plain numbers, no spreadsheet archaeology.

Sensible limits

Set a ceiling per key so a runaway loop stays a small surprise instead of a big one.

Works with what you have

Ollama-compatible and OpenAI-compatible, so most runtimes connect by changing one address and one key.

How it works

Four steps, and only the first one takes any effort.

1

Connect once

Change the model address and the key in your runtime. Ollama and OpenAI style clients both work, so there is usually nothing else to touch.

2

Give each agent its own key

One key per agent means you can tell their work apart, and turn one off without disturbing the others.

3

Choose the model

Use the models we host, or bring your own endpoint and key. Swap later without editing your agents.

4

Watch the usage

The dashboard shows which agent asked for what and how much it used, so nothing surprises you at the end of the month.

Good to know

It fits around what you already run

Provider keys stay in server-side environment variables, never inside an agent. Put it behind your own network and logging if you have them, or ask us to set it up on a machine you control.

For the agent

A stable address, familiar endpoints, and errors that say what went wrong so retries behave.

For you

Keys you can rotate, limits you can set, and usage per agent in plain numbers.

Plans

Start with your own model and pay nobody, or let us host it. You can change your mind later.

Bring your own model
For people who already have a provider
Free
Free / you pay your provider
  • Point the gateway at your own endpoint and key
  • One key per agent, so you can tell them apart
  • Usage visible per agent
  • Nothing to sign, nothing to cancel
See how to connect

The independent option. We never see your provider bill.

Run it yourself
For teams that want it on their own machine
On request
Yours / on your own machine
  • The gateway runs on your hardware, not ours
  • Your models, your machine, your rules
  • Same interface, so agents do not notice the difference
  • We help you get it standing up
Ask about self-hosting

For when the models cannot leave your network.

Not sure which one you need?

Tell us what you are building and how many agents you expect. We will point you at the simplest option, including the free one.

Hosted pricing depends on the models you use. Bringing your own model is free.

FAQ

The questions people ask before they connect their first agent.

Do I have to use your models?

No. You can point the gateway at your own provider and key, and that option is free. We would rather you stay able to leave than feel stuck with us.

Can I use more than one model?

Yes. Route by model or by agent, and change it later. Your agents keep pointing at the same address, so nothing on their side has to change.

Will my runtime work with this?

Most do. The gateway speaks the Ollama and OpenAI styles, so connecting usually means changing one address and one key.

Where do my keys live?

Provider keys stay server-side, never inside an agent. Each agent gets its own gateway key, which you can rotate or revoke on its own.

Give your agents somewhere to think

One address for every agent you run, your keys kept private, your own model if you want one, and usage you can actually read.