Private
Visible only to your company. Use this for internal tools that connect to proprietary systems or contain business logic you do not want to share. This is the default for all new apps.
The Sprigr App Marketplace is an extension system that lets you create custom tools your AI agents can use during conversations and workflows. Instead of waiting for platform-level integrations, you can write code that connects your agents to any API, database, or external system — and share those tools across your organisation or with the wider Sprigr community.
Think of marketplace tools as plugins for your agents. A tool might check inventory levels in your warehouse management system, pull invoice data from your accounting platform, generate compliance documents from templates, or fetch weather forecasts for scheduling outdoor jobs. If you can call an API or process data with code, you can turn it into a tool your agents can use.
Every marketplace listing is one of three kinds:
The Apps page is one catalogue with filter chips; the Agents chip shows agent templates on their own.
Every app in the marketplace belongs to a trust tier that controls who can see and install it. Three tiers are in use today:
Private
Visible only to your company. Use this for internal tools that connect to proprietary systems or contain business logic you do not want to share. This is the default for all new apps.
Shared
Reachable through a private share link. Shared apps do not appear in the public catalog, and anyone who has the link can view and install the app, so send it only to the companies you mean to share with. Useful when you work with partners, franchises, or affiliated businesses that would benefit from the same tooling without making it public.
Listed
Published to the public marketplace catalog after a Sprigr review. Anyone on Sprigr Team can browse, install, and use your app.
A fourth tier, certified, is reserved for apps that pass a deeper platform security and quality review. Only the Sprigr team can mark an app certified; there is no process to apply for it.
Apps start private. When you are ready to distribute one, open its detail page: Share generates a private invite link (the shared tier; once a link exists the button reads Copy Share Link), and List publicly submits the app for review. A Sprigr reviewer checks its scopes, write protection, a test install and its listing text; once approved it appears in the public marketplace catalog, and if it is not approved you are told why and can resubmit. While it waits, the app page shows where the review is and a Withdraw request button takes it back.
Building and deploying a marketplace tool follows a straightforward process:
Write your code — Click Create App on the Apps page and fill in the app’s name, description, tool details, and starter code. Then open the app in the built-in App IDE: a Monaco code editor with a file tree, syntax highlighting, and a test console. Write a handler function that accepts structured input and returns output your agent can use.
Test it — Use the Test tab to provide sample input and run your tool in a sandbox environment. Check the console output, verify the response shape, and iterate until it works correctly.
Deploy it — Click Deploy to bundle your code and make it available to agents. Each deployment creates a new version, so you can roll back if needed. Installations that track the latest version pick up the new version automatically (installers can instead pin to a specific version). Full apps built with the app kit are published from the terminal instead, with sprigr app validate, sprigr app dev, and sprigr app publish.
Agents use it — Once deployed, any agent with the tool installed can call it during conversations and workflows. The agent sees the tool’s name, description, and input schema, and decides when to use it based on the conversation context.
Search the Apps page by name, description, category or tag, or narrow it with the filter chips (one per app family, plus Agents, Installed and Published by you). Tags you add to an app are search terms: they help people find it, but there is no separate tag filter.
Apps are not limited to standalone operations. An app can declare a dependency on specific tools from another marketplace app installed in the same organisation (app_dependencies in its manifest) and call them at runtime with env.SPRIGR.invoke(tool, args). It can likewise declare integration_dependencies and call a connected integration through env.SPRIGR.integrations.invoke; today that works for Shopify only. The install consent screen shows the dependencies that need your sign-off, such as interface connections and fulfilment services; other dependencies are granted with the install. You manage the resulting grants afterwards — see App Permissions and Grants.
For example, a “schedule outdoor job” app might depend on a weather forecast app to check conditions and on your calendar integration to find available slots, with each dependency maintained independently.
Beyond plain tools, the platform gives app builders a set of capabilities that show up in the product as a user:
tools[].confirmation) covers actions that only need the agent to double-check.@sprigr/app-bridge): session hand-off, navigation, notifications, resizing, tool invocation, and event emission.Every marketplace app runs inside its own isolated sandbox on Cloudflare’s Workers platform, deployed per installation. This means:
The marketplace is designed to be flexible. Here are some examples of what teams are building:
Inventory alerts
Connect to your warehouse or spreadsheet system and alert agents when stock falls below reorder thresholds. Agents can proactively notify customers about availability.
Custom CRM connectors
Pull customer records, update deal stages, or log interactions in CRMs that do not have a native Sprigr integration yet.
Compliance generators
Generate safety checklists, inspection reports, or regulatory documents from templates using job-specific data.
Weather-based scheduling
Fetch weather forecasts and factor conditions into scheduling recommendations for outdoor work like roofing, landscaping, or painting.
The marketplace is not limited to tools. You can also install shared agents — complete AI agents with curated training data and a pre-configured persona. While tools add capabilities to your existing agents, shared agents are ready-to-use specialists you install into your company.
For example, you might install an Ecommerce Advisor agent that already knows about conversion metrics, customer lifetime value, and cart abandonment strategies. Or a Support Agent that comes pre-loaded with customer service best practices and escalation workflows.
Shared agents come with versioned training data snapshots, so the publisher can continue improving the knowledge base without disrupting your installation. You can also add your own company-specific knowledge on top.
Some apps need permissions beyond their own sandbox — for example, an app published by a partner that reads stock levels from your data, or an app that writes back to your connected Shopify or Xero integration. These permissions are modelled as grants: each one names a single tool the app may call, and you consent to them at install time. You stay in control afterwards: grants can be paused and resumed, and uninstalling the app revokes them all. When an update adds an app-to-app or event permission, it waits for your approval; new tools on an integration the app already depends on are added with the update. See App Permissions and Grants for details.
Ready to build your first app? Head to Creating Custom Apps for the handler contract, the runtime environment, the App IDE, and the app kit (@sprigr/apps-app-sdk and the sprigr app CLI).
Want to browse what is already available? Check out Installing Apps to learn how to find, install, and manage marketplace apps for your agents.
Looking for pre-built agents? See Shared Agents to learn how to install agent templates with curated training data.
Want to publish your own agent? Check Training Data for how to curate and manage knowledge bases for your agent templates.
You can also create and manage apps programmatically via MCP from your IDE — see MCP Overview for the create_app, install_app, and publish_version tools.