What Is Agentic Customs? Tools, Workflows and Limits

If every vendor now says “AI agent,” agentic customs here means a workflow in which an AI agent selects and calls tools to help prepare customs work, while the organisation defines evidence requirements and approval boundaries. That is a working product definition, not a legal status or a standardized certification.

If the phrase is used to mean “the agent filed the entry,” you are describing a different product than Doana’s public MCP catalog. That catalog extracts EASA Form 1; it does not submit declarations.

What makes a workflow agentic

A fixed parser accepts a file and returns fields. An agent can decide which supported tool to call, inspect a result and choose a permitted next step. That flexibility creates a need for explicit limits: tool availability should not be confused with authority to execute an operational action.

For example, an agent can extract an EASA Form 1, retrieve an in-flight job and present uncertain fields to a reviewer. Doana’s public tool catalog supports that sequence. It does not expose customs declaration submission.

The organisation still defines who may export reviewed data, who may send a message, and who may file. If those permissions live only in a prompt, the workflow is not under org-defined approvals.

How to read current logistics announcements

On 10 September 2026, DHL and Alibaba.com announced an agreement that includes exploring integration of DHL Global Forwarding services into Accio. “Explore” means the announcement is not a completed live integration, and it is not a Doana product or partnership.

CargoAi publishes MCP connector documentation, and Warp describes a freight MCP offering. Those pages are other providers’ freight MCP docs. Doana does not quote, book or track, and still only extracts EASA Form 1.

Where MCP fits

MCP supplies a common way for an agent client to discover and call external tools. The Streamable HTTP specification describes one transport for that connection. It does not classify goods, validate documents, or authorize a customs declaration. Those decisions belong to the services and organizations using it.

Doana’s endpoint is https://doana.ca/api/mcp. The /mcp website page is not the transport. OpenAPI on Doana describes the MCP tools; it does not add a REST POST /extract.

A bounded Doana walkthrough

Choose a document type (EASA Form 1), an output schema (easa-form-1-v1), a named review owner and a failure path. Measure corrections and unresolved exceptions before extending the workflow into filing systems you already control.

Concrete sequence, still not filing:

1. Confirm the file is an EASA Form 1 you are authorized to process. Classify anything else out.
2. Connect ChatGPT, Claude or Codex using the integrations index. Complete OAuth. Call get_usage.
3. Upload through the client’s supported path (file, content_base64 up to 64 KiB, or create_mcp_upload / browser_upload_url). TIFF is rejected. PDF 50 MB / 20 pages, JPEG/PNG 20 MB.
4. Call extract_easa_form1. Persist job_id. Poll get_extraction_result while status is dispatch_pending, queued, running, or outcome_unknown. Import only when status is succeeded, documentType is easa_form_1, and result is present.
5. Review uncertainFields and serial arrays against the PDF. Export only reviewed values into the broker or forwarder system of record.

Five files per personal account per UTC week. MCP_QUOTA_EXHAUSTED waits until Monday 00:00 UTC unless paid credits exist. Failed or out-of-scope jobs refund the unit. If the packet is FAA-only, stop: FAA 8130-3 API availability is the planning page.

What to measure before calling the workflow agentic

Measure corrections, unresolved exceptions, duplicate jobs under timeout, and whether filing still requires a named person in the system of record. If the agent can send the declaration without that person, you have not kept org-defined approvals. Protocol support is not filing authority by itself.

If Warp or CargoAi is in the same agent, give those connectors separate permissions so extracting a Form 1 cannot book. That split is part of the definition, not an afterthought.

For Doana, a concrete starting point is EASA Form 1 extraction. See the Customs MCP Server guide for the current scope, or AI customs agent workflow for a proposed review process.

What is not agentic customs

A chat that invents origin, a model that files without a named person, or a connector that books freight because a Form 1 extracted cleanly. Those are automation without the approval boundary. MCP made the call possible; it did not make it authorized.

Doana’s public catalog still only exposes extract_easa_form1.