Adyen Checkout Utility Service

```json
{
  "service_type": "platform",
  "base_url": "https://help.adyen.com",
  "auth_method": "api_key",
  "auth_config": {
    "header_name": "X-API-Key",
    "api_key_source": "Adyen Customer Area",
    "description": "API key required for Checkout Utility API requests, managed in Adyen Customer Area dashboard"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "Pricing depends on individual merchant agreement with Adyen; Checkout Utility API usage may be billed as part of standard transaction fees",
      "actual_api_pricing": "Please refer to merchant contract or Adyen Customer Area"
    }
  },
  "rate_limits": {
    "unknown": true,
    "note": "Rate limits not publicly documented; Adyen recommends contacting support for specific volume needs"
  },
  "capabilities": [
    "Origin keys for Web Drop-in and Components",
    "Apple Pay domain verification",
    "Address lookup and validation",
    "Shopper information utilities for Checkout",
    "Webhook signature validation tools",
    "Payment method and merchant account utilities",
    "Support for card, bank transfer, wallet, and other payment methods",
    "Integration with Adyen Checkout API ecosystem",
    "Reconciliation and reporting utilities",
    "Test card number generation for integration testing"
  ],
  "raw_analysis": "Service Identified: Adyen Checkout Utility Service (via support.adyen.com / help.adyen.com)\n\nPlatform Type: Payment technology support and utility service, part of Adyen's broader global payment platform. The provided URL (support.adyen.com) redirects to help.adyen.com, which is a multilingual customer help center built on Nuxt.js/Vue.js with i18n support (English, German, Spanish, French, Italian, Japanese, Portuguese, Chinese).\n\nCore Function: The Checkout Utility API provides utility functions specifically for merchants integrating with Adyen's Checkout APIs. This includes generating origin keys for Web components, Apple Pay domain verification, and address lookup functionality. Despite the similar name, this is distinct from the main Checkout API which processes payments.\n\nAuthentication: API key-based authentication required for each request, submitted via X-API-Key header. API keys are managed through the Adyen Customer Area dashboard. The support site itself appears publicly accessible without authentication, but the actual Utility API requires merchant credentials.\n\nTarget Audience: Merchants and developers currently using or planning to integrate Adyen Checkout APIs, primarily for e-commerce payment processing across web and mobile platforms. Both test environments and live production environments are available.\n\nMaturity: Very mature, production-grade system. Adyen is a global payment company founded in 2006, publicly listed, and processes payments for major companies. The Checkout API is their flagship product, and this Utility Service is a stable, well-documented component.\n\nIntegrations: Designed to work primarily with Adyen's own payment stack:\n- Adyen Drop-in and Components (JavaScript library)\n- Adyen Checkout API v66+ (transaction processing)\n- Adyen Mobile SDKs (iOS/Android)\n- Various server-side SDKs (Java, Python, Node.js, PHP, .NET)\n- Manual/API webhooks for payment notifications\n- No direct third-party service integrations found in the utility API since it's part of the internal Adyen ecosystem\n\nPage Characteristics: The help center HTML shows a Nuxt.js SSR application with OneTrust cookie consent and Google Tag Manager integration. The page structure reflects a modern SaaS docs platform with internationalization support across 10+ locales. The description clearly indicates this is the documentation/support portal, with actual API calls likely documented in an OpenAPI spec elsewhere on the Adyen developer portal.\n\nMonetization: Standard Adyen merchant model: no direct per-call pricing published for utility endpoints; costs typically embedded in overall payment processing fees (transaction percentage + fixed fee). There's likely a free test environment for development purposes."
}
```

2/3 tests passed

```json
{
  "overall": 64,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 5.0,
    "response_parseability": 7.5,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 4.0,
    "latency": 8.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "type": "enterprise_contract",
    "transparency": "low",
    "description": "Price depends on individual merchant agreement; not publicly available"
  },
  "issues": [
    "No llms.txt endpoint for AI-discoverable documentation",
    "Pricing model opaque — requires enterprise contract",
    "Auth likely complex (Adyen requires merchant account setup, not self-serve)",
    "Platform is payment-utility focused, narrow for general use",
    "Response parseability good but requires Adyen's proprietary formats"
  ],
  "recommendations": [
    "Add llms.txt to help.adyen.com for agent-friendly API docs",
    "Publish transparent pricing tiers or at least utility API per-request costs",
    "Provide sandbox quick-start with temporary API keys for agents",
    "Document exact error codes and webhook signature verification pseudo-code more clearly",
    "Reduce dependency on manual merchant onboarding flows where possible"
  ]
}
```