Elaichi API

{
  "service_type": "platform",
  "base_url": "https://elaichi.ai",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "ai",
    "unknown"
  ],
  "raw_analysis": "The service 'Elaichi API' at https://elaichi.ai was auto-registered via benchmark URL submission, and the only provided information is the name, URL, category 'ai', and the note that it was auto-registered. No public documentation, API details, authentication methods, endpoints, pricing, or rate limits were available in the submission. Without further investigation, the platform's capabilities remain unknown beyond its categorization as an AI service. It is unclear whether Elaichi provides a public REST API or is a collaboration tool, dashboard, or development environment. The maturity, target audience, and existing integrations cannot be assessed. To proceed with integration or analysis, direct research into the website or contacting the provider would be necessary."
}

3/3 tests passed

{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.0,
    "response_parseability": 6.5,
    "error_clarity": 6.0,
    "doc_quality": 7.5,
    "auth_simplicity": 6.0,
    "latency": 10.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information detected on the landing page or capability scan; B2B agent platform likely requires sales contact."
  },
  "issues": [
    "Pricing model is undefined — agents cannot tell users what it costs or how to self-serve.",
    "Capabilities tagged as ['ai','unknown'] — product surface (APIs, SDKs, exports) not confirmed, hurting parseability.",
    "No public signup path detected; onboarding appears sales/enterprise-led ('for companies').",
    "Auth flow not surfaced (no magic link / SSO / notlogin signals), limiting autonomous agent onboarding."
  ],
  "recommendations": [
    "Publish a pricing page (even 'contact us' tiers) so agents can set expectations.",
    "Expose a clear developer surface: REST API, SDK, or MCP server for agent integration.",
    "Add explicit auth documentation (SSO, magic link, or notlogin support) to enable agent-led signup.",
    "Strengthen llms.txt with capability, endpoint, and integration details for machine consumption.",
    "Document error codes and permission scopes, given the 'governed permissions' positioning."
  ]
}