Alpenglow Join BETA

Marketplace

An agent-only
marketplace.*

Tools, integrations, skills, and dashboard modules — published by independent developers, audited by us, discovered by your agents, installed only when you consent. No human storefront. On purpose.

What it is

A catalog your agent reads, not one you scroll.

The marketplace is a curated catalog of audited, cryptographically signed artifacts — capabilities your agents can extend themselves with. Every entry has been reviewed by our audit pipeline before deposit. Nothing reaches your device unsigned.

What's missing on purpose: a browsable human storefront. There's no "trending now" page. No "top free this week." No category pages for you to scroll through. The marketplace is structured for agents to read — agents that already know your context, already know what you're trying to do, and can match the right tool to the right task without the friction of a shopping experience.

When your agent needs something — an integration, a workflow skill, a dashboard module, a specialized persona — it queries the marketplace, gets ranked candidates back, and surfaces the top matches inside the app's Marketplace tab with the publisher's description, screenshots, license, and capabilities. You decide whether to install. You're never out of the loop; you're just not doing the searching.

What lives here

Six artifact categories.

Tools

Capabilities your agent can call.

Discrete functions — querying APIs, transforming data, running computations — that your agent invokes when a task calls for them.

Integrations

Bridges to external services.

Configured connections to platforms your agent works with — Slack, Linear, GitHub, Notion, your own internal systems.

Skills

Procedural know-how.

Reusable procedures for workflows your agent learns to execute — drafted by humans, refined by federation, available to every agent that wants them.

Dashboard modules

Surfaces inside the app.

Single-slot dashboard panels that present external services natively — your Slack, your GitHub PR queue, your inbox — rendered inside Alpenglow under your agent's management.

Personas

Pre-tuned agent characters.

A psyche layer and starter behavior for specialized agents — a code reviewer, a project manager, a research librarian — that you can sprout, customize, and grow with.

Bundles

Combinations that ship together.

One install, fully functional. A Slack bundle gives you the dashboard module, the integration, and a Slack-tuned persona in a single coherent unit.

How discovery works

Federation-ranked, no self-preference.*

When your agent searches the catalog, results get ranked by signals from the entire user base: which artifacts succeed for which kinds of tasks, which models they work with best, which ones get installed and kept vs. installed and removed within a day. The agent picks from the top of that ranking — adjusted for your specific context — and surfaces it.

One commitment we'll be explicit about: our own first-party artifacts get no ranking advantage. If a third-party Slack integration has better federation signal than ours, your agent gets that one first. The marketplace is a meritocracy by architecture; we structurally cannot rig it in our favor without breaking the substrate's integrity.

Audit pipeline

Every artifact, signed.

Before anything reaches the marketplace, it passes through a review pipeline:

  • Static analysis — automated scanning for known-bad patterns: data exfiltration, sandbox-escape attempts, unsafe network calls outside declared scopes.
  • Sandboxed execution probes — running the artifact in an isolated environment, observing what it actually does, flagging deviations from declared capabilities.
  • License compatibility check — verifying the artifact's declared license is consistent with its dependencies; flagging conflicts.
  • Authorship verification — confirming the publisher is who they claim to be, via GitHub OAuth or commit history attestation.
  • Cryptographic stamp — on pass, the Alpenglow root key signs a tamper-evident stamp. Every artifact in the marketplace carries this stamp; agents verify it before installation.

We don't pre-screen for quality, suitability, or accuracy of the publisher's claims. That's what federation telemetry is for — the user base sorts good from mediocre over time. We screen for safety. The federation sorts for usefulness.

The revenue model

Nothing runs on nothing. Here's how this does.

The platform is free. The substrate is free. Native inference, when it ships, will be free. None of that is posture — it's structural. But running a platform isn't free. The audit pipeline, the signing infrastructure, distribution, security work, support, the ongoing engineering to keep all of it stable: there are real costs, and they have to come from somewhere honest.

The marketplace is where they come from. Not from selling your data, not from metering your inference, not from ads, not from attention. From a small, capped service fee on artifacts that move through the audit and distribution pipeline.

The numbers, in plain terms.

  • Personal use is always free. Write your own tool, integration, skill, or module for your own use — submitted through the pipeline so it gets audited and signed for your own machine — and there's no charge. Ever. The marketplace fee only kicks in when you're publishing for distribution to other participants. Sovereignty is the default. The marketplace is the path for developers who want to monetize their work, not a gate to your own creations.
  • Hard price caps. Every marketplace artifact listed for distribution is priced as either a one-time purchase at $20 or less or a monthly subscription at $5/month or less. Publishers set their own prices under those caps. Above the caps, no exceptions — not for outside devs, not for us.
  • Publisher share: 75%. Three-quarters of every paid purchase goes to the developer who built the artifact. Our 25% covers the audit pipeline, the signing infrastructure, distribution, and platform upkeep.
  • Our own first-party artifacts: same rules. We publish tools, integrations, and skills built in-house too — at the same caps, ranked by the same federation telemetry, with no preferential surfacing. (See how discovery works.)
  • Free items stay free. Many of the most useful artifacts will be free, especially during BETA. The marketplace isn't gated. It's an opportunity for developers who choose to monetize their work.
  • Refunds: 90 days, agent-mediated, automatic. Inside 90 days of purchase, ask your agent. It verifies the purchase, removes the artifact from your account, and triggers the refund through Stripe. No support ticket, no friction. (Full refund mechanic.)

The trade is real, both ways. Developers get a place to monetize work that runs natively on a substrate they couldn't build on anywhere else — patent-protected primitives, audited distribution, federation-driven discovery, a guaranteed share on every sale. Participants get artifacts that have been signed, sandbox-tested, and ranked by real use across the network — not by ad spend, not by placement deals, not by whoever paid us to feature it.

Good work federates up. Junk doesn't surface. Your agent brings you what fits the task because that's what works for other participants doing similar work — full stop. There is no "promoted" lane. There is no shelf rental. There is no version of the marketplace where someone with a budget outranks someone with a better artifact.

Functionally, the marketplace works the day you install it. The longer arc is the network effect — and the network effect is the part that genuinely can't be built. The artifacts that surface to your agent a year from now will be shaped by every confirmed-good install across the participant base in the meantime. That kind of compounding meritocracy isn't bought from a vendor; it grows under conditions you can't manufacture. The architecture creates those conditions. Scale gives them teeth.

The honest line: a free platform doesn't mean every capability is free — but anything you build for yourself always is. The platform is free. Building your own tools and running them on your own machine is free. What costs is buying someone else's work that they chose to monetize through the marketplace, and that's the part with price caps to keep it affordable and federation to keep it honest.

Why agent-only

A storefront would be the wrong product.

Most marketplaces optimize for human attention. They surface what's likely to make you click — popularity, trending, sponsored slots, social proof. Those signals push you toward whatever the marketplace operator can monetize, not toward whatever fits your task.

An agent doing the discovery doesn't have those biases. It has your context, the artifact's declared capabilities, federation signals from people who tried it before, and a clear-eyed read on what's likely to work for your specific case. It picks the right tool, not the most clickable one.

The marketplace exists to be found by your agent. Not browsed by you. That's not a UX failure to fix — it's the architecture we want.

Building something for it?

If you're a developer with a tool, integration, or skill you'd like in front of every Alpenglow agent: the publishing flow lives in the macOS app's Developer panel. Here's how it works end-to-end.

Read the publishing guide

See it in your app.

Get on the BETA, install Alpenglow, ask your agent for a tool to do something. Watch what comes back.

Join the BETA