Publish an agent
The catalogue has no accounts and no upload form. Publish a package to npm with the two markers below, and it appears here the next time the catalogue is built.
What the catalogue looks for
- The keyword
standardagentin the package'skeywords. - A
standardagentfield inpackage.jsonwhoseentryAgentslists at least one agent.
Both come from the specification's Packaging page. A package with the keyword but without the field is left out.
{
"name": "standardagent-my-workflow",
"version": "0.3.1",
"type": "module",
"main": "./dist/index.js",
"keywords": ["standardagent"],
"standardagent": {
"entryAgents": ["my_agent"]
},
"peerDependencies": {
"@standardagents/spec": ">=0.2.0"
}
}What an agent's page shows
- Entry agents, from
standardagent.entryAgents. - Effects and thread endpoints, when the field lists them.
- Hooks the agent adds to a parent that composes it, from
standardagent.parentHooks. - The
@standardagents/specrange inpeerDependencies. - Version, licence, publisher, and links, as npm reports them.
Providers and tooling
A package that supports agents without being one is listed under Ecosystem when it carries the standardagents keyword. Adding provider to the keywords places it with the model providers.
To remove a listing, remove the keyword and publish a new version, or unpublish the package from npm. The catalogue only mirrors what npm reports.