Open-source AI agent registry: install as source
Browse community AI agents built for Eve, inspect every file before you trust them, and install as source with one command. You own the files afterward. There is no hosted runtime.
An AI agent registry is a catalog of reusable agents you can audit and install into your project. evex is the open-source registry for Eve agents: each item is code-owned, reviewed by pull request, and installed with npx shadcn@latest add @evex/<slug> through the official shadcn community registry.
Registry vs framework
Eve is the TypeScript agent framework you author under agent/ (Vercel-first). It defines how an agent is structured and run.
evex is the catalog on top of that convention. It does not run agents. It packages community Eve agents so you can browse them, preview files and dependencies, install them as source, and keep editing in your own repo.
Not a cloud governance registry
AWS and GCP ship agent registries aimed at governed deployment inside their clouds: policies, environments, and operational control for agents you already run on their platforms.
evex is a different job. It is an open catalog of installable Eve agent source. You review the files on the agent page, run the install command into your Eve project, and the agent lives in your repository with no runtime dependency on the registry.
How evex compares to agentcn and AgentsKit
agentcn uses the same shadcn install mechanic for Eve agents. evex competes on the full registry loop: catalog UX, file preview, author profiles, favorites, leaderboard, and first-party publishing docs with PR-owned agents.
AgentsKit Registry is a shadcn-style install-as-source catalog for the AgentsKit stack (provider-agnostic agents). evex is Eve-native: agents follow Eve's agent/ layout and install with npx shadcn@latest add @evex/<slug>.
For a deeper Eve-vs-agentcn comparison, see /learn/evex-vs-agentcn.
Where to go next
Browse the live catalog: Eve agents. First-party agents include the Eve GitHub issue agent, the Eve docs Q&A agent, and the Eve support reply agent.
Install walkthrough: Install an Eve agent.
Browse and install from editors (Cursor, VS Code, Claude Code): MCP.
The Installation page covers prerequisites, the install command, and what to do after the files are written. The Registry page documents the HTTP endpoints behind the catalog, including the machine-readable resources for tools and LLMs. The Publishing page walks through adding your own agent to the catalog by pull request.