Unmei-tarot API

{
  "service_type": "platform",
  "base_url": "https://unmei-tarot.com/en",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "tarot reading",
    "fortune telling",
    "web application"
  ],
  "raw_analysis": "Unmei-tarot appears to be a tarot reading / fortune-telling web platform (name translates roughly to 'Destiny Tarot'). The /en path indicates an English localization, suggesting it targets an international audience alongside a likely Japanese primary market. It is registered here as 'Unmei-tarot API' but there is no evidence of a public programmatic API: no endpoints, no documentation, no auth scheme, and it was auto-registered via a benchmark URL submission, meaning the description is unverified. The service is almost certainly a consumer-facing website offering tarot/fortune results, likely via a web UI, possibly with paid readings or subscriptions. Maturity is low/unknown from available information; no developer integrations, SDKs, or partners are documented. No public REST API can be confirmed, so for integration purposes this should be treated as a platform with no known API surface; any automation would require scraping the website (likely against terms of service) or manual use. Pricing, rate limits, and authentication are unknown."
}

1/3 tests passed

{
  "overall": 44,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 6.0,
    "response_parseability": 3.0,
    "error_clarity": 3.0,
    "doc_quality": 3.0,
    "auth_simplicity": 5.0,
    "latency": 6.0,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information available from checks; consumer-facing tarot reading app."
  },
  "issues": [
    "No public API, structured data, or programmatic interface detected — purely a web application",
    "robots.txt returns 404 — no crawl guidance for agents",
    "No llms.txt — no agent-oriented discovery file",
    "No documented pricing, auth flow, or developer docs from observable surface",
    "Response previews are Next.js HTML shells; content extraction for agents is non-trivial",
    "Unknown auth flow — no SSO or magic link evidence"
  ],
  "recommendations": [
    "Publish an llms.txt and robots.txt to guide agents",
    "Expose a documented API or structured export if any programmatic use is intended",
    "Clarify pricing and terms on a discoverable page",
    "Provide machine-readable metadata (OpenAPI / JSON-LD) for the core reading flow",
    "Reduce homepage latency below 1s where possible"
  ]
}