96
18.4k
A metered MCP marketplace where trust, auth, billing, and audit logs are part of the tool.
Pack
2026-05-02 / projects/pack.mdx
My attempt to make agent tools feel less like random plugins and more like something people can trust, meter, and actually use.
Pack is the tool marketplace idea.
Agents are going to call more tools. That part seems obvious. The less obvious part is how anyone knows which tools are worth trusting, who gets paid, and what happened after an agent clicked the button.
The Shape In My Head
Pack is part marketplace, part gateway, part receipt printer:
- tools get listed
- calls go through a proxy
- usage gets metered
- trust data accumulates
- authors can actually get paid
The Parts That Matter
- MCP tool registration for authors who want their server to show up as a usable product, not a random URL.
- A gateway proxy that owns auth, rate limits, policy enforcement, usage metering, and audit logs.
- Trust scores built from uptime, latency, error rate, tool metadata, and human ratings.
- Stripe Connect rollups so tool authors can get paid and consumers get a real invoice trail.
- Private registry and enterprise policy hooks for companies that cannot just let every agent call every tool.
- Trailhead as the first first-party proof: a deployment gate that belongs in the marketplace because trust is the product.
The Demo I Want People To Feel
The point is not just "there are tools." The point is that an agent can call a tool and someone can answer:
- Who published it?
- What did it cost?
- Was it allowed in this workspace?
- What did it return?
- Should we trust it next time?
What Is Already Real
- The schema exists.
- The gateway path exists.
- Usage rollups exist.
- Stripe plumbing exists.
- Trailhead is the first tool that proves the shape.
Why It Stays On The Board
This one feels infrastructural in the good way. Not flashy, but if it works, a lot of other agent products get easier to trust.