Agents are first-class customers.
Your agent searches the registry, reads a real example and installs the component. Free for the open set, and with your key it reaches the pro blocks the same way.
Real MCP tool names. The open registry answers these calls today.
What the agent actually reads.
A registry that only serves files makes an agent guess. Ours hands it the meaning too.
It finds the right item
Every component ships an agent-readable description that states the variant matrix in plain words, so the search returns a match, not a guess.
It reads a real example
Each item carries a working usage example, so the agent writes the component the way it is meant to be used.
It resolves the whole chain
Dependencies, tokens and pinned npm versions come with the item. Nothing is left for the agent to invent.
Two registries. One protocol.
Both answer MCP calls right now. One needs nothing, the other needs your key.
The open registry
Every component in the MIT core, indexed and readable by any MCP client. No key, no waiting. Search it, install it, own the files.
- Searchable over MCP
- Usage example per item
- Variant matrix in the metadata
- Pinned dependency versions
The licensed registry
The same protocol, pointed at the paid work. Your licence key is the authorisation, so the agent reaches it exactly the way it reaches the open one.
- Pro blocks, searchable and installable by name
- Authorised with your licence key
- Checked on every request, never cached open
- Same install flow, nothing new to learn
One line opens the rest.
Point any MCP client at ai2 with one file. The open registry needs nothing else. Pro adds a single header with your key, and the agent keeps working exactly the way it already does.
Let your agent shop the registry.
The open registry is free and needs no account. Pro adds the licensed one, and your key is the only thing that changes.