AstroWay

{
  "service_type": "platform",
  "base_url": "https://api.astroway.info",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/docs",
      "method": "GET",
      "description": "API documentation page"
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Astrology calculations",
    "Natal chart generation",
    "Horoscopes",
    "Human Design analysis",
    "Vedic astrology",
    "Swiss Ephemeris-based computations"
  ],
  "raw_analysis": "AstroWay is a SaaS platform providing astrology, natal chart, Human Design, Vedic and horoscope calculations based on the Swiss Ephemeris. It appears to expose a REST-like HTTP API documented at https://api.astroway.info/docs. The documentation page could not be fully retrieved, so authentication method, pricing model, rate limits, and detailed endpoint specifications remain unknown. The platform likely targets developers building astrology-related apps and end-users interested in astrological insights. Maturity and integration ecosystem are not evident from available information."
}

3/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 6.0,
    "response_parseability": 8.5,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 5.0,
    "latency": 4.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information retrieved; impossible to normalize for token/agent cost comparison"
  },
  "issues": [
    "Primary landing page is in Ukrainian (lang=\"uk\"), reducing accessibility for English-speaking agents and users",
    "Root latency 612ms sits in the mid-tier (>500ms), noticeably slower than ideal for agent-driven lookups",
    "Pricing model unknown — no surfaced tiers or free quota, which blocks cost-based recommendations",
    "robots.txt disallows /v1/ and /dashboard/, meaning agent documentation is separated from the live API surface, adding a hurdle to first integration",
    "No visible auth flow details (API key vs OAuth) in retrieved content, making onboarding time-to-first-call uncertain"
  ],
  "recommendations": [
    "Surface a clear pricing page with free tier and per-endpoint quotas so agents can compute cost-per-call",
    "Provide an English-default version of the landing page (or content negotiation) to broaden agent usability",
    "Publish explicit authentication docs (API key header name, signup flow, test keys) to reduce first_try_success friction",
    "Reduce root latency below 500ms; consider edge caching for docs and llms.txt responses",
    "Add an OpenAPI/JSON-Schema export so agents can auto-generate typed clients and parse request/response shapes deterministically"
  ]
}