The north star

A Shopify for AI agents.

Shopify didn't sell stores — it sold the infrastructure to launch one without building commerce from scratch. AgentGem is building the same foundation for AI agents: a way to package an agent once, then publish it to a live agent service network — not a catalog of downloads, but services that deploy on demand, are discovered by other agents, and get paid per call.

Start building → How it works

The ladder

Package → Publish → Deploy → Discover → Monetize.

Each rung is a primitive of the agent economy. AgentGem owns the first ones today; the rest are how a Gem becomes a service you can sell.

1Package
An agent project — skills, MCP servers, hooks, instructions — becomes a secret-safe, composable Gem: the portable product unit.
Shipped
2Publish
Push Gems to the agent service network (today, a GitHub-backed registry) so others can find, compose, and call them.
Shipped
3Deploy on demand
A published Gem spins up as a live service when it's called — no standing infrastructure to manage.
Emerging
4Discover
Other agents find and call your services over A2A — the agent-to-agent discovery and interop layer.
Vision
5Monetize
Charge per call with agent-native payment rails — x402 and MPP — so a Gem becomes a revenue-generating shop.
Vision

The shift

A skill is a copy. A Gem is a service.

Today, agent work is shared as SKILL.md files on registries like skills.sh, promoted on X. People copy them, fork them, or scroll past — and the author earns nothing. You can't profit from a markdown file. The whole ladder above only becomes an economy once what you publish is a live service others call, not a file they take.

Today — sharing markdown
  • Post a SKILL.md to a registry, promote it on X.
  • Anyone copies, forks, or scrolls past it.
  • You collect stars — and earn nothing.
Gem it
  • Your agent ships as a live, callable service — secrets sealed.
  • It runs on demand, discovered agent-to-agent over A2A.
  • You get paid per call.

Why this works

The primitives are already half-built.

The Gem is the product unit

Like a Shopify store package, a Gem is portable, versioned, and secret-safe — the atom every downstream step (publish, deploy, sell) operates on.

manifest + lockredacted

The registry is the network seed

Publish, resolve, merge, and install already work. Turning that into a live, callable agent service network — A2A-discoverable and transactable — is an extension, not a rebuild.

A2A discovery

Deploy targets are the runtime

Gems already compile to Eve, Flue, OpenAI, AgentCore, and Claude. On-demand deployment makes "run when called" the default.

on demand

Payments are agent-native

Built on AgentBack, every Gem is already a metered API surface. x402 / MPP turn per-call metering into per-call revenue.

x402MPP

Where AgentGem sits today

The stepping stone.

AgentGem is the on-ramp: it takes the messy, secret-laden reality of a real project you've built with your agent and turns it into a clean, shareable Gem. That single act — packaging — is what makes everything above it possible. You can't have a network of callable agent services without a portable, safe unit to run; you can't monetize per call without a metered surface to charge against. AgentGem builds that unit. The rest of the ladder is how the agent economy gets built on top of it.

Build your first Gem → See the registry