Agentic Developer Hub

You ship the part only you can.

The Hub doesn’t live alone. It sits between the Cookbook and the Dev Team — recipes and team-shaped workflows for how to build an AI persona — the Persona Toolkit, the runtime layer that wires a persona into your app, and the Persona Registry, its public face on the open web.

Five pieces, one job each. Everything is composable, with one token to bind them.

Developer Cookbook

Knowledge. Teaches it. Principles, guidelines, ingredients, and recipes for AI-assisted development. The shared knowledge base everyone — humans and AI agents alike — works from.

Developer Team

Process. Builds it. A coordinated set of AI agents that do software development and project management work, governed by the Cookbook. Multi-agent discovery, analysis, and building that ships into the Hub.

Developer Toolkit

Boots on the ground. Runs it inside your app. The runtime connector and orchestrator that lives in your product. Per-platform SDKs for Web, Apple, Android, and Windows that pull Hub personas, persist state, and run the chat UI.

Developer Hub

Services · Identity · Data · Ops. Holds the data. The center, and this site. Everything below is here.

Persona Registry

Public storefront. Shows it to the world. The face the world sees. Public persona profiles and LLM provider wiring, published to the open web. Where Bob the dog-namer lives at his own URL.

Casey wants to ship Dognamr.com — an AI that suggests names for dogs. The whole thing is going to be powered by a persona called Bob. Here’s how Casey uses the Agentic Developer Hub to make it happen.

1. Register Bob. Casey creates Bob in the hub: name, bio, capabilities, model preferences. Bob’s public profile lives on the Agentic Persona Registry, and logging in from there brings Casey back here.
2. Give Bob a brain. Bob’s system prompt, his breed dictionaries, his guardrails — Casey drops them into the Persona Data Store, scoped to Bob and Casey’s Dognamr project.
3. Remember the visitors. Every Dognamr visitor pins a few favorite names. Casey writes that state to the User Data Store, scoped to the same project, so it follows the visitor across devices.
4. Bundle into a project. Casey creates the Dognamr project — pulling in Bob, Bob’s data, the visitor user-data namespace, and a status group for dognamr.com and its endpoints.
5. Mint an application token. Casey creates the Dognamr application inside that project and mints a token. The token can read Bob, write to user data, and post status — and nothing outside that project.
6. Wire the surfaces. Dognamr.com talks to the REST API. Casey’s coding agent talks to the MCP server. Same auth, same project — different ways in.
7. Watch the lights. The Dognamr status page groups dognamr.com, the breed-classifier endpoint, and the hub APIs Bob depends on. When something blinks red at 2am, the whole picture is one URL.

The story in full, piece by piece →

Each is usable on its own, and they compose: a project bundles the ones you need, and an application inside it carries a token scoped to exactly that.

Sign in and create a persona, a project, and the token that binds them. Next in the story: Agentic Developer Hub Help, where the topics are.