Agent Payment
Add Stripe-style USDC metering and billing to your API or agent tools with non-custodial flows and demo services to prototype without signup.
Overview
agent-payment is an MCP server for the Build phase that adds non-custodial, Stripe-style USDC API billing with eight free demo services and no signup required to try.
What is this MCP server?
- Stripe-style USDC billing patterns for APIs callable from agents
- Eight free demo services with no signup for local prototyping
- Non-custodial payment model emphasized in server description
- npm package agent-payment-mcp v0.9.1 with stdio transport
- stdio MCP server suited to Claude Code and desktop agent hosts
- Package version 0.9.1
- Eight free demo services, no signup
- npm identifier agent-payment-mcp with stdio transport
What problem does it solve?
You want agents to call paid APIs but lack a quick, crypto-native metering layer that fits MCP workflows.
Who is it for?
Solo builders shipping API or agent products who want USDC billing experiments without building a payment stack from zero.
Skip if: Teams that need fiat-only Stripe dashboards with no crypto settlement or no tolerance for pre-1.0 billing software.
What do I get? / Deliverables
You prototype and wire USDC-metered billing into agent tools using demo services first, then connect your production API surface.
- Metered USDC billing hooks for agent-callable APIs
- Prototype access via eight no-signup demo services
- Non-custodial billing integration path for MCP-hosted tools
Recommended MCP Servers
Journey fit
Monetization plumbing belongs in build when you wire backends and agent-exposed paid endpoints, before you scale distribution in launch and grow. Integrations subphase is where payment rails, webhooks, and MCP billing tools plug into your API surface.
How it compares
USDC billing MCP integration, not a generic Stripe CLI skill or marketplace plugin.
Common Questions / FAQ
Who is agent-payment for?
agent-payment is for indie API and agent developers who want non-custodial USDC metering exposed to MCP clients, with demos to learn the flow before production.
When should I use agent-payment?
Use it during build when you add paid tool endpoints or usage limits to an MCP server or backend, after core API behavior works locally.
How do I add agent-payment to my agent?
Install the npm package agent-payment-mcp (stdio) and add it to your MCP client config per evidai/agent-payment-mcp repository instructions.