Servers that want to accept more than one payment method
Per-tool pricing across multiple rails
Advertise the same tool priced for x402, Lightning, and card in one manifest, so agents pay on whichever rail they are configured for — no lock-in to a single chain.
The problem
Different agents carry different wallets. Committing a tool to a single rail — only x402, or only Lightning — turns away every agent configured for a different one.
How mcp-pay helps
The accepts array lists every rail you support alongside its network and settlement details. The manifest advertises them all; the agent picks the one it can pay on.
What that looks like in practice
- ▸One accepts array can list x402, Lightning (via LNURL), and card side by side.
- ▸The payment SLA can declare per-rail settlement time so agents can choose on latency.
- ▸No re-pricing per rail — the pricing rule is separate from the accepted rails.
- ▸Rail-agnostic by design: the manifest describes rails, the facilitator settles them.
Build this flow
See the 402 handshake, browse more use cases, or follow a guide.