KumpeApps API

{
  "service_type": "platform",
  "base_url": "https://kumpeapps.com",
  "auth_method": "username_password",
  "auth_config": {
    "notes": "All API calls require authentication. Users must authenticate with their KumpeApps username/password. Access is gated — users must be granted access (likely via contacting the maintainer, given the truncated 'to gain access please use the co...' text)."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "No public pricing information available. Appears to be a personal or small-team project (KumpeApps / KKid)."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "KumpeApps account authentication",
    "KKid-related functionality (exact scope unclear)",
    "Access-controlled API (invite/approval gated)",
    "Possible AI and security related features (per category tags)"
  ],
  "raw_analysis": "KumpeApps appears to be a small, personal or hobbyist project (likely by an individual developer, given the 'KumpeApps' branding and the 'KKid' sub-product name). The description explicitly states that, due to security concerns, ALL calls to the API require authentication using a KumpeApps username/password. There is no open/anonymous access and no documented public developer portal. The provided text indicates that access is explicitly gated ('If you have access then you may...' and 'To gain access please use the co...' — presumably 'contact the developer/admin'). This strongly suggests a private or invite-only platform, not a commercial or widely available service.\n\nNo versioned API path, docs URL, base path, or endpoint list is provided in the source material, so endpoints cannot be enumerated. No OpenAPI/Swagger spec, developer portal, or SDK references were given. Category tags (auth, ai, security) suggest the platform intersects authentication and possibly AI-driven features, but without documentation these capabilities are speculative.\n\nMaturity: low/unclear. No evidence of public documentation, status page, pricing, or community. Integrations: none documented. Auth model: username/password with manual approval to obtain access. Rate limits: unknown. Pricing: unknown (no evidence of paid offering; likely free/personal).\n\nRecommended next steps for integration: contact the platform owner to request API access and obtain documentation; otherwise this service is not viable for general automated integration."
}

1/3 tests passed

{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 2.0,
    "response_parseability": 3.0,
    "error_clarity": 3.0,
    "doc_quality": 2.0,
    "auth_simplicity": 2.0,
    "latency": 8.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "public_pricing_available": false,
    "notes": "No public pricing information. Appears to be a personal/small-team project (KumpeApps / KKid) with no stated commercial tier."
  },
  "issues": [
    "Landing page immediately requires login ('Please login') with no public value proposition or feature description visible to agents or users.",
    "No public pricing information — agents cannot advise users on cost, free tier, or commercial terms.",
    "robots.txt endpoint failed DNS resolution — subdomain/host appears misconfigured or non-resolvable.",
    "llms_txt endpoint failed DNS resolution — no agent-oriented discovery file exists.",
    "Access is invite/approval-gated, blocking autonomous agent onboarding.",
    "Exact scope of 'KKid-related functionality' is undefined; no public API docs referenced.",
    "Cannot verify signup flow, SSO, or auth options from available data — likely account-only with no NotLogin/magic-link support visible."
  ],
  "recommendations": [
    "Publish a public landing page describing the value proposition, features, and target audience before gating behind login.",
    "Add a public pricing page or explicitly state 'free / personal project' so agents can set user expectations.",
    "Fix DNS for robots.txt and llms.txt (or host them under the primary domain) to enable agent discovery.",
    "Provide public API documentation with authentication details, rate limits, and example requests/responses to improve parseability.",
    "Support magic-link or 'Sign in with Notlogin' style onboarding so agents can complete setup without human intervention.",
    "Document limitations, invite/approval process, and turnaround times clearly to raise error clarity.",
    "Add a status page or uptime indicator to build consistency confidence.",
    "If intended for broader users, offer a self-serve trial tier rather than approval-gated access."
  ]
}