About agentpay
Spending controls for AI agents: per-agent budgets, vendor allowlists, full audit trail.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @agentpay-run/mcp-serverAGENTPAY_API_KEYSecretAgentPay wallet API key (ap_test_... or ap_live_...). Generate at https://agentpay.run/dashboard.AGENTPAY_BASE_URLOverride for self-hosted or local dev. Defaults to https://agentpay.run.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
4Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| vendor | string | Yes | Vendor identifier. Domain form preferred ('openai.com', 'stripe.com'). Used for vendor allowlist matching and audit logs. |
| metadata | object | No | Optional free-form metadata stored on the transaction. Useful for tagging the agent run / task that triggered the charge. |
| amount_cents | integer | Yes | Amount in USD cents. e.g. 1200 = $12.00. Must be a positive integer. |
| idempotency_key | string | No | Optional key to prevent double-charging on retries. Re-sending the same key + wallet returns the prior result instead of creating a new charge. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.