koomalooma Partner API

{
  "service_type": "platform",
  "base_url": "https://koomalooma.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "model": "BPaaS (Business Process as a Service)",
      "description": "Likely enterprise/subscription-based since it's a loyalty platform service for merchants and partners"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "loyalty_points_issuance",
    "merchant_rewards_program",
    "mobile_and_web_loyalty",
    "customer_engagement",
    "partner_integration",
    "points_for_actions"
  ],
  "raw_analysis": "koomalooma is a Loyalty BPaaS (Business Process as a Service) platform targeting mobile and web companies. It enables merchants to issue loyalty points to their customers for performing specific actions. The service is positioned as a turnkey loyalty infrastructure — merchants do not build the loyalty engine themselves; they consume it as a service.\n\nService Type: This is a platform (B2B SaaS/BPaaS), not a standalone public API product. The 'Partner API' referenced suggests there is a programmatic interface exposed to business partners (likely merchants or channel partners), but no public REST documentation is provided in the given inputs.\n\nAuthentication: Unknown. As a partner-style B2B platform, it likely uses OAuth 2.0, API keys, or a signed request scheme issued per-partner. No details available.\n\nEndpoints: No explicit REST endpoints are documented in the provided content. The 'Additional Content' block is entirely about Cryptorefills, a different service, and does not describe koomalooma — this appears to be contamination from an unrelated source and should be disregarded for koomalooma analysis.\n\nPricing: Unknown, but BPaaS models typically price via subscription tiers, per-transaction fees, or revenue-share with partners. Likely a freemium/enterprise hybrid but not confirmed.\n\nMaturity: The product presents itself as 'the first Loyalty BPaaS' — a marketing claim implying relative novelty in the loyalty-as-a-service niche. Public API/protocol maturity cannot be assessed from the given inputs.\n\nIntegrations: Not disclosed in the provided content. As a loyalty platform it would typically integrate with e-commerce platforms (Shopify, WooCommerce, Magento), mobile SDKs (iOS/Android), and CRM/marketing tools — but this is inference, not confirmed.\n\nRecommendation: To properly assess koomalooma, we would need access to their developer documentation portal (often at docs.koomalooma.com or developer.koomalooma.com) and their partner onboarding page. The provided description is truncated ('custome...') and offers insufficient detail for endpoint-level or auth-level documentation.The Cryptorefills content should be excluded from this analysis as it describes an unrelated service."
}

3/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 4.0,
    "latency": 6.0,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "model": "BPaaS (Business Process as a Service)",
    "unknown": true,
    "notes": "Pricing not publicly exposed; likely enterprise/subscription-based. No self-serve tier identified."
  },
  "issues": [
    "Pricing model is undisclosed — agents cannot compare or estimate cost for users",
    "No clear self-serve onboarding signal; BPaaS implies enterprise sales cycle, breaking first-try-success",
    "Auth flow unclear — no documented OAuth/API key/magic-link path visible in checked endpoints",
    "llms.txt content appears mismatched (references Cryptorefills API, not Koomalooma) suggesting incomplete or templated agent-facing docs",
    "Robots/sitemap exist (good signal) but no structured API surface confirmed",
    "Response preview is a large Next.js HTML blob — not agent-parseable without a dedicated API",
    "Latency at ~1.3s on main site is acceptable but not fast",
    "No security headers detected on primary endpoints"
  ],
  "recommendations": [
    "Publish a public pricing page or at least tier ranges so agents can advise users",
    "Fix the llms.txt to accurately describe Koomalooma's own API/capabilities (currently appears to leak Cryptorefills content)",
    "Expose a documented public API with OAuth or API-key auth for agent onboarding",
    "Provide a self-serve developer sandbox or magic-link signup to reduce onboarding friction",
    "Add structured JSON endpoints (OpenAPI spec) alongside HTML site for parseability",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to signal reliability",
    "Publish a status page and uptime SLA to improve consistency perception",
    "Clarify BPaaS scope in plain language in docs — what a merchant/partner actually integrates"
  ]
}