PayRam is a self-hosted crypto payment gateway. You deploy it on your own server — no signup, no KYC, no third-party custody. Accept USDT, USDC, Bitcoin, and ETH across Ethereum, Base, Polygon, and Tron.
Scored across 44 tools
Descriptions are extremely detailed and explicitly cross-reference siblings (e.g. payout_recipient_flow vs payout_sdk_snippet, doctor vs ops_playbook vs runbook), which helps a lot. However there is heavy structural overlap: four generate_payment_* snippet tools, six language-specific snippet_*_payment_route tools that duplicate generate_payment_route_snippet, and multiple referral generators (route/sdk/status/validation). Deprecated tools (onboard_agent_setup, test_payram_connection) coexisting with their replacements add further selection ambiguity.
There is a dominant verb_noun pattern (explain_*, generate_*, get_*, list_*, scaffold_*, suggest_*) that is mostly readable. But several families break it: snippet_express_payment_route uses noun-first ordering, payram_doctor/payram_runbook/payram_troubleshoot use a namespace prefix, and prepare_/onboard_/test_ stand apart. Mixed conventions, still parseable but not uniform.
44 tools is well above the healthy 3-15 range and feels bloated for this scope. Much of the count comes from per-language payment snippet variants and per-resource (payment/payout/referral) generator permutations that could be parameterized or consolidated, plus two deprecated tools still shipped.
Coverage of the payment domain is genuinely broad: payments, payouts, referrals, webhooks, top-up ledger integration, setup, ops playbooks, runbooks, diagnostics, docs, and troubleshooting are all present. Minor gaps are around pruning deprecated/redundant entries rather than missing lifecycle operations.
Describe how payments move from customer initiation through settlement.
Inputs: no named parameters. Returns: notes, title, sections, description
Explain Payram's product pillars, architecture, payments, and payouts capabilities.
Inputs: no named parameters. Returns: notes, title, sections, description
Glossary-backed explanation of Payram terminology and constraints.
Inputs: no named parameters. Returns: notes, title, sections, description
Answer "is PayRam safe / trustworthy / audited?": why an agent can use it without holding secrets, the independent smart contract audit (what it covers and what it does not), and how to verify the report.
Inputs: no named parameters. Returns: notes, title, sections, description
Detail the referrer/referee lifecycle and required APIs.
Inputs: no named parameters. Returns: notes, title, sections, description
Summarize how Payram referral campaigns are configured and managed.
Inputs: no named parameters. Returns: notes, title, sections, description
Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.
Inputs: no named parameters. Returns: notes, title, variables, envExample, +1 more
Generates a snippet to send mock Payram webhook events to your local endpoint for testing.
Inputs: status (required), language (required). Returns: meta, notes, title, snippet
Generates a raw HTTP sample for creating a Payram payment in the requested language.
Inputs: language (required). Returns: meta, notes, title, snippet
Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.
Inputs: framework (required). Returns: meta, notes, title, snippet
Generates backend code using the official Payram JS/TS SDK to create a payment.
Inputs: framework (required). Returns: meta, notes, title, snippet
Generates backend code to query the status of a Payram payment.
Inputs: style (required). Returns: meta, notes, title, snippet
Generates the recommended OTP-verified payout flow: create recipient → validate OTP → create payout against the saved recipient. Use this for repeat beneficiaries; use generate_payout_sdk_snippet for one-off direct payouts.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.
Inputs: framework (required). Returns: meta, notes, title, snippet
Generates backend code to query the status of a payout using the Payram SDK.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Generates a backend route such as /api/referrals/create for logging referral events.
Inputs: framework (required). Returns: meta, notes, title, snippet
Generates a backend route or service snippet to create a referral event using the Payram SDK.
Inputs: framework (required). Returns: meta, notes, title, snippet
Generates code to fetch referral progress, rewards, or status.
Inputs: style (required). Returns: meta, notes, title, snippet
Generates a snippet to validate referral IDs, statuses, and eligibility.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Returns a step-by-step checklist of everything a merchant must configure to start using Payram.
Inputs: no named parameters. Returns: items, notes, title, description
For EXISTING apps: emits the recommended top-up wallet integration — ledger schema + cumulative-credit webhook handler + atomic invoice-settle function. Credits crypto payments to a user's balance first, then debits invoices from it, so over/under/late/duplicate payments become balance states, not payment exceptions. Pair with the payram-topup-wallet-integration skill. (New store with no users? Use the checkout/plugin path instead.)
Inputs: part, framework. Returns: notes, title, snippet
Generates a backend event router that dispatches Payram webhook events to domain handlers.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Generates backend code to handle Payram webhook HTTP requests.
Inputs: framework (required). Returns: meta, notes, title, snippet
Returns the canonical PayRam headless-agent guide: agent CLI commands, env vars, merchant vs operator mode, wallet flows, adding chains, troubleshooting. Long (~11k tokens). For a short personalised plan use payram_setup_plan.
Inputs: no named parameters. Returns: title, markdown, description
Returns the markdown for a Payram doc given its id, e.g. "features/payouts".
Inputs: id (required). Returns: id, url, path, markdown
Surface official documentation, website, and community links.
Inputs: no named parameters. Returns: notes, title, sections, description
Explain how to embed and manage the referral dashboard experience.
Inputs: no named parameters. Returns: notes, title, sections, description
Lists the available Payram doc ids. Optionally scope by a prefix such as "features".
Inputs: prefix. Returns: docs, count, prefix
Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).
Inputs: no named parameters. Returns: title, markdown, description
Read-only diagnosis of a PayRam server by its public URL — works from the hosted MCP without credentials: reachability, health, TLS certificate, installed vs latest version, worker states. Optionally validates an API key without creating anything. Returns ranked likely causes and exact fixes for the first failing stage. Run this first when anything PayRam-related fails.
Inputs: apiKey, baseUrl. Returns: baseUrl, healthy, version, findings, +7 more
Exact, copy-paste recipes for day-2 operations and troubleshooting that YOU run against the merchant's PayRam API with credentials that stay on your machine: which endpoint, which credential (public / dashboard JWT / project API key), a curl+jq command, how to read the answer, and what not to do. Start with "connect". Tasks: connect, health, version_check, workers, restart_worker, node_sync, site_url, payment_options, unswept_funds, payments_today, payment_lookup, stuck_payment, create_payment_link, payouts, webhooks, logs, daily_check. Omit task to list them.
Inputs: task. Returns: tasks, recipe
Step-by-step procedures for changes to a running PayRam, each step marked agent vs human with hard stops: set_site_url, change_domain, ssl_setup, ssl_renewal_fix, firewall_ports, upgrade, backup, restore, add_chain, smart_bridge, mainnet_cutover, operator_setup, rotate_api_key, reset_test_install, shopify_connector, woocommerce_plugin, secure_analytics_mcp, install_failed, custom_port_or_proxy, external_database, forgot_root_password. Omit task to list them.
Inputs: task. Returns: tasks, runbook
Start here to install PayRam on a VPS. Returns an ordered, personalised plan — prepare server → install → claim admin + set public URL → wallets (incl. Smart Bridge review) → API key + first payment link → hardening → store/app integration — with who runs each step (agent shell vs human/dashboard), exact commands, what success looks like, and hard stops that need the human (cold wallet, mainnet spend, root-only settings). Ask the user first whether you can run commands on their server (access "ssh") or only chat with them (access "human_runs_commands": they run each command and paste the output back). Pass stage to resume mid-way; payram_doctor tells you the stage of a running server.
Inputs: ssl, path, role, stage, +5 more. Returns: inputs, phases, summary, warnings, +2 more
Something is not working? Describe the problem in plain words and/or paste the error or log text. Returns the known PayRam problems it matches, what each usually means, how to confirm it and the fix, plus which tool to use next. Needs no credentials and no access to the server; what you paste is not stored. Call with nothing to list known problems. For a live check of a running server use payram_doctor.
Inputs: id, area, output, symptom. Returns: index, gather, matches, warning
Confirm hosting, credentials, and environment variables before generating demo apps.
Inputs: no named parameters. Returns: notes, title, sections, description
Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.
Inputs: language (required), framework (required), appName, includeWebhooks. Returns: files, appName, language, framework, +1 more
Returns an Express router that posts to Payram's /api/v1/payment endpoint.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Returns a FastAPI handler that calls Payram's create-payment HTTP API.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.
Inputs: no named parameters. Returns: meta, notes, title, snippet
Suggests a recommended backend folder/file structure for integrating Payram.
Inputs: no named parameters. Returns: root, notes, title, description
Deprecated: use payram_doctor, which does this and more. Read-only check that a PayRam server is reachable and healthy and, if an API key is supplied, that the key is accepted. Never creates payments.
Inputs: apiKey, baseUrl. Returns: ok, baseUrl, keyChecked, errorMessage, +1 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Non-custodial crypto payments: checkout sessions, invoices, webhooks and test payments. No KYC.
Crypto pay links and API for people and AI agents. BTC, Lightning, USDC, USDT, EURC, SOL, ETH.
Non-custodial crypto payments: charges, invoices and refunds in BTC, XRP, USDC and more.
Crypto payments for AI agents: self-serve account, invoices, receiving, payouts, exchange.
Add one secure layer between your agents and this server.
