API & MCP

REST + Model Context Protocol. Real FAA data; agent-payable via x402.

REST

# Match ADs to one aircraft (free)
GET https://faa-ad.dropwatchhq.com/v1/match?make=Cessna&model=172

# Assess a fleet (paid: x-api-key)
POST https://faa-ad.dropwatchhq.com/v1/assess   x-api-key: fad_...
  { "aircraft":[ {"tail":"N12AB","make":"Piper","model":"PA-28-181","hoursTIS":4210} ] }

# Audit CSV export (Fleet+ tier)
GET https://faa-ad.dropwatchhq.com/v1/audit.csv   x-api-key: fad_...

MCP

POST https://faa-ad.dropwatchhq.com/mcp
{ "jsonrpc":"2.0","id":1,"method":"tools/call",
  "params":{ "name":"match_ads","arguments":{"make":"Cessna","model":"172"} } }

Tools: match_ads (free) · recurring_due (free) · assess_fleet (paid / x402)

x402 (agent pay-per-call)

Machine-discoverable at /.well-known/x402 and /llms.txt. assess_fleet returns a 402 challenge payable in USDC on Base — no login.

Informational only — not a maintenance record. This tool surfaces public FAA Airworthiness Directives and computes indicative deadlines from public AD text. It does not determine serial-number or installed-appliance applicability (which can depend on manufacturer Service Bulletins). Always verify applicability and method of compliance with your A&P/IA before any maintenance or dispatch decision. Compliance with 14 CFR Part 39 remains the owner/operator's legal responsibility (14 CFR 91.403).