Writing
Notes from drafting the v0.1 spec.
Design questions we hit while shaping the manifest, the 402 flow, and where metering lives. Written for MCP server builders.
-
Wallet-side vs server-side metering for agentic spend
Who counts the calls? The wallet, the MCP server, or both? A look at the tradeoffs mcp-pay's v0.1 schema makes, and why the answer ends up being 'both, but for different things'.
protocolwallets -
Designing payment flows that don't break the LLM call
Most payment flows assume a human at the other end. Agentic calls have a tighter latency budget and a smaller error tolerance. Here is what the v0.1 mcp-pay flow does to stay inside both.
protocolagents -
Why MCP servers need payment awareness, not paywalls
Paywalls are 1990s vocabulary for a problem agents need to solve differently. mcp-pay treats payment as metadata an agent can read at /.well-known/, not a wall it has to bounce off.
specdesign