Aviation document tools for your agent
Extract EASA Form 1 with Aviation Customs AI Agents
On day one, an aviation customs AI agent should extract one supported certificate, show uncertainty, and stop. Treating a tidy chat as a filed entry is how review gets skipped.
Pick a customs, aviation, or freight review workflow below. The public tool is extract_easa_form1. Filing, booking, and airworthiness stay in the systems you already trust.
Public catalog as of 12 September 2026: extract_easa_form1 only.
Customs preparation
A customs agent extracts one EASA Form 1, builds a review table with source, field, value, uncertainty and reviewer decision, and leaves filing in the broker system of record. It does not classify goods or submit declarations.
Use the customs child page when mixed packets and silent “corrections” are the bottleneck. Success is a draft with source references. Origin and valuation stay human-supplied evidence.
Aviation receiving and AOG
An aviation agent shows the next document task, extracts Form 1 identifiers, and keeps job_id so AOG teams do not double-extract after a timeout. Extraction confidence is not a release-to-service. Serial numbers remain arrays. release13 and release14 stay separate objects on the result.
Use the aviation child page when receiving or AOG document chaos is the bottleneck. The agent does not decide installation eligibility. Compare part and serial characters with the source PDF before matching inventory.
Freight documents, not bookings
A freight agent prepares certificate data beside a shipment reference. Doana does not quote, book or track. Warp and CargoAi publish their own freight MCP products; those are not Doana operations. Extracting a Form 1 must not authorize a paid booking.
Use the freight child page when the bottleneck is aviation documents on a forwarding desk. Keep transport MCP connections behind separate permissions from extract_easa_form1.
How to connect
Create a personal account, register https://doana.ca/api/mcp as Streamable HTTP, complete OAuth, and list tools. ChatGPT needs a custom MCP app and a same-turn signed attachment. Claude cannot see local disk paths. Codex can send local bytes or use browser_upload_url instead.
Call get_usage before the first file. Poll get_extraction_result. Do not invent a REST /extract. The /mcp website page is not the protocol endpoint. Five files per personal account per UTC week. Client setup lives under /en/integrations.