Aviation Weather Center
The NOAA/NWS Aviation Weather Center (AWC) public data API provides machine-to-machine access to operational aviation weather products including METARs, TAFs, pilot reports (PIREPs/AIREPs), SIGMETs (domestic and international), G-AIRMETs and AIRMETs, Center Weather Advisories (CWAs), TFM convective forecasts (TCFs), area forecasts, area forecast discussions, meteorological information statements (MIS), and reference data for stations, airports, NAVAIDs, fixes, features, and obstacles. Responses are available in raw text, JSON, GeoJSON, XML, and (for METAR/TAF) IWXXM formats.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Aviation Weather Center the way a machine reads it — 49 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Aviation Weather Center scores 43.8/100 (thin), with a separate agent-readiness read of 45/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Aviation Weather Center
Each block below is one kind of artifact we hold for Aviation Weather Center. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Aviation Weather Center Navigational Data API
Decoded navigational information
Aviation Weather Center Weather Data API
Decoded weather information
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
AviationWeather.gov API
OPEN COLLECTIONRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aviationweather Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Aviationweather Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Aviation Weather Center API Rules
SPECTRALAviation Weather Center API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AviationWeather AIRMET
JSON SCHEMAAviationWeather Airport Info
JSON SCHEMAAviationWeather Domestic SIGMET
JSON SCHEMAAviationWeather Graphical AIRMET (G-AIRMET)
JSON SCHEMAAviationWeather International SIGMET
JSON SCHEMAAviationWeather METAR Observation
JSON SCHEMAAviationWeather Pilot Report (PIREP/AIREP)
JSON SCHEMAAviationWeather Station Info
JSON SCHEMAScroll within the panel for all 10 ·
JSON Structure 10
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Aviationweather Airmet Structure
JSON STRUCTUREAviationweather Airport Structure
JSON STRUCTUREAviationweather Airsigmet Structure
JSON STRUCTUREAviationweather Cwa Structure
JSON STRUCTUREAviationweather Gairmet Structure
JSON STRUCTUREAviationweather Isigmet Structure
JSON STRUCTUREAviationweather Metar Structure
JSON STRUCTUREAviationweather Pirep Structure
JSON STRUCTUREAviationweather Station Structure
JSON STRUCTUREAviationweather Taf Structure
JSON STRUCTUREScroll within the panel for all 10 ·
Examples 20
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Aviationweather Cwa Example
EXAMPLEAviationweather Fix Example
EXAMPLEAviationweather Mis Example
EXAMPLEAviationweather Taf Example
EXAMPLEAviationweather Tcf Example
EXAMPLEScroll within the panel for all 20 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Aviation Weather Center — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aviationweather · machine-readable index on apis.io