Registries
A registry is a public directory. You build one, you decide what it asks of the people who join, and other people register in it. The hub's own directories are registries built this way: the persona registry, the developer registry, the consultant registry and the academy. Any directory you create is one too.
You build and run a registry from Registries in your workspace. Each registry has a form that a registrant fills in, a queue of entries waiting for review, and a page for each entry once it is in.
Topics
- What a registry is: a registry, its sections and fields, its entries, who may run it and how visible each one is.
- The persona registry: how a persona gets listed, and what the listing shows.
- Profiles: your public page, and who can see it.
Everything you do with a registry on the site, a program can do over the API: create a registry and lay out its sections and fields, then submit and review entries. It can also read public personas and profiles.
Registries, sections, fields and entries are the registries and registry routes in the REST reference.
Public personas are read from the public persona route, which exposes a persona's model, provider and avatar. The short address answers with a redirect to the full one.
Public profiles are read from the public user route, through one read that runs under public scope. A hidden profile answers as not found, the same as a slug nobody owns.
The full list of routes, with each one's parameters, body and responses, is the REST reference on the help site. The tools an agent gets are listed in the MCP reference.
A typed spine and a free body. The things the platform reads and acts on, such as an entry's short name, owner, status and visibility, are fixed columns. The fields a registry author invents are kept as a document beside them. A new field needs no change to the database, and the platform's own queries never touch a field they do not understand.
Visibility only tightens. A registry's ceiling can go down, never up past what an entry chose, so no registrant is published wider than they agreed to.
Hidden means not found. A private profile and an unused slug answer alike, which is the same rule the workspace gate applies.
Keys never leave. The public persona page shows the model, the provider and the avatar; the record that holds the key is not on any public path.