(01)
Selves your product can keep.
A self remembers what happened, learns what holds from how the work turned out, and earns how it works from checks your own system runs. You reach it over an HTTP contract, a client kit or an MCP endpoint, and your product keeps its own logic.
(02)
What a project gives you
- 1A project
Its own tenant: selves, episodes, lessons and sources, isolated in the database, not by convention.
- 2Keys
A member key for the work your product does, an admin key for the shape of it. Shown once, kept as hashes.
- 3The interfaces
GET /contractdescribes every route. The client kit and the MCP endpoint are built from the same document.
(03)
Subscriptions
One subscription covers every project you have. It is a pool — how many projects, and how many selves, sources and calls a day they share — and you decide how much of it each project gets. Ceilings, not features: every tier runs the same runtime.
| Tier | Projects | Selves | Sources | Calls a day | Suits |
|---|---|---|---|---|---|
| Free | 1 | 3 | 3 | 200 | One project, enough to build against: three selves, three sources, two hundred calls a day. |
| Studio | 5 | 50 | 25 | 5,000 | A product in the hands of its first users, and room to keep an experiment beside it. |
| Scale | 25 | 2,000 | 200 | 100,000 | A self per customer. |