Applicability API & Data
Registration → configuration → AD, inside your product.
The same applicability engine behind Aviagent, as an API and licensed data feed. Bring the intelligence into your system; keep your own interface.
Who it's for
Aviation software vendors
Add airworthiness-directive applicability to your MRO, CAMO, or fleet product without building the data pipeline.
Lessors & asset managers
Resolve the AD position of any tail at transfer, redelivery, or portfolio review — from the authority's own data.
Analytics & data platforms
License the relationship data — applicability, supersedure, comply-once links — as a maintained feed.
What you get
Applicability API
Per-tail resolution: registration → type/TCDS → configuration → the ADs that actually apply.
Bulk relationship data
The AD graph — applicability, supersedure, and EASA↔FAA comply-once links — on a refresh schedule.
Authority freshness
EASA and FAA synchronised daily, with the source and last-sync date on every record.
Provenance on every answer
Each result traces to its authority source — public facts kept distinct from derived relationships.
How it works
One request per aircraft returns the applicable set with the reasoning and source behind each AD.
POST /v1/applicability
{ "registration": "LN-NIK", "as_of": "2026-07-25" }
→ {
"aircraft": { "type": "…", "msn": "…", "engine": "…" },
"applicable_ads": [
{ "id": "EASA-AD-…", "source_url": "…", "reason": "…" }
]
}Illustrative — final request/response shape confirmed at onboarding.
Commercial model
Usage-based tiers with an annual minimum. Permitted-use, redistribution, and model-training terms are set out in the licence. Tell us your volume and use case and we'll scope it.
Provenance & licensing
Public authority facts stay distinct from Aviagent's derived relationship data. Every record carries its source and freshness, so what you license is traceable and defensible.
Request API access
Tell us what you're building and we'll follow up with access and terms.