Dados Abertos - API

{
  "service_type": "platform",
  "base_url": "https://inpe.br",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "Open government data provided by INPE (Brazilian National Institute for Space Research); publicly funded, no cost for access."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Open data access",
    "Wildfire/fire monitoring data",
    "Processed satellite-derived fire data",
    "Brazilian territory fire monitoring (Queimadas program)"
  ],
  "raw_analysis": "The service described is 'Dados Abertos - API' from INPE (Instituto Nacional de Pesquisas Espaciais), the Brazilian National Institute for Space Research. It provides open data processed by INPE's Queimadas (wildfires/burnings) monitoring group.\n\nWhat it does: INPE's Queimadas program is a long-running (since the late 1980s) Brazilian government initiative that monitors active fires and burn scars across Brazil and South America using satellite imagery (e.g., Aqua, Terra, NOAA, Suomi-NPP/VIIRS, and other sensors). The open data API makes this processed fire detection data publicly available for researchers, government agencies, NGOs, journalists, and the general public.\n\nWho it's for: Primarily Brazilian government agencies, environmental researchers, academic institutions, journalists reporting on Amazon deforestation and fires, NGOs, and international organizations monitoring climate and land-use change.\n\nMaturity: INPE is a well-established, reputable government research institution. The Queimadas program is one of the most authoritative sources for fire data in Brazil and has been operating for decades. Data is generally considered high quality and is widely cited.\n\nIntegrations: As an open data initiative, it typically integrates with data portals, GIS tools, and research pipelines. Common access patterns include web downloads (CSV, shapefiles, GeoTIFF), FTP, and possibly OGC/WMS services. A REST API may exist (e.g., through the BDQueimadas portal) but details are not specified here.\n\nThe provided URL 'https://inpe.br:dados-abertos' is malformed (uses a colon rather than a path separator) and likely does not resolve to an actual endpoint. The real portal is typically at https://queimadas.dgi.inpe.br or https://dados.gov.br. Actual API endpoints, rate limits, and authentication details could not be determined from the provided information. Authentication is almost certainly not required, as this is open government data."
}

0/3 tests passed

{
  "overall": 54,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 4.0,
    "response_parseability": 6.0,
    "error_clarity": 4.0,
    "doc_quality": 4.5,
    "auth_simplicity": 9.0,
    "latency": 3.0,
    "consistency": 3.0
  },
  "pricing_normalized": {
    "model": "free",
    "cost_to_agent_user": "0",
    "notes": "Open government data from INPE; no payment, no tiering."
  },
  "issues": [
    "All three Uptime checks failed with DNS resolution errors ('No address associated with hostname'), indicating the tested hostname is unreachable or misconfigured.",
    "No security headers observed (moot given DNS failures, but no TLS/HSTS signal was captured).",
    "No robots.txt or llms.txt discovered, suggesting no agent-oriented crawling guidance exists.",
    "Documentation quality could not be verified because endpoints were unreachable.",
    "Latency readings (68-521ms) reflect DNS failure returns, not real round-trip performance, making real latency unknown."
  ],
  "recommendations": [
    "Verify the correct endpoint host (INPE may expose services via different domains such as terrabrasilis.dpi.inpe.br or queimadas.dgi.inpe.br) before recommending to agents.",
    "Publish an llms.txt or machine-readable capabilities manifest so agents can discover data endpoints programmatically.",
    "Document API authentication, rate limits, and data schema clearly to improve error clarity and parseability.",
    "Provide a status page or uptime SLA to help agents assess consistency before integrating.",
    "Structure data access via stable REST/GeoJSON/WMS endpoints with clear versioning so agents can parse responses reliably."
  ]
}