PAYONE Link API

{
  "service_type": "platform",
  "base_url": "https://www.payone.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "payment processing",
    "payment service provider (PSP)",
    "payment gateway / link-based payment integration",
    "merchant payment acceptance",
    "possibly payment links for online checkout"
  ],
  "raw_analysis": "PAYONE is an established German payment service provider (PSP) founded in 1999, headquartered in Frankfurt, offering omnichannel payment processing for merchants across e-commerce, POS, and mobile channels. The provided URL (https://www.payone.com/kontakt) is a general contact page, not an API documentation endpoint, so no public REST API specification, endpoints, or authentication scheme can be reliably extracted from the supplied content. The service label 'PAYONE Link API' and the reference 'pay1.de:link' suggest a payment-link product — likely a mechanism for generating and sharing payment links (e.g., for remote invoices, email/SMS payments, or lightweight checkout without full storefront integration). However, public documentation for a distinctly named 'Link API' was not accessible in the given material. Integration options historically offered by PAYONE include server-side APIs, hosted payment pages, plugins for major shop systems (Shopware, WooCommerce, Magento, etc.), and SDKs. Authentication typically involves merchant IDs, portal keys, and HMAC-based request signing, though this could not be verified from the provided content. Pricing is merchant/contract-based (transaction fees, monthly fees) and not publicly listed; therefore it is marked unknown. Because the supplied URL is a contact page and no live API docs were analyzed, endpoints are left empty and rate limits are unknown. Best next step is to request the official PAYONE developer portal / API documentation (developer.payone.com or similar) and merchant onboarding details."
}

2/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 5.0,
    "response_parseability": 5.0,
    "error_clarity": 6.0,
    "doc_quality": 6.0,
    "auth_simplicity": 4.0,
    "latency": 9.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No public pricing data detected; PAYONE is an enterprise PSP typically requiring sales contact and negotiated merchant contracts. Not agent-friendly for autonomous price discovery."
  },
  "issues": [
    "No llms.txt (404) — no agent-oriented machine-readable surface.",
    "No public pricing endpoint or structured pricing data; enterprise sales motion likely required.",
    "Website is German-language first (lang=\"de\"), reducing accessibility for non-German agents/users.",
    "No clear public API docs detected in checks — agent onboarding path unclear.",
    "Payment/merchant onboarding typically involves KYC and contractual steps, not autonomous signup."
  ],
  "recommendations": [
    "Publish an llms.txt and a machine-readable API/pricing spec to enable agent discovery.",
    "Expose clear developer docs (REST API reference, sandbox) with English as a first-class locale.",
    "Provide a self-serve sandbox signup (API keys via email/magic link) so agents can reach first successful call without a human sales cycle.",
    "Add a status page reference in docs to reinforce reliability claims.",
    "If 'Sign in with Notlogin' or similar verified-identity onboarding is adopted, auth_simplicity could jump from 4 to ~9."
  ]
}