Maps

{
  "service_type": "platform",
  "base_url": "https://tomtom.com",
  "auth_method": "api_key",
  "auth_config": {
    "parameter_name": "key",
    "location": "query"
  },
  "endpoints": [
    {
      "name": "Maps Raster API",
      "path": "/map/1/tile/{style}/{zoom}/{x}/{y}",
      "method": "GET",
      "description": "Renders map data as gridded tile images (PNG/JPG)."
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "notes": "TomTom offers a free tier with limited requests per day and paid plans for higher volumes; exact tiers require reviewing the pricing page."
    }
  },
  "rate_limits": {
    "notes": "Varies by plan; typically requests per second/day limits"
  },
  "capabilities": [
    "map tile rendering",
    "raster map tiles",
    "custom map styles",
    "multiple zoom levels",
    "global coverage"
  ],
  "raw_analysis": "Service: Maps (TomTom)\nURL: https://tomtom.com\n\nThe Maps API web services suite provides a Raster API that renders map data into square tile images (PNG or JPG). These tiles are served via a RESTful HTTP GET interface, commonly accessed with a URL pattern containing style, zoom level, and tile coordinates. Authentication is typically done via an API key passed as a query parameter ('key').\n\nThe TomTom Maps platform is a mature, commercial location technology offering used by developers, enterprises, and automotive applications. It includes routing, geocoding, traffic, and map display APIs. The Maps Raster API is part of a broader suite that also includes Vector Tiles and other mapping services.\n\nIntegration options include SDKs for web (JavaScript), Android, iOS, and various backend languages. The platform supports custom styles and high-resolution tiles. Pricing follows a freemium model with a free tier (limited daily requests) and paid tiers for production usage. Rate limits are plan-dependent and documented in the developer portal.\n\nNo public self-service REST discovery beyond the developer documentation; full API reference and key management are available at developer.tomtom.com."
}

2/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 6.5,
    "response_parseability": 8.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 5.5,
    "latency": 8.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "freemium",
    "free_tier": "limited requests/day",
    "paid_tiers": "volume-based",
    "transparency": "low — exact tiers require reviewing pricing page"
  },
  "issues": [
    "No llms.txt endpoint (404) — agents lack a canonical machine-readable capability summary",
    "Pricing details are vague in the provided analysis; exact free/paid limits require manual pricing page review",
    "Latency on llms_txt check was 1154ms (though 404), suggesting heavier backend routing",
    "Auth flow not described — unclear if API keys are self-serve or gated",
    "robots.txt is broadly permissive for AI, which is a positive, but no explicit agent API roadmap"
  ],
  "recommendations": [
    "Publish an llms.txt with capabilities, tile URL templates, zoom levels, attribution requirements, and auth steps",
    "Expose a clear self-serve API key flow for agents (ideally via sign-in with verified identity, notlogin-style, or simple OAuth)",
    "Document rate limits and free-tier quotas explicitly so agents can plan request budgets",
    "Return structured error payloads on tile/API failures (status codes + reason) to improve first-try success",
    "Add a status/uptime page for reliability perception",
    "Clarify freemium tier boundaries in the analysis layer so agents can quote pricing confidently"
  ]
}