Introducing the Connic Marketplace

Until today, the building blocks of a Connic project lived in separate corners of the site: an agent catalog here, a connector catalog there, retrieval sources somewhere else. As the catalog grew, that split stopped making sense. So we rebuilt it as one place: the Connic Marketplace.

What is the Connic Marketplace?

The Connic Marketplace is organized into three categories. Each one answers a different question that comes up when building an agent: where to start, what triggers it, and what does it know.

The storefront is curated rather than showing everything at once. It has a spotlight, category shelves, and a global search. Every category page adds facet filters and a full grid for browsing the complete catalog.

Agent templates: from catalog to running code in one command

Templates are complete, working agent setups, including examples like an invoice processor, a customer support triager, a Stripe dunning flow, and a Kafka fraud detector. Each template page shows the agents and tools inside, the file tree it scaffolds, and the connectors it expects.

Installing one is a single command:

pip install connic-composer-sdk
connic init my-project --templates=invoice

The catalog also supports multi-select: check several templates and the sticky command bar builds one connic init command that scaffolds them all together. The project repository receives plain YAML and Python rather than a black box. Teams can edit, extend, or remove any of it because they own the code. Our 2026 deployment platform comparison places this scaffold-and-deploy model in the wider market.

Connectors: the production path for triggering agents

Connectors are how agents plug into the systems where events already happen: a webhook from a SaaS backend, a Kafka topic, a Stripe event, a cron schedule, an MCP client. Each connector page documents its modes, configuration, and how it hands events to the agents.

The connector catalog itself has not changed; it now sits next to the templates that use it. A template page links directly to the connectors it expects, so an agent can be wired up from its template. Our connector pattern comparison helps with selection. The article on pre-built connectors explains their advantages over custom integration code, and the connector catalog lists the available options.

Retrieval sources: keep agents in sync with project content

The third category covers what agents know. Retrieval sources sync content into an agent's retrieval: Notion pages, Confluence spaces, Superhuman Docs (Coda) docs, or an entire website. Instead of one-off uploads, a source stays connected and keeps the retrieval current as the underlying content changes. The retrieval documentation explains how it works.

One publisher model, built for more publishers

Today, every listing in the marketplace is built, published, and maintained by us, and carries the Connic publisher badge. That is deliberate: everything installed from the marketplace is production-ready and supported.

Teams building something on Connic that belongs in the marketplace can talk to us. Self-service publishing is not open yet, but we are lining up the first external publishers now.

What happens to the old catalog pages?

The previous catalog URLs redirect permanently to their new homes: the agent catalog now lives at /marketplace/agent-templates, the connector catalog at /marketplace/connectors, and retrieval sources at /marketplace/retrieval-sources. Old bookmarks and links keep working; existing installations and configurations do not change.

Pricing is unchanged too. Marketplace listings are free to install and configure. Charges cover what running agents consume, billed as runs, compute, and storage like any other agent activity on Connic. The pricing page provides the details.