Agents that keep working

Your own agent. It asks first.

Define an agent without code: what it is for, how it speaks, the skills and knowledge it has, a schedule and the tools it may use. Chat with it in real time. When it wants to do something risky, it stops and waits for a person to say yes.

Request access See how it works

Early access, by request. A working name. The windows on this site show sample data.

approvals · 1 waitingwaiting
a risky tool always waits

Connects toGeenius OSany MCP serverthe weba webhook

Four windows
Four windows from Agent host: a definition, a chat, an approval and a digest. Sample data.

Agents as data

No code, every save a version.

An agent is a definition: a description, standing instructions, a persona, skills and knowledge as text, a model tier, connectors, tools, a schedule and limits. It is validated when you save, stored as an immutable version and obeyed by the runtime. Deploy a version, roll back to another, and the agent follows.

  • Skills and knowledge are text in the prompt
  • Templates to start from: inbox triage, research digest, a Geenius OS project reporter
  • Folders, tags and favourites for a library

How agents are defined

definitionas data
every save is an immutable version

The risk rule

One rule decides what asks first.

Reading the web is safe. Every connector tool is risky unless you listed it as read-only. A webhook is always risky. Anything the rule does not know is risky. A risky call is suspended inside the agent and appears in the approvals inbox; the agent waits until a person approves or denies it.

  • The approval gate reads only this rule
  • A decision is recorded and the agent is told
  • No one can approve through the AI door

How approvals work

the risk rulesafe · risky
the approval gate reads only this rule

Schedules

It wakes up and leaves a digest.

Give an agent a schedule and a prompt, and it wakes by itself: read the pages you follow, report what is open in your projects. The last result is kept as a digest you can read, and your own AI can read it too through Geenius OS.

  • From every minute on Max to every hour on Pro
  • A hard stop on tool calls a day
  • Logs and costs per run

Schedules

research-digest · scheduleevery 24 h
a scheduled agent leaves a digest

Your model

Your own key, or built-in credits.

On Pro an agent runs on the model key you add; it is sealed and never shown again, and the deployment's keys are never used for your workspace. On Premium and Max agents run on the built-in AI and a month's credits are counted per step, by model tier. A tool-call limit a day is a hard stop, not a bill.

  • Pro: 1 agent, your own key
  • Premium: 3 agents, 1,000 credits
  • Max: 10 agents, 3,000 credits

Models and credits

usage412 / 1,000
what the plan holds and what is used

A door for your AI

Your AI can watch and talk. Not decide.

Connect Claude, ChatGPT or Grok to Geenius OS once. Your AI can list your agents, send one a message, read a digest, look at the approvals queue and check usage. It has no approve action: otherwise an AI could approve its own webhook, which is what the gate exists to prevent.

  • One tool, six actions
  • On every plan
  • Connector secrets are never readable

Connect your AI

your AI · geenius_agenthostwatch · talk
the door has no approve action

In numbers

Facts you can check, not testimonials.

Agent host is in early access and has no public customers yet. These are things you can look up in the app and the docs today.

  • 1rule decides what is risky, and the gate reads only that
  • 3built-in templates: inbox, research digest, OS project
  • 6actions on the AI door, none of them approves
  • 10agents on Max

Honest labels

What works today.

We say what is live in early access, what depends on your setup, and what is not offered.

  • Pre-beta
    Agents, chat, connectors, approvals, schedules and versions

    Built and in the app now. Early access: people request access.

  • Pre-beta
    Built-in AI on Premium and Max

    The model is called through the hub with the deployment's keys. On a development deployment without keys an offline stand-in answers; there is no such stand-in for a customer.

  • Pre-beta
    Limits and credit costs

    The plan limits and the cost of a model step per tier are the current values and may change before plans are sold.

  • Pre-beta
    The name

    Agent host is a working name.

  • Not offered
    Your own code

    An agent is data: there is no code to run.

  • Not offered
    Approving through your AI

    Only a person of the workspace decides an approval, in the app.

Four ways
Four ways to use it. Sample data.

Pricing

Three plans. No free tier.

Per month, in euros, VAT included. Included in the matching Geenius OS plan. Payments are in test mode during early access.

  • €9Pro: 1 agent, your own model key
  • €19Premium: 3 agents, 1,000 credits
  • €49Max: 10 agents, 3,000 credits

Questions

Good questions.

What is Agent host?

A place to create and run your own agents without code: persona and instructions, skills, knowledge, schedules, tools through MCP connectors, a real-time chat and an inbox for approvals of risky actions. It is an app of Geenius OS and also works on its own.

Is Agent host the final name?

No. It is a working name and can change.

Is it ready to use?

It is in early access: people request access and payments are in test mode. What this site describes is built. Request access.

Do I write code?

No. An agent is a definition: text, settings and tools. There is no code to run.

Who makes it?

AVS Media, a small company in Nijmegen, the Netherlands, as one of the apps of Geenius OS.

Do I need Geenius OS?

No. Agent host has its own account and plans. A Geenius OS plan includes the matching plan, and Geenius OS is the first connector an agent can use.

All questions

Give it a job.

Agent host lets people in step by step. Ask for a place, or sign in with Geenius OS.