Flutterwave

{
  "service_type": "platform",
  "base_url": "https://api.flutterwave.com",
  "auth_method": "api_key",
  "auth_config": {
    "header_name": "Authorization",
    "header_value_format": "Bearer {secret_key}",
    "key_types": ["secret_key", "public_key", "encryption_key"],
    "key_environment": "dashboard-managed (test/live mode toggle)"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "Transaction-based pricing rather than subscription; rates vary by country, payment method, and transaction type (local cards, international cards, mobile money, bank transfers). Typically disclosed as a percentage per successful transaction plus possible local caps. Some products (e.g. Flutterwave Store, payout tools) may have separate fee structures. Exact rates must be confirmed from Flutterwave's pricing page or account manager."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Payment collection (cards, bank accounts, USSD, mobile money, QR, bank transfer)",
    "E-commerce checkout (Flutterwave Checkout / Standard)",
    "Recurring billing and subscriptions",
    "Payouts and bulk transfers (bank/mobile money)",
    "Multi-currency support (African and international currencies)",
    "Payment links and invoicing",
    "Fraud detection and risk management (Barter-like tools)",
    "Virtual cards and virtual accounts",
    "Merchant dashboards and reporting",
    "Webhooks for transaction events",
    "Plugin integrations (WooCommerce, Shopify, etc.)",
    "Developer-friendly REST API with SDKs (PHP, Python, Node, etc.)"
  ],
  "raw_analysis": "Flutterwave is a leading African fintech platform that provides payment infrastructure for businesses operating in Africa and globally. Founded in 2016, it has grown into one of the continent's most prominent payment technology companies, often described as a 'Stripe for Africa'. \n\nCore offering: A RESTful payments API that enables merchants to accept payments via cards (local and international), bank transfers, USSD, mobile money, and other local methods across multiple African countries. It also supports payouts (transfers to bank accounts and mobile wallets), subscriptions, and value-added services like virtual cards and invoicing.\n\nTarget users: African and global merchants selling into African markets, fintech startups, e-commerce platforms, SaaS businesses, and traditional enterprises seeking to digitize payments. Also serves global businesses needing to collect or disburse funds in Africa.\n\nMaturity: Flutterwave is a mature, well-funded company with a presence in many African countries and global processing capabilities. It is a licensed payment provider in several jurisdictions, though regulatory scrutiny has occurred in some markets (e.g. Kenya). The API is stable, documented, and widely used, with official SDKs and plugins. The company has faced past security incidents and compliance challenges, but remains a major market player.\n\nIntegrations: Extensive — WooCommerce, Shopify, Magento, custom SDKs, and direct API access. Webhooks support real-time notifications. The platform also offers tools like Flutterwave Store (no-code commerce) and Barter (virtual cards for online spending).\n\nAuth model: API keys (public/secret) issued via dashboard; secret key used as Bearer token in Authorization header. Encryption key available for additional security.\n\nPricing: Transaction-based; exact rates depend on region, payment method, and volume. Generally competitive with other African payment gateways. Must be confirmed via official pricing.\n\nRate limits: Not publicly documented in detail; typical of payment APIs to enforce per-endpoint limits and burst protection. Best to check developer docs or contact support for specifics.\n\nOverall: A comprehensive payments platform for Africa with strong API capabilities, broad method coverage, and significant market adoption."
}

1/3 tests passed

```json
{
  "overall": 78,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.0,
    "response_parseability": 9.0,
    "error_clarity": 7.0,
    "doc_quality": 8.0,
    "auth_simplicity": 7.0,
    "latency": 9.5,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "transaction_based",
    "subscription": false,
    "free_tier": false,
    "pricing_disclosed": false,
    "notes": "Per-transaction percentage fees varying by country, payment method, and transaction type. Exact rates require confirmation from pricing page or account manager; no standardized published schedule surfaced. No llms.txt or structured pricing endpoint."
  },
  "issues": [
    "No llms.txt file — agents cannot cheaply discover platform capabilities or constraints.",
    "robots.txt returns 404 — no crawl guidance for agents or crawlers.",
    "Pricing details are opaque at the API surface; rates vary by region/method and require human negotiation or manual lookup.",
    "Root response returns obfuscated/legacy keys (rave, nocd, dlyvr, _2q_8r) rather than a clean service descriptor — good for humans, ambiguous for agents.",
    "Auth flow for merchant onboarding (API keys + account verification) is not trivially automatable end-to-end."
  ],
  "recommendations": [
    "Publish an llms.txt describing the API surface, auth model, supported currencies, and pricing structure so agents can onboard users without scraping docs.",
    "Expose a machine-readable pricing endpoint (per country/method) to reduce the human lookup step.",
    "Return a structured service descriptor at a conventional endpoint (e.g., /.well-known/service or /api/v1/meta) instead of obfuscated root keys.",
    "Add explicit error/limitation docs covering regional restrictions, KYC requirements, and settlement timelines.",
    "Consider 'Sign in with Notlogin'-style verified agent onboarding to remove the human verification step during API key provisioning."
  ]
}
```