Miataru

{
  "service_type": "platform",
  "base_url": "http://miataru.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "location sharing",
    "POST JSON requests to service methods",
    "JSON formatted responses"
  ],
  "raw_analysis": "Miataru is a location-sharing service exposed via a simple HTTP API. Based on the limited description, clients POST a JSON-formatted request to a service method (appears to be named 'locations' or similar) and receive a JSON-formatted response. The service appears to be free/open, with no indicated authentication mechanism, though this is uncertain given the sparse documentation provided. The URL given is HTTP (not HTTPS), which is a security concern for a location-sharing platform. No pricing, rate limits, or formal endpoint documentation is included in the provided content. The description categorizes it under 'ai, api' but the functionality described (location posting and retrieval) does not obviously relate to AI. Maturity and audience are unclear from the available information. Publicly documented API details are insufficient to enumerate specific endpoints or capabilities beyond basic location exchange."
}

1/3 tests passed

```json
{
  "overall": 52,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 7.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 5.0,
    "latency": 9.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "details": "No pricing information detected — cannot assess cost efficiency for agent recommendations"
  },
  "issues": [
    "No llms.txt or robots.txt — agents have no machine-readable guidance for crawling or capability discovery",
    "Pricing model is completely unknown, blocking cost-based recommendations",
    "No security headers detected on responses — raises trust/robustness concerns",
    "Auth flow not described in checks — onboarding friction unknown for agents",
    "Documentation surface appears thin; no getting-started or API reference surfaced in checks"
  ],
  "recommendations": [
    "Publish an llms.txt describing capabilities (location sharing + POST JSON service methods) so agents can self-onboard",
    "Add a clear pricing page with a machine-readable summary (free tier + paid tiers)",
    "Document the authentication model explicitly (token, API key, or OAuth) so agents can recommend confidently",
    "Provide an OpenAPI/JSON schema for the POST service methods to improve parseability and first-try success",
    "Expose error response schemas so agents can handle failures deterministically",
    "Ship a public status endpoint and security headers to raise consistency and trust scores"
  ]
}
```