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 marketplace is organized into three categories. Each one answers a different question you hit when building an agent: where do I start, what triggers it, and what does it know.
The storefront is curated, not a dump of everything at once. You get a spotlight, category shelves, and a global search. Every category page adds facet filters and a full grid when you want to browse exhaustively.
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=invoiceThe catalog also supports multi-select: check several templates and the sticky command bar builds one connic init command that scaffolds them all together. What lands in your repository is plain YAML and Python, not a black box. Edit it, extend it, delete half of it. It is your code. For how this scaffold-and-deploy model fits into the wider market, survey the 2026 agent deployment platform landscape.
Connectors: the production path for triggering agents
Connectors are how agents plug into the systems where your events already happen: a webhook from your 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 your agents.
The connector catalog itself has not changed, but it now lives alongside the templates that use it. A template page links directly to the connectors it expects, so the path from "this looks useful" to a wired-up, triggerable agent is one continuous flow. To go deeper on how connectors compare, read the connector pattern comparison, see why pre-built connectors beat custom integration code, or browse the connector catalog.
Retrieval sources: keep agents in sync with your content
The third category covers what your 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. Read more about how the retrieval works.
Agent templates, connectors, and retrieval sources in one catalog. Free to install; you only pay for what your agents consume when they run.
Explore the marketplaceOne publisher model, built for more publishers
Today, every listing in the marketplace is built, published, and maintained by Connic, and carries the Connic publisher badge. That is deliberate: everything you install from the marketplace is production-ready and supported.
If you are building something on Connic that you think belongs in the marketplace, 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; nothing you installed or configured changes.
Pricing is unchanged too. Marketplace listings are free to install and configure. You pay for what your agents consume when they run, billed as runs, compute, and storage like any other agent activity on Connic. See how Connic pricing works for the details.