{"id":"dyneth02-air-quality-trends-analysis-project","name":"Air-Quality-Trends-Analysis-Project","af_score":27.0,"security_score":56.8,"reliability_score":12.5,"what_it_does":"AirSense is a full-stack air-quality monitoring and analytics platform. It aggregates multi-source PM2.5/PM10 data (Open-Meteo, OpenAQ, IQAir, WAQI) into a MySQL-backed time series, provides multi-city KPIs and comparisons, performs SARIMAX-based forecasting with evaluation metrics, and offers an LLM-based planning agent for natural-language analytics plus automated PDF report generation. Access is controlled via JWT authentication with tiered (Free/Pro/Enterprise) enforcement.","best_when":"Used as an academic/full-stack project where users can run the system end-to-end (frontend + FastAPI + MySQL) and are comfortable with architecture implied by the README rather than fully specified API contracts.","avoid_when":"When you need a clearly documented, stable external API surface for third-party programmatic integration, or when you require explicit details on rate limits, error codes, pagination conventions, and retry/idempotency behavior.","last_evaluated":"2026-03-30T15:33:28.619567+00:00","has_mcp":false,"has_api":true,"auth_methods":["JWT authentication"],"has_free_tier":true,"known_gotchas":["The README references an “MCP-style tool orchestration” approach, but no actual MCP server interface/tool contracts are provided in the reviewed content, so agent integration may require custom wiring.","LLM planning agent behavior is described at a high level (reflection/trace explainability), but there are no documented guarantees about determinism, tool selection constraints, or safe failure modes.","No API-level pagination, rate limit headers, or error-code mapping is documented here, which can cause brittle automation around list/query endpoints."],"error_quality":0.0}