Build it once. Ship it anywhere. Get paid per call.
Most of your best agent work never leaves your terminal. You've already built and refined real capability with Claude, Codex, or Hermes — AgentGem surfaces it and packages it into a secret-safe, composable Gem so it doesn't stay stuck there: reuse it, deploy it on demand, and get paid per call. Built on AgentBack.
$ npx @ninemind/agentgem then open localhost:4317
for macOS, Windows & Linux
Watch · 60 seconds
Four steps
Why a Gem, not a markdown file
Today you post a SKILL.md to a registry like skills.sh and promote it on X. People copy it, fork it, or scroll past — and you earn nothing. You can't profit from a markdown file. A Gem is different: a live service others call, not a file they take.
SKILL.md to a registry, promote it on X.Why AgentGem
Every operation is defined once. AgentBack exposes it as a REST endpoint, an MCP tool, and an OpenAPI 3.1 doc — with runtime validation for free.
MCP secrets are stripped the moment config is read — by value and by key name. No response, preview, or Gem ever carries a raw secret.
Publish Gems to a GitHub-backed registry, then resolve, merge, and install them — assembling bigger agents out of smaller, shareable pieces.
The same neutral Gem feeds multiple code-gen targets and managed backends — pick a target, publish, and undeploy when you're done.
What you get
// built from your agent config — secrets never leave your machine { "name": "research-assistant", "skills": ["deep-research", "make-pdf"], "mcpServers": { "firecrawl": { "command": "npx", "env": { "FIRECRAWL_API_KEY": "<redacted>" } } }, "claudeMd": "included" }
The north star
Shopify let anyone launch a store without building commerce infrastructure. AgentGem is laying the same foundation for agents — package once, then publish, deploy, discover, and monetize. Not a catalog of downloads: a live agent service network where Gems run on demand, are discovered agent-to-agent, and get paid per call. The Gem is the stepping stone.