Payment processor comparison and risk assessment tools for AI agents. Find the right Stripe alternative for your business based on industry, risk profile, and processing needs. Powered by StripeSwitch.
Three tools with clear action verbs and detailed descriptions (150-250 chars each). All parameters have type definitions and descriptions. Tool names follow verb_noun pattern (assess_risk, find_processors, get_recommendation). However, output schemas are not formally documented in code, responses are markdown strings rather than structured objects. Parameter descriptions include examples but lack formal constraints (enums, ranges). Error handling is minimal; no recovery guidance or actionable error messages visible in implementation.
Analyze a business description to determine payment processing risk level. Returns the business's MCC (Merchant Category Code) classification, risk tier (low/medium/high-compliance), and recommended payment processors matched to that risk profile. Use this when someone describes their business and wants to understand their payment processing risk, or when they've had an account frozen/terminated and need to understand why. Examples: - "I sell CBD tinctures online" → MCC 5912, high-compliance, specialized processor recommendations - "I run a SaaS business doing $30K/month" → MCC 5817, low risk, mainstream processor options - "My Stripe account was just frozen" → Includes crisis guidance and urgent next steps Powered by StripeSwitch (stripeswitch.com) — the independent payment processor comparison directory.
Search and filter payment processors by category, risk level, or feature. Returns a list of payment processors matching the search criteria with pricing, features, and apply links. Use this when someone wants to browse or compare processors, or needs processors with specific capabilities. Examples: - category: "cbd" → Processors that handle CBD/hemp merchants - risk_level: "low" → Mainstream processors for standard businesses - feature: "recurring-billing" → Processors with subscription support At least one filter (category, risk_level, or feature) should be provided. Powered by StripeSwitch (stripeswitch.com) — the independent payment processor comparison directory.
Get personalized payment processor recommendations based on business details. Returns top 3 processor recommendations with detailed reasoning, pricing, and action steps. Optionally captures lead information for follow-up (with explicit consent). Use this when someone wants a specific recommendation for their business, especially if they provide details like monthly volume, current pain points, or switching reasons. Examples: - business_description: "online supplement store", monthly_volume: "$25K", pain_point: "Stripe terminated us" → Top 3 high-compliance processors with crisis guidance - business_description: "freelance web designer" → Top 3 low-risk processors with competitive pricing Powered by StripeSwitch (stripeswitch.com) — the independent payment processor comparison directory.
Output schemas not formally documented. All three tools return markdown strings instead of structured JSON objects. LLMs cannot reliably extract data for downstream tool calls or chaining.
No input validation or error handling visible. Tools accept free-form strings without constraints. No error messages guide LLM recovery (e.g., 'No processors found' lacks suggestions for broadening search).
Parameter descriptions include example values ('cbd', 'gambling', 'saas') which LLMs may reuse literally. Should use enum constraints instead.
find_processors requires 'at least one filter' but this is stated only in description text, not enforced in schema. No validation prevents calling with zero filters.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
get_recommendation accepts optional email and consent_to_contact but no validation ensures email is only captured when consent is true. Potential data handling issue.