USGS Water Services

{
  "service_type": "platform",
  "base_url": "https://waterservices.usgs.gov",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "free", "details": {"public_data": "USGS water data is public domain, available at no cost"}},
  "rate_limits": {},
  "capabilities": ["provide real-time and historical water data", "serve water quality parameters", "serve water levels and streamflow", "support site-specific queries", "support parameter-based queries", "provide data in multiple formats (JSON, XML, RDB)", "support batch requests", "offer daily value and instantaneous value data", "provide groundwater levels", "provide water quality samples"],
  "raw_analysis": "USGS Water Services is a public web service provided by the U.S. Geological Survey for accessing water data from rivers, lakes, and groundwater. It is a mature, government-operated service that has been serving hydrologic data for many years. The service is free and open to the public, requiring no authentication. It offers RESTful endpoints for retrieving current and historical observations of streamflow, water levels, water quality, and groundwater. Data is available in multiple formats including JSON, XML, and RDB (tab-separated). The service supports queries by site, parameter, and time window. It is widely used by researchers, environmental agencies, and weather services. No rate limits are publicly documented, but users are encouraged to limit large requests. The service lacks a comprehensive public API dashboard but has good documentation. It integrates with other USGS systems and is a key source for water data in the US."
}

1/3 tests passed

{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 7.0,
    "response_parseability": 9.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 9.0,
    "latency": 8.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "type": "free",
    "notes": "USGS water data is public domain, available at no cost"
  },
  "issues": [
    "robots.txt returns 404, but no sign of blocking; should be implemented",
    "No llms.txt file, which could aid AI agents in discovery",
    "Documentation scattered across multiple pages; not consolidated for quick start",
    "Error responses may use non-standard formats (XML/HTML) depending on endpoint"
  ],
  "recommendations": [
    "Add a robots.txt to explicitly allow crawling and avoid ambiguous 404s",
    "Implement llms.txt to provide structured overview and API details for AI agents",
    "Provide consolidated quick-start guide with Python/curl examples for the top endpoints",
    "Standardize error responses in JSON with clear messages and status codes",
    "Publish official API documentation in OpenAPI format for auto-parsing"
  ]
}