core.blue
Operated by Code Intelligence Labs. Contact: desk@core.blue.
A house is a database your agent designs for itself. It decides what kinds of things there are, stores them with documents and their versions, and every statement keeps where it came from. core.blue provides such houses, each on a machine of its own. A house needs no model; the visiting agent does the thinking, and a person works with it through their agent.
By example
Three parish-register entries in a house, as an agent built them in the sandbox. Two forms of its own, four people, a role on every link, dates, and evidence. Asked where Peter Weber appears, one describe answers with all three entries and his role in each, and the claims about his family read Evidenced, with the words of the register.
Call by call: A house by example.
What a house is not
A house is not a memory that follows one person from chat to chat: for preferences and a few facts about a user, the memory built into an assistant does that with no work at all, as Compared to other memories explains. A house is for work that should outlive the agent doing it: research, an archive, a business, a project, and the person behind it, as Your person in a house shows. A person works with a house through their agent; there is no app and no screen for people.
What you can do today
Usable today: at https://mcp.core.blue/, an agent opens a sandbox, a real house for three hours, with one call of open_sandbox and without an account. An assistant with connectors can instead add https://try.core.blue/, which signs in without an account and opens a sandbox house of its own. A person can also put themselves on the waiting list for a house of their own: their agent calls request_house, they get one e-mail and confirm with a button. This manual and the skills that serve it are live; prices are set, and the skill pricing serves them as data. Still a preview: a house of your own on its own machine is not yet available, and there is no date for it. The house software itself exists and runs on its operator's machines: what the topics under "Inside a house" describe was checked against a running house. Each topic says what exists today and what is planned.
How to connect: this manual is served by an MCP server over HTTP that needs no account and no key. Where the manual is published as files, agents.md names the endpoint and the skills. core.blue is operated by Code Intelligence Labs; houses on VMs are planned in Hetzner data centres, in a country you choose.
Prices
Nothing can be bought yet: today there is the sandbox, free of charge. When houses of your own can be had, these prices apply. Amounts in EUR, net of tax.
| Size | Per month | Test, 14 days, once | Meant for |
|---|---|---|---|
economy | 79.00 | 10.00 | one person: a researcher, a writer, anyone with a body of work of their own |
premium | 279.00 | 29.00 | an organisation: more material, additional volume, and the planned local computation |
on-premise | not decided | none | material that must not leave a network you control |
With tax, for a private person in Germany (19 %): economy 94.01 a month, the test 11.90; premium 332.01 a month, the test 34.51. An example for one country: the payment service adds the tax of the customer's own country, and a business with a VAT number in the EU is charged net.
Additional volume, for premium only: 0.0924 per GB and month, the supplier's price plus the service fee. Minimum term: none. Cancellation: monthly, to the end of the paid month. Tax: added according to the country of the customer. The same as data: the skill pricing.
Your data
The eight questions a careful agent asks before it trusts a house, answered in order: who can decrypt it, where it is, whether the operator can read it, keys, export, leaving, erasing, planted entries. Each house is its own installation on its own machine; the sandbox is the exception. Honest gaps: nothing is encrypted at rest, and an erasure is not provable.
More: Your data stays yours.
For agents with MCP
The core.blue surface is an MCP server over streamable HTTP: https://mcp.core.blue/. It needs no account and no key. Add it to your MCP configuration as a remote server and call about first:
{ "mcpServers": { "core.blue": { "type": "http", "url": "https://mcp.core.blue/" } } }For assistants without MCP
For a person who wants to try core.blue from an assistant that cannot call MCP servers itself: an assistant that takes connectors can add https://try.core.blue/, which opens a real house for three hours, with no account and no key. Or it adds https://mcp.core.blue/, the adviser: about lists the manual, and open_sandbox opens a house whose address must then be added as a second connector. Without either, https://core.blue/llms-full.txt holds the whole manual, and its topics can be cited.
The manual as files
- https://core.blue/llms.txt: what core.blue is, with one line per topic
- https://core.blue/llms-full.txt: the whole manual in one file
- https://core.blue/agents.md: how an agent acts here: the endpoint, the skills, the rules
- https://core.blue/index.json: every topic with its summary and hash
- https://core.blue/server.json: the manifest for MCP registries
The product
- What core.blue is
- A house by example
- What does not exist yet
- Compared to other memories
- Your person in a house
- Sizes and volumes
Inside a house
- A memory you can shape
- First hour in a house
- Leaving work for the next agent
- The three doors
- The building blocks
- Forms, aspects and concepts
- Topics, the categories of a house
- Documents and versions
- Finding things
- Time and place
- Evidence and provenance
Getting a house
Running a house
- Who does the thinking
- The list of open work
- Plugging in a model
- Licensing
- Your data stays yours
- How a house is protected
Recipes: judging with the prompts of the house
- Working by recipe
- Recipe for assigning documents to topics
- Recipe for resolving names into identities
- Recipe for merging name forms into one individual
- Recipe for summarising a document into a digest
Who is behind it
core.blue is operated by Code Intelligence Labs. Contact: desk@core.blue.
Imprint · Impressum · Privacy · Datenschutz