DreamerOS
WHAT IT DOES, AND WHAT IT DOES NOT

What DreamerOS does.
In plain words.

An AI that can reach your mail, your files and your money is a frightening thing to hand a stranger. It should be. Most people do not want a clever assistant. They want to know what it can touch.

DreamerOS is one place to work with the big AI tools, and it remembers you between them. It checks each answer before you get it, and hands you a receipt saying what it checked. You can open the doors below and read those checks yourself, right now, without an account.

The scary bit is real.
So here is the line.

What DreamerOS does not do without you

  • It does not reach any account of yours until you connect that account yourself. Nothing is connected the day you sign up.
  • Before you connect a tool, the app tells you in plain words what it reads and what it can change. You say yes, or it does not happen.
  • It cannot touch a tool you never connected. There is no back door, and no default list.
  • Every answer carries a receipt naming the checks that ran. You can read it, and you can hand it to anyone.
  • You can look up any receipt without logging in. So can the person you gave it to.

Four doors.
No account. Open them yourself.

The panels below are not typed into this page. Your browser asks the DreamerOS gateway for them as you read, and prints what comes back. Each panel shows the address it asked. Paste any of them into a new tab and you will see the same thing we did.

Which engines are answering

DreamerOS puts your question to one of five engines. This door names them and says which are up at this second.

asking the gateway...
https://api.dreameros.app/api/v1/public/engine-status

How many receipts have been signed

Answers come with a signed receipt. This door counts them, and says when the first one was issued.

asking the gateway...
https://api.dreameros.app/api/v1/receipts/stats

How many tools your AI can call

DreamerOS hands a set of named tools to whichever AI client you connect. This door publishes the whole set and how many each plan reaches.

asking the gateway...
https://api.dreameros.app/api/v1/agent/manifest

How any AI tool plugs in

The public contract that lets any client, even one we have never heard of, pick up your memory. We publish it, so nobody needs our permission to build against it.

asking the gateway...
https://api.dreameros.app/.well-known/dreameros-continuity.json

If a panel says it could not read a door, that is what happened. We would rather show you a blank than a number we cached last week.

What it does today.
Every one of these is running.

Each card says the thing in plain words. Who gets what is on the plans page. The grey line at the bottom of each card is for the engineer in the room. It shows what talks to what, over what, with what permission, and how far it goes.

1

One key, and the AI tools you already use

Connect DreamerOS once with one key, and any client that speaks MCP can reach it. Claude Desktop, ChatGPT, Cursor, VS Code, Windsurf, Claude Code, Codex, Lovable and Base44 all speak it. One key opens all of them and you are not charged per tool. The connection itself is live. We are still working through a fresh customer test of each client's own setup steps, and the setup page says which ones have passed so far.

client -> gateway | MCP over streamable HTTP | Authorization: Bearer dros_* key | one key, no per-client limit
2

A named tool set your AI can call

Your AI does not guess what DreamerOS can do. It reads a list of named tools and calls the one it needs. The live count is in the panel above, read straight from the door.

client -> gateway | MCP tools/list | Bearer | set filtered per plan at call time, not at connect time
3

Five engine families, one answer

ChatGPT, Claude, Gemini, Grok and Perplexity. DreamerOS picks one for each question, and you can pick one yourself. If one of them is down, another takes the question instead of failing.

app -> gateway | POST /api/v1/actions/select-engines | Bearer | engine count set by plan, server side
4

A receipt on every answer

Answers come with a signed receipt naming the checks that ran. If a daily receipt cap is reached, it resets at midnight UTC and the answer still arrives in full. Reading receipts you already hold is never capped.

anyone -> gateway | GET /api/v1/receipts/{id} | no auth | public lookup, signed, resolvable by the person you handed it to
5

Checks with a published price list

There are four depths of checking, from a free structural pass to an exhaustive one. The gateway publishes what each depth does and what each costs, so you can read the price before you spend anything.

Who can use it: the free and default depths are open to anyone. The two deeper depths depend on your plan. anyone -> gateway | GET /api/v1/verify/depths | no auth | four depths, cost in USD, self-disclosed
6

Memory that follows you between tools

What you told it last week is still there next time, whichever tool you open it in. Your context lives with DreamerOS, not inside one chat window, so switching device or vendor does not wipe it.

any client -> gateway | GET /.well-known/dreameros-continuity.json | no auth to read the contract | endpoints, response headers and anchor counts per plan
7

A session hands over to the next one

A session can close by writing down where it got to, and the next session reads that first. You stop paying, in time and in patience, to explain yourself again.

Who can use it: anyone signed in, in the app. Handing that note to a connected engine depends on your plan. app and MCP -> gateway | session handoff write and read | Bearer | in-app every plan, connected-engine export paid
8

Thirty-seven skills you call by name

Named jobs you can ask for directly inside any client you connected, instead of describing the same task from scratch every time. They are free. They always were.

client -> gateway | MCP tool dreameros_skill | Bearer | 37 named skills, no plan floor above sign-in
9

Hand it a file, a picture, audio or video

Drop it in and ask about it. DreamerOS reads video two ways at once: what is said and what is on the screen. You can ask about either.

Who can use it: anyone signed in. app -> gateway | file, image, audio and video ingest | Bearer | attached files up to 20 MB, attached video up to 200 MB, video in a voice message up to 15 MB, plain upload 10 MB
10

More than one ear on your audio

Transcription is where most tools quietly guess. DreamerOS can run more than one transcriber on the same audio and take the reading they agree on.

Who can use it: how many transcribers run on your audio depends on your plan. app -> gateway | speech to text, multi engine merge | Bearer | transcriber count set by plan
11

Your rules, exported into 21 other AI tools

Write down how you want an AI to behave once. DreamerOS turns that into the file each of 21 other tools expects, so they all behave the way you set it here.

app -> gateway | direction set export | Bearer | 21 vendor formats, one gate, no per-vendor limit
12

Timestamped proof you thought of it first

Write an idea down and DreamerOS stamps it, so later you can show when you had it. The stamp has a link anyone can open. No daily limit on stamps.

Who can use it: anyone signed in. Anyone with the link can look a stamp up. app -> gateway | idea notary write and lookup | Bearer to write, no sign-in to read | no daily limit on writes
13

It can read a live web page and act on it

Not a stale copy from a search index. It opens the page, reads what is there, and can fill something in for you. Anything it changes leaves a receipt.

Who can use it: depends on your plan. gateway -> hosted browser | read and act | Bearer | receipt written for every change
14

Bring your own model

Already paying for a model somewhere else, or running your own? Point DreamerOS at it. You keep the model, you keep the bill, and the checks still run.

Who can use it: anyone signed in. client -> gateway | MCP tool dreameros_byollm | Bearer | your endpoint and your key, per provider
15

An image and video studio in the app

Make pictures, edit the ones you made, and make short video where your plan includes it. How many you get a month depends on the plan, and the app shows you your own count.

app surface /media | web, signed in | session | per-plan monthly counts resolved server side
16

The record of what was decided

DreamerOS keeps every check it ran on your behalf. You can go back weeks later and see what it decided and why. It is your record, not a summary we wrote for you.

Who can use it: anyone signed in. app -> gateway | decision record read | Bearer | per-member scope
17

Scanned PDFs get read too

It never edits your PDF. It reads a copy, even one that is only pictures of pages, and gives you the text back.

Who can use it: anyone signed in. app -> gateway | scanned PDF text recovery | Bearer | automatic, no toggle, every plan
18

Up to five checks, no shared blind spot

19

The receipt shows which rules and which engine

Every receipt names the version of your direction set that ran the turn. It also names which engine answered.

gateway -> receipt | direction set version and engine on every answer | Bearer to fetch | same fields, every plan

What we are building next.
Listed here, so you always know where the product is going.

Each line below is on our roadmap. None of it carries a price, because we only price what we can hand you today. It is here so you can see exactly where the product is going.

Buying an extra engine slot on top of your plan on the roadmap
A bundle that adds automations and better image tools to a smaller plan on the roadmap
Automations on the smaller plans, plus one packaged automation on the roadmap
The top picture and video allowances sold on their own, without moving plan on the roadmap
Three transcribers on the smaller paid plans on the roadmap
The deepest check on the smaller paid plans on the roadmap
Exporting your rules into other tools from the free plan on the roadmap
Reading and acting on live web pages from the free plan on the roadmap
Buying a bigger memory ceiling without changing plan on the roadmap
Scoring your own text for intent fidelity from your own code, self serve on the roadmap
One feed of your errors and deploys across connected services, on the smaller plans on the roadmap

Every line above sits on our roadmap, waiting on the piece still being built or the permission switch we plan to flip. We sell a capability only once you can use it.

Read the plans,
then try the free one.

The free plan carries the memory, the receipts, the skills, the file reading and the one key that opens every client above. You do not have to pay to find out whether this is for you.

See what it does on your own question Try DreamerOS free