EtMDB REST API v1

{
  "service_type": "platform",
  "base_url": "https://etmdb.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Ethiopian movie database",
    "Film metadata",
    "Rest API v1"
  ],
  "raw_analysis": "EtMDB (Ethiopian Movie Database) is a specialized database platform focused on Ethiopian cinema. Based on its description as 'The Ethiopian Movie Database' and the presence of a REST API v1 endpoint at https://etmdb.com, it likely serves film industry professionals, researchers, and movie enthusiasts seeking information on Ethiopian films, actors, directors, and related metadata. The platform appears to be a niche database with a public API, but no detailed documentation, authentication method, pricing model, rate limits, or endpoint specifications are provided in the given content. Its maturity and adoption level are unclear, but the existence of a versioned API suggests some level of development commitment. Integrations beyond the REST API are not mentioned. Overall, EtMDB fills a specific gap for Ethiopian film data, but lacks transparent public information about its API, access policies, or ecosystem."
}

1/3 tests passed

{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 3.0,
    "response_parseability": 2.0,
    "error_clarity": 3.0,
    "doc_quality": 3.0,
    "auth_simplicity": 3.0,
    "latency": 9.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No public pricing information available; unclear whether the REST API is free, freemium, or paid. Agents cannot recommend without knowing cost."
  },
  "issues": [
    "Main site returns 403 Forbidden — likely bot-blocking (Cloudflare or similar), preventing agents from reading docs, value prop, or API details.",
    "No llms.txt found (403), so agents have no machine-readable summary of the platform.",
    "No pricing information exposed anywhere checked; agents cannot advise users on cost.",
    "robots.txt uses Content-Signal directives and likely restricts automated access — hostile to agent consumption.",
    "Platform is a niche Ethiopian movie database with a generic REST v1 API; value prop is unclear and narrow for most users.",
    "No visible auth documentation or API key flow; onboarding path opaque.",
    "403 responses mask real error semantics — agents can't distinguish rate limiting from blocking from missing resources."
  ],
  "recommendations": [
    "Allow non-browser user agents (or provide an explicit agent-friendly allowlist) so docs and API references are readable.",
    "Publish an llms.txt with API base URL, auth flow, rate limits, and a few example queries.",
    "Expose clear pricing/usage terms — free tier, rate limits, and whether an API key is required.",
    "Return structured JSON errors (401/403/429 with reason codes) instead of generic 403 HTML for API endpoints.",
    "Provide OpenAPI/Swagger spec for the REST v1 API so agents can generate calls reliably on first try.",
    "Clarify the value proposition on a public, crawlable page — currently a niche database with an unclear audience."
  ]
}