SumUp — can an agent use it?
SumUp invests heavily in agent infrastructure — official MCP server, Agent Skills, SDKs in seven languages — while simultaneously blocking ClaudeBot in robots.txt. The API surface is real and transactional, but the contradictory crawler stance and absent rate-limit documentation create friction an agent must navigate.
FIND & RETRIEVE · 7.5
ACT & TRANSACT · 6.8
TRUST & DURABILITY · 6.0
FIND & RETRIEVE7.5/10Can an agent get correct information?
Machine-readable surface6/10
Developer portal is well-structured with API reference, changelog, and SDK docs. However, robots.txt explicitly blocks ClaudeBot (Disallow: /), no llms.txt on the main domain, sitemap returns 404 at the standard path (sitemap_index.xml exists but not at /sitemap.xml). The developer subdomain is reachable and clean, but the main commercial site is partially walled off from AI crawlers. source
Information retrieval quality8/10
Pricing is published and specific: 2.6% + 10¢ for in-person, 3.5% + 15¢ for online/manual entry, $0/mo free tier, $49/mo POS Plus, $99/mo full POS. Hardware costs visible. Connect loyalty plans priced at $269/mo and $349/mo. An agent can answer a merchant's cost question without guessing. source
Documentation for machines8.5/10
Comprehensive developer portal at developer.sumup.com with full API reference, quickstart guides, testing/sandbox documentation, OAuth 2.0 and API key auth guides, SDKs in seven languages (JS, Python, .NET, Java, PHP, Go, Rust), CLI tools, and a dedicated Build with AI section covering MCP, Agent Skills, and Plugins. source
ACT & TRANSACT6.8/10Can an agent do the job?
Action coverage7/10
API covers core payment actions: create checkouts, process payments via Cloud API for terminals, refunds, account management. Online payments have hosted and embedded checkout options plus custom integrations. In-person payments supported via Cloud API and mobile SDKs. Some advanced POS features (floor plans, loyalty, Connect SMS) may not have full API parity with the UI. source
Agent protocol support8.5/10
Official MCP server at mcp.sumup.com/mcp (GitHub: sumup/sumup-mcp) that covers core transactional actions — creating checkouts and processing payments via Cloud API, not just documentation queries. Additionally offers Agent Skills (6 published skills including checkout implementation, debugging, testing), an Agent Toolkit, and Plugins. The protocol surface reaches the actions the service is used for. source
Access & auth friction8/10
Self-serve API keys generated from the dashboard (Settings > For Developers > Toolkit > API Keys) in minutes. OAuth 2.0 available for multi-merchant integrations. MCP server supports both OAuth and API key auth. Affiliate keys for card-present transactions. No manual approval or enterprise gate for API access. source
Agent payment capability4/10
SumUp is a payment processor, so agents can create checkouts and process payments on a merchant's behalf via the API and MCP server. However, there is no evidence of support for any published agent payment protocol (ACP, AP2, MPP, x402). The transaction capability exists but through proprietary checkout flows, not interoperable agent-payment standards. A merchant's agent can charge a customer, but there is no delegated spend-capped authority framework. source
Cost & rate fairness6.5/10
Transparent per-transaction pricing with no monthly minimum on the free tier. No documented rate limits anywhere in the developer portal — neither specific numbers nor even an acknowledgment that limits exist. No evidence of agent-vs-human price discrimination. The lack of published rate limits is a friction point for agents that need to plan request volumes, though the absence also means no punitive throttling is documented. source
TRUST & DURABILITY6.0/10Will it still work next quarter?
Permission & ToS stance5/10
Contradictory signals: robots.txt explicitly blocks ClaudeBot (Disallow: /) on the main domain, while the developer portal actively courts AI agents with a dedicated Build with AI section, official MCP server, and Agent Skills. The terms of service do not explicitly mention automation, bots, or AI agents — neither prohibiting nor welcoming them. The ClaudeBot block likely targets training data scraping rather than API-mediated agent use, but the ambiguity creates legal uncertainty for an agent operator. source
Reliability & continuity7/10
Public status page at status.sumup.com covering regional availability. Developer portal includes a changelog for API updates. Operates across 36+ countries with years of continuous service. However, terms state SumUp may 'at any time terminate, suspend, update, or modify the Services with immediate effect without prior notification' (§1.6), and fees are 'subject to change at SumUp's discretion' (§1.4) — standard payment-processor language but adversarial for agent reliance. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- sumup.com — home — country selector, product overview (accessed 2026-09-18)
- sumup.com/en-us/credit-card-processing-fees — pricing — transaction fees, plan tiers, Connect loyalty (accessed 2026-09-18)
- sumup.com/en-us/terms — terms — service modification rights, fee change rights (accessed 2026-09-18)
- sumup.com/robots.txt — robots — blocks ClaudeBot, sitemap_index.xml reference (accessed 2026-09-18)
- developer.sumup.com — developer portal — API reference, SDKs, Build with AI section (accessed 2026-09-18)
- developer.sumup.com/tools/llms/mcp-server — MCP server — official, managed at mcp.sumup.com, OAuth + API key auth (accessed 2026-09-18)
- developer.sumup.com/tools/llms/agent-skills — Agent Skills — 6 published skills for AI coding assistants (accessed 2026-09-18)
- developer.sumup.com/tools/authorization/api-keys — API keys — self-serve from dashboard, Bearer auth (accessed 2026-09-18)
- status.sumup.com — status page — regional coverage (accessed 2026-09-18)