# OpenWeatherMap — API Agent Score

> Score: 59/100 (Grade: D) | Domain: openweathermap.org | Rubric: 1.0.0 | Checked: July 24, 2026

OpenWeatherMap scored 59/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 59/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 72/100 (B)
- Developer Experience: 52/100 (D)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 58/100 (D)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — 4 of 50 public signatures use loose types (anyTypeRatio=0.080). Investigated: sdk 93%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://home.openweathermap.org/users/sign_up; free tier / sandbox documented. Investigated: docs 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [fail] Description completeness — 23/23 operations lack a description. Investigated: sdk 0%.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (llmstxt/openweathermap_llms_txt, 1531 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 75%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 50 sampled pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 100% or newest entry older than 90 days. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 50 sampled pages convert to over 100K chars (max 958K HTML → 119K markdown (92% boilerplate)). Investigated: docs 80%.
- [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 2 assessed pages (2 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

OpenWeatherMap's API program shows strength in discovery reachability and crawlability, but two areas are holding back partner success at scale: developer experience and agent usability. Partners today lack a fast path to a first working call — no quickstart, no code samples, and thin descriptions mean onboarding takes weeks instead of minutes. Simultaneously, AI agents have no reliable context layer (no AGENTS.md, no structured docs, no runnable examples) and cannot safely execute or validate workflows. Prioritize closing the onboarding and agent-readiness gaps first, as they directly block both human partners and the automated agents they increasingly rely on.