CommunityOverview

Community

Agorio is open core: the SDK, all six governance plugins, and the merchant adapters are MIT-licensed, and anyone can publish compatible extensions. This section is the discovery and contribution hub.

Publishing a plugin

Anyone can publish an @agorio/sdk-compatible plugin to npm. There are two shapes:

  1. EnterprisePlugin — lifecycle middleware that hooks onBeforeToolCall, onAfterToolCall, onRegister, onInit, and hydrate?(state). The six reference plugins in plugins/ (spending-controls, approval-workflow, audit-trail, agent-identity, policy-engine, procurement) are the models.
  2. AgentPlugin — simpler; adds a custom tool (name, JSON schema, handler). Use this when you want the agent to call your function as a tool.

Recommended package shape:

@your-org/agorio-plugin-<name>/
├── src/index.ts          # exports your plugin factory
├── tests/                # at least one test against MockMerchant
├── package.json
├── README.md
└── LICENSE

Listing requirements (full details in docs/guides/community-plugins.md):

  • MIT (or another OSI-approved permissive license) to be listed; proprietary plugins are welcome but unlisted.
  • Clean npm audit on runtime dependencies.
  • Ship TypeScript types.
  • At least one test that runs against MockMerchant.

Open a PR adding your plugin to the plugins registry and a reviewer will confirm it installs cleanly into a fresh v1 project, has a documented README, and ships no telemetry to a non-customer-controlled endpoint by default. There’s no exclusivity — the registry is a convenience, not gatekeeping.

MigrationPlugins Registry