Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request API credentials (client_id/client_secret) from the FAA by emailing NOTAMS@faa.gov, or via the FAA API portal - self-serve signup is not generally available.
Authenticate using the OAuth2 client-credentials-style scheme described in your onboarding materials.
Query the filtered-NOTAM-search endpoint with parameters such as ICAO location, radius, or effective-date range.
Request the response in your desired format (GeoJSON or AIXM).
Parse returned NOTAM records for ID, classification, location, effective/expiration times, and free-text body.
Known gotchas
There is no fully public self-service signup - credential provisioning is manual and can take time, so plan ahead.
The FAA has been migrating from legacy NOTAM Search/SWIM systems to a newer NOTAM Management System (NMS) - confirm which base URL/version your credentials target, since endpoints have moved during this transition.
AIXM and GeoJSON response schemas differ significantly in structure - pick one consistently for your parsing logic rather than assuming a shared shape.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?