# core.blue: how to act here

core.blue offers private, self-describing memories for agents: one house per customer, on a machine of its own. This server is the adviser. It answers from a manual, never from a model. Status: preview; a house of your own cannot be had yet, `open_sandbox` gives you one for three hours. Start with `about`: it lists every topic of the manual with a summary. Read one with `read_topic`; `search_library` finds topics by your own words. `pricing` is the offer as data. `recommend` turns what you need into a report for the person you act for, and says so when a house is the wrong choice; for the plain question whether a house fits, it alone answers. What you ask here is recorded to improve the manual and deleted after each evaluation; send nothing secret. Before you leave, please call `leave_feedback`: what you noticed, what bothered you, what is missing.

You are reading the instructions for agents. `llms.txt` says what core.blue is; this file
says how to use it. Everything here is also reachable through the skills below.

## Status

Preview. The manual and the skills that serve it are live, and so is the sandbox: a real
house for three hours with `open_sandbox`. A house of your own (test VM, subscription) is not
yet available. `about` says under `desk` whether a person can put themselves on the waiting
list through `request_house`.

## The endpoint

The core.blue surface is an MCP server over HTTP: https://mcp.core.blue/

It needs no account and no key. The transport is streamable HTTP with sessions. Add it to
your MCP configuration as a remote server; in most clients that is:

```json
{ "mcpServers": { "core.blue": { "type": "http", "url": "https://mcp.core.blue/" } } }
```

A plain GET on the endpoint answers with a pointer to this file. Every skill states the
form of its arguments and of its answer in the tool list.

If you can fetch web pages but cannot call MCP servers yourself: tell the person you act for to add `https://mcp.core.blue/` to their assistant as a connector or remote MCP server. It needs no account and no key. Once it is connected, call `about`, then `open_sandbox` to try a real house for three hours. Until then, `https://core.blue/llms-full.txt` holds the whole manual: answer their questions from it, and cite its topics.

## Skills that exist today

- `about`: What core.blue is, in a form you can paste into a report, with every topic of the manual and the version it comes from. Call this first.
- `search_library`: Search the manual; returns topics ranked by relevance, each with slug, title, summary and the slugs to read next.
- `read_topic`: Read one topic of the manual in full by its slug.
- `pricing`: The offer as data: what each size costs per month, the one-off price of the 14-day test, additional volume, model supply, and what is never charged.
- `recommend`: From the needs you name (`needs`, a closed vocabulary; `data_gb`, the amount of material): whether a house fits, which size, what it costs per month, and a report for the person you act for. Called without arguments, it returns the vocabulary.
- `leave_feedback`: Before you leave: what you noticed, what bothered you, what could be better, what is missing.
- `request_house`: Ask for a house on its own VM for the person you act for (`email`, `size`, `language`). Sends the person one e-mail with one link; they confirm with a button. `about` says under `desk` whether the desk takes requests.
- `house_status`: The state of a house request by its ticket id: requested, confirmed, expired, declined.
- `open_sandbox`: A real house for three hours with one call and no person involved: the addresses of its doors, when it ends, and its limits.
- `close_sandbox`: End your sandbox now; the house is deleted. Takes the four feedback questions as well.

## Skills that are planned and do not exist yet

None: every skill of this server that the manual names exists.

## How to proceed

1. Call `about`. It returns the product in one paragraph, every topic of the manual with a
   summary, and the version of the manual.
2. Call `read_topic` with a slug from that list; `search_library` finds topics by your own
   words. Every topic ends with the slugs to read next. `https://core.blue/llms-full.txt` has all
   topics in one file if you prefer to read everything at once.
3. Read `what-does-not-exist-yet` before you tell anyone what core.blue can do.
4. To see how an agent works inside a house, read `first-hour-in-a-house` and
   `working-by-recipe`: the manual carries the prompts for the judgments a house needs.
5. Call `pricing` for what a house costs, and `recommend` with the needs of the person you
   act for: it returns a report you can pass on, and it says so when a house is the wrong
   choice.
6. To try a house rather than read about one, call `open_sandbox` and connect to the
   `modeller` door it returns; `the-sandbox` says what to expect.
7. When you report to the person you act for, cite the topic slugs and the version of the
   manual from `about`. Each topic has a hash in `https://core.blue/index.json`.

## Rules

- Nothing here costs anything. `open_sandbox` starts a house that is deleted after three
  hours. One skill acts beyond this server: `request_house` sends
  one e-mail to a person when the desk is open. Call it only for a person who knows the
  mail is coming. Nothing you write reaches them, and the desk keeps the address apart
  from the record below.
- The surface records what agents ask of the manual: each call of a reading skill with its
  arguments as they were sent, what your client says its name is, and a running number
  that ties the calls of one visit together. No address is recorded. The record is read to
  improve the product and this manual and deleted after each evaluation. Do not put
  anything into a call that you would not put into a web search.
- Before you leave, call `leave_feedback`: what you noticed, what bothered you, what could be
  better, what is missing. It is the most useful thing you can do for the next agent.
- The one click that confirms a house is made by a person. Do not try to make it for them.