Predictika · AI assistants clearing exports

An AI assistant’s export clearance, checked before anything ships

An AI assistant at a US manufacturer prepares shipments, reexports and technology releases and says whether each one needs an export license. Before anything goes out, it sends the facts to the Validator: how the item is classified, where it is going, what it will be used for, which license exception is claimed, what license is on file, and what the assistant itself concluded. The Validator works out whether the item is subject to the rules, whether a license is required, whether the exception or license actually covers this shipment, and returns every finding together.

Corvane Systems Inc. is a fictional exporter. The scenarios are illustrative and this page is not legal advice. The reference tables the validator uses are small illustrative excerpts of the Commerce Control List and Country Chart, dated October 6, 2026, and must be verified before any real use. The validator takes facts as input; it holds no sanctions list and sees no personal data.

Scope: US export control determinations for items classified as EAR99 or under ECCNs 3A991, 3A001, 6A003, 2B001, 5A002, 3E001 and 9A012, shipped, reexported or released as technology to ten listed destinations, with license exceptions LVS, GBS, TSR and STA. See everything this validator covers

The validator decides one question for one proposed export, reexport or technology release: allow, needs approval or block. It handles any case involving the listed classifications, destinations, end uses and license exceptions, not just the scenarios shown on this page.

  • Covered. Whether the item is subject to the EAR (de minimis US content of foreign-made items, with the lower limit for the most restricted destination group; deemed exports of technology to foreign nationals, excluding permanent residents and protected individuals). Whether the country chart requires a license for the classification and destination. The military end-use rule, embargoed destinations and weapons-of-mass-destruction end uses. Whether the claimed license exception (LVS, GBS, TSR, STA) is available for this item, destination and value, and whether its paperwork is on file. Whether the license on file covers this item and destination, has not expired and has enough balance. The end-use statement for licensed shipments to restricted destinations. Red-flag indicators. Whether the assistant’s own license determination is right.
  • Not covered. Defense articles under the ITAR; sanctions screening of the parties and their owners (a separate validator); license applications; the encryption exception (ENC) and classification of items not in the list above; the rest of the Commerce Control List and Country Chart; any rule published after October 6, 2026; and the company’s own systems and live data.
  • Assumptions. The classification, country group, ownership and screening facts arrive as inputs from the exporter’s own systems and are not verified here. The tables are illustrative excerpts and some entries are simplified.
The AI trade-compliance assistantProposes a shipment, reexport or technology release and states whether it needs a license.
Predictika validatorApplies every export rule at once and returns the verdict, each finding, and how it reached its determination.
The exporterShips only what the validator allows; the compliance officer sees what needs approval.

9 scenarios in 4 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI trade-compliance assistant says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI trade-compliance assistant (scripted)

Before acting, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  


    
Where rules-based screening gets it wrong
Click to expand
    
Our assessment of what a typical rules-based trade-compliance tool (classification lookup, country-chart lookup and workflow holds) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built. A single lookup, such as a chart cell or a license balance, is routine for these tools and is left out of the table.

    
What the validator caughtTypical rules-based toolPredictika
A license determination the assistant states that disagrees with the computed oneCannot do it
The assistant’s conclusion is free text in a message. Nothing compares it with the computed determination unless someone builds that integration for each field.		The stated determination travels with the request and is compared with the computed one on every call.
De minimis percentage and deemed export treated as part of the same determinationOnly with workarounds
The percentage is usually worked out in a spreadsheet or by hand, with the lower limit for the most restricted group applied by whoever remembers it; the permanent-resident carve-out is a separate manual step.		The arithmetic, the threshold for the destination and the carve-out are rules in the same model and run on every call.
A license exception claimed for the wrong reason: value limit, item, destination group, missing paperworkOnly if someone is vigilant
Each exception is its own checklist. It works when the reviewer picks the right one; nothing stops a claim that fails two conditions from slipping through on the first it passes.		Every condition of the claimed exception is checked together, and each failure is listed.
Several problems in one request, reported together with a consistent verdictOnly with workarounds
Workflow holds usually stop at the first failed check, so the assistant fixes one thing, resubmits and finds the next.		Every finding comes back in one answer, ordered block, approval, then note, with one verdict.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the facts arrive; one problem never hides another. Blocking findings stop the request. Approval findings need a compliance officer. The examples below are the messages returned in the recorded runs.

    
1Item not classified: The item has no export classification. Classify it as an ECCN or EAR99 before any shipment, release or reexport.
2Weapons-of-mass-destruction end use: The end use is a nuclear, chemical, biological or missile end use. No license exception or ordinary license applies. Refer to the compliance officer.
3The stated license determination is wrong: The request says no license is required, but one is required for ECCN 3A001 to Singapore.
4Exception not available for this item: License exception STA is not available for ECCN 9A012.
5Exception not available for this destination: License exception LVS is not available for shipments to China. The destination is not in a country group the exception allows.
6Over the exception value limit: This shipment of $4,200 is over the $3,000 limit for license exception LVS on ECCN 6A003.
7Exception paperwork missing: License exception TSR requires a signed consignee statement or written assurance on file, and none is on file.
8No license on file: A license is required for ECCN 3A001 to Singapore and no license is on file.
9License expired: The license on file expired 5 days before the planned ship date.
10Not enough license balance: The license on file has $150,000 remaining and this shipment is $180,000.
11License covers a different item or destination: The license on file covers 6A003 to Singapore, not 6A003 to Mexico.
12End-use statement missing: A signed end-use statement from the end user is required for a licensed shipment to China and none is on file.
13Embargoed destination needs sign-off: Iran is an embargoed destination. A valid license is on file, but the compliance officer must sign off on every shipment.
14Military end-use review: Military end use in China. ECCN EAR99 is not on the military end-use list, so no license is required, but the compliance officer must review the end user.
15Red flags to resolve: 1 red flag indicator was reported. The compliance officer must resolve it with the customer before shipment.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Electronic components to Singapore: No license on file

    
The agent's request. Please clear a shipment of 3A001 high-performance electronic components to Singapore, valued at $180,000. No license is required for this order, so I plan to ship it today.

    
Verdict: Blocked.

    
    
      
  • The stated license determination is wrong. The request says no license is required, but one is required for ECCN 3A001 to Singapore.
    • 
      
  • No license on file. A license is required for ECCN 3A001 to Singapore and no license is on file.
    • 
      
  • How the validator determined this. License required by the country chart. 1 control reason of ECCN 3A001 applies to Singapore.
    • 
    

    
2. Electronic components to Singapore: License found, balance too low

    
The agent's request. Please clear the same shipment of 3A001 components to Singapore, valued at $180,000. A license is required, and there is a license on file for 3A001 to Singapore with $150,000 remaining and 75 days left.

    
Verdict: Blocked.

    
    
      
  • Not enough license balance. The license on file has $150,000 remaining and this shipment is $180,000.
    • 
      
  • How the validator determined this. License required by the country chart. 1 control reason of ECCN 3A001 applies to Singapore.
    • 
    

    
3. Electronic components to Singapore: License with enough balance

    
The agent's request. Please clear the same shipment of 3A001 components to Singapore, valued at $180,000. A license is required, and there is a license on file for 3A001 to Singapore with $400,000 remaining and 75 days left.

    
Verdict: Allowed.

    
    
      
  • How the validator determined this. License required by the country chart. 1 control reason of ECCN 3A001 applies to Singapore.
    • 
    

    
4. Cameras to Germany under a license exception: Exception LVS claimed

    
The agent's request. Please clear a shipment of 6A003 cameras and imaging systems to Germany, valued at $4,200, under license exception LVS.

    
Verdict: Blocked.

    
    
      
  • Over the exception value limit. This shipment of $4,200 is over the $3,000 limit for license exception LVS on ECCN 6A003.
    • 
      
  • No license on file. A license is required for ECCN 6A003 to Germany and no license is on file.
    • 
      
  • How the validator determined this. License required by the country chart. 1 control reason of ECCN 6A003 applies to Germany.
    • 
    

    
5. Cameras to Germany under a license exception: Exception STA with consignee statement

    
The agent's request. Please clear a shipment of 6A003 cameras and imaging systems to Germany, valued at $4,200, under license exception STA. The consignee statement is on file.

    
Verdict: Allowed.

    
    
      
  • How the validator determined this. License required by the country chart. 1 control reason of ECCN 6A003 applies to Germany.
    • 
    

    
6. Foreign-made machine tool for China: 15 percent US content

    
The agent's request. Please clear a reexport of a foreign-made 2B001 machine tool to China, fair market value $80,000. The controlled US content is $12,000. No license is required, and the end-use statement is on file.

    
Verdict: Allowed.

    
    
      
  • How the validator determined this. Not subject to the EAR. US-controlled content is 15 percent of the foreign-made item, at or under the 25 percent de minimis limit for China.
    • 
    

    
7. Foreign-made machine tool for China: 30 percent US content

    
The agent's request. Please clear a reexport of a foreign-made 2B001 machine tool to China, fair market value $80,000. The controlled US content is $24,000. No license is required, and the end-use statement is on file.

    
Verdict: Blocked.

    
    
      
  • The stated license determination is wrong. The request says no license is required, but one is required for ECCN 2B001 to China.
    • 
      
  • No license on file. A license is required for ECCN 2B001 to China and no license is on file.
    • 
      
  • How the validator determined this. Subject to the EAR. US-controlled content is 30 percent of the foreign-made item, over the 25 percent de minimis limit for China.
    • 
      
  • How the validator determined this. License required by the country chart. 2 control reasons of ECCN 2B001 apply to China.
    • 
    

    
8. Approvals the compliance officer must give: Military end user, EAR99 pumps

    
The agent's request. Please clear a shipment of EAR99 pumps to China, valued at $58,000. The end user is a military customer and the end-use statement is on file. No license is required for EAR99 items.

    
Verdict: Needs approval.

    
    
      
  • Military end-use review. Military end use in China. ECCN EAR99 is not on the military end-use list, so no license is required, but the compliance officer must review the end user.
    • 
      
  • How the validator determined this. No license required. No control reason of ECCN EAR99 applies to China.
    • 
    

    
9. Approvals the compliance officer must give: Red flag on a licensed shipment

    
The agent's request. Please clear a shipment of 2B001 machine tools to Mexico, valued at $95,000. A license is required, and there is a license on file for 2B001 to Mexico with $120,000 remaining and 90 days left. The customer asked us to deliver to its freight forwarder as the final destination.

    
Verdict: Needs approval.

    
    
      
  • Red flags to resolve. 1 red flag indicator was reported. The compliance officer must resolve it with the customer before shipment.
    • 
      
  • How the validator determined this. License required by the country chart. 2 control reasons of ECCN 2B001 apply to Mexico.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI assistant at a US manufacturer prepares shipments, reexports and technology releases and says whether each one needs an export license. Before anything goes out, it sends the facts to the Validator: how the item is classified, where it is going, what it will be used for, which license exception is claimed, what license is on file, and what the assistant itself concluded. The Validator works out whether the item is subject to the rules, whether a license is required, whether the exception or license actually covers this shipment, and returns every finding together.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please clear a shipment of 3A001 high-performance electronic components to Singapore, valued at $180,000. No license is required for this order, so I plan to ship it today.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with two findings, all in one answer. The request says no license is required, but one is required for ECCN 3A001 to Singapore. A license is required for ECCN 3A001 to Singapore and no license is on file.
    6. 
      
  6. The validator returned two blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the request are checked against each other.
    7. 
      
  7. What this shows: for a license determination the assistant states that disagrees with the computed one, a rules-based tool cannot do this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the Stated Lic to required. It sets the Lic Status to on_file, the Lic Days Left to 75, the Lic Remaining to 150000, the Lic Dest to singapore and the Lic ECCN to ECCN_3A001.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. The license on file has $150,000 remaining and this shipment is $180,000.
    12. 
      
  12. Two findings cleared, but the change brings a different blocking finding: not enough license balance.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the Lic Remaining to 400000.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared, and the validator's figure matches the request.
    18. 
      
  18. Two problems caught in one call, fixed in two passes, and a clean request. That is the value of Predictika's validator: catching mistakes before the action runs.
    19.