# WeatherAPI — API Agent Score

> Score: 63/100 (Grade: C) | Domain: weatherapi.com | Rubric: 1.0.0 | Checked: July 24, 2026

WeatherAPI scored 63/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/weatherapi)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 63/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 49/100 (F)
- Agent Discovery: 80/100 (A)
- Agent Understanding: 70/100 (B)
- Agent Usability: 41/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="1.0.2") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — Medium parameter complexity (avg 5.1 params/op; nested/body schemas present). Investigated: spec 83%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 63% example coverage (target 80%+). Investigated: spec 100%, docs 0%.

### Developer Experience

- [pass] Description completeness — 99% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [warn] Quickstart present — Quickstart page reachable (7 variants scanned starting at https://www.weatherapi.com/error.aspx) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 12 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%, sdk 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/weatherapi, 92 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt exists but contains no parseable links. Investigated: docs 80%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap present (12 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 3 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, spec 50%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 81%.
- [warn] Operation purpose clarity — 75% of operations are agent-inferable (target 90%+). Investigated: spec 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 1 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 2 server entries; no test-key prefixes documented. Investigated: spec 0%, docs 0%.

## Executive Summary

WeatherAPI's API design and discoverability are strong — partners and agents can find and understand the surface without friction. However, two areas are critically undermining partner program outcomes: onboarding is slow and self-serve because there is no developer portal with code samples or a changelog, and agents cannot operate reliably because idempotency, rate-limit signaling, pagination, and sandbox separation are all undocumented or absent. Prioritize closing the operational reliability and onboarding gaps first, then layer in agent-specific context to make the program fully AI-agent ready.