Use cases
Five complete walkthroughs on the hosted SDK and the MCP server, with every snippet lifted from code that runs.
Each use case is one working walkthrough, read end to end. The status page is a Next.js app that stores its data in a workspace and keeps serving during an outage. The agent workflow connects Claude Code to the same workspace and shows what a narrowed key changes on the wire. Skills and memories teach the workspace agent a skill with records, then show what it remembers and who may change it. Nested notes builds a tree of notes, then moves it and shares it from its root. Vibecoding follows the model catalogue from one schema file to a back office, a typed API and an agent that reads the same records.
Status page
Declare five objects, sync them once, and serve a public status page that keeps answering when Standards is unreachable.
Agent workflow
Connect Claude Code, read and write records through the MCP tools, then watch a read-only key remove the write tools and refuse a call.
Skills and memories
Teach the workspace agent a skill with the records API, then watch what it learns about one of your records land on that record's memory page.
Nested notes
Declare a hierarchical notes object, write sub-notes from the editor, move one between trees and share a whole tree from its root.
Vibecoding
One TypeScript file becomes a back office with work queues, a typed API and a tool your agent can query. The model catalogue, from schema to production.
Next steps
- Records: the query API both cookbooks build on.
- MCP tools: the full catalogue the agent workflow narrows.
- Workspaces and API keys: the permissions behind every refusal shown here.
- Book a demo