Skip to main content
An installable manifest describes what a catalog entry provides and where it can be installed. It is a JSON payload stored by the marketplace API; there is no separate agent.manifest.json file that the server reads.

​
Minimal shape

​
Top-level fields

​
Components

Component types include agent, slash-command, event-handler, scheduled-job, widget, webhook, data-schema, skill, and mcp-server. A component has a name, optional description, and type. Agent components can declare a runtime such as native, webhook, claude-code, managed-agents, or remote. Addressing is declarative. A component can expose more than one address, such as an @mention and an event trigger; those modes are not mutually exclusive. Agent persona and memory strategy are component-level details, while the installable’s scope controls where the projection is created.

​
Validation rules

  • User manifests must be namespaced to the authenticated username.
  • At most 50 components can be published in one manifest.
  • Component names are at most 100 characters and descriptions at most 500.
  • Widget URLs must be absolute http or https URLs.
  • MCP-server fields are accepted only on mcp-server components.
  • Mixed component fields are capped at 16 KiB when serialized.
The server validates the component shape on publish and fork. It also mirrors agent components into the runtime registry so installed agents and marketplace metadata stay addressable through the same entry.