The export rules that actually reach a one-person AI business

On 20 November 2025 the US Department of Justice announced charges against four people over an alleged effort to move controlled Nvidia GPUs to China. Two are US citizens and two are nationals of the People’s Republic of China. The counts include conspiracy to violate the Export Control Reform Act, violations of that Act, smuggling and money laundering, and the department set out maximum penalties of 20 years for each Export Control Reform Act count, 10 years for each smuggling count and 20 years for each money laundering count. Assistant Attorney General John A. Eisenberg said the indictment alleges “a deliberate and deceptive effort to transship controlled NVIDIA GPUs to China by falsifying paperwork, creating fake contracts, and misleading U.S. authorities” [1]. The defendants in that case are people, not corporations, and that is the part worth your attention.

You do not ship GPUs. Your AI spend is an API bill and two or three subscriptions, and the reasonable first reaction to a chip-diversion case is that it belongs to a different industry. Mostly it does. But the rules those cases run on are written broadly enough to touch a freelancer with one overseas client, and the enforcement shape they demonstrate is the one that matters to you: liability that lands on the individual who signed. This guide is for a solo operator or a small team selling AI-assisted work, with no compliance function and no lawyer on retainer. It is not for you if you ship, resell or lease hardware, hold controlled technical data, or sell to a government customer. Those are real trade-compliance problems and they need a real trade-compliance lawyer.

Enforcement names people, and you are the only name on your business

Look at the penalty structure in the underlying statute and the personal shape of it is explicit. Under 50 U.S.C. 4819, a person who “willfully commits, willfully attempts to commit, or willfully conspires to commit, or aids and abets in the commission of” an unlawful act under the section “shall be fined not more than $1,000,000” and, “in the case of the individual, shall be imprisoned for not more than 20 years, or both” [2].

The civil track sits in the same section, and its text does not use the word willfully at all. It provides for “a fine of not more than $300,000 or an amount that is twice the value of the transaction that is the basis of the violation with respect to which the penalty is imposed, whichever is greater” [2]. Read the two subsections next to each other and the practical point is that the criminal exposure turns on intent while the civil exposure, as written, does not.

Inside a large company there is a layer between an employee and that statute. Someone else reviews the contract, someone else runs the screening, someone else decides whether an order looks strange. That layer is the reason most people in most companies never think about export rules at all. In a business of one to five people, the layer does not exist. The person who negotiates the deal, writes the invoice, issues the login and clicks through the terms is the same person, and there is nobody upstream who was supposed to catch it.

Buying tokens is not an export, and the definition tells you what is

Start with what the word means, because the everyday sense of it is narrower than the legal one. Under 15 CFR 734.13, an export is “an actual shipment or transmission out of the United States, including the sending or taking of an item out of the United States, in any manner.” The same section then adds the clause that surprises people: “releasing or otherwise transferring ‘technology’ or source code (but not object code) to a foreign person in the United States.” And the destination is not where the person is standing. “Any release in the United States of ‘technology’ or source code to a foreign person is a deemed export to the foreign person’s most recent country of citizenship or permanent residency” [3].

Read that quickly and it sounds like every contractor you have ever onboarded is an export event. It is not, because the rule only reaches items that are subject to the Export Administration Regulations in the first place, and 15 CFR 734.3 draws that boundary. Information and software that “are published, as described in § 734.7” sit outside the regulations, as do information and software that “arise during, or result from, fundamental research” and material that appears “in patents or open (published) patent applications available from or at any patent office” [4]. Inside the boundary, the section notes that items subject to the regulations which are not listed on the Commerce Control List are designated “EAR99” [4].

So the test is not whether a file feels technical. It is whether the thing you are releasing is controlled information about a controlled item. Go through the material you actually hold for a client and try to describe any of it that way. For a marketing consultancy or a bookkeeping automation shop the exercise usually ends in about a minute with nothing on the list, and that is a better answer than a vague sense of unease.

The reason to know the definition anyway is that it tells you where the exposure would appear if it ever did. It is not the moment a box crosses a border. It is the moment you hand access to someone. If you take on a client in a controlled sector and end up holding their technical documentation, the release happens when you add a contractor to the repository, not when you email a deliverable overseas [3]. That is a specific, checkable moment, and it is the one to slow down at.

The export clause is already in the contract you clicked through

The rule most likely to bite you this year is not a statute. It is a term of service you agreed to without reading. Anthropic’s Commercial Terms state that “Customer may not export or provide access to the Services to persons or entities or into countries or for uses where it is prohibited under U.S. or other applicable international law,” and specify that this covers “(a) to countries where export from the US or into such country would be prohibited or illegal without first obtaining the appropriate license, and (b) to persons, entities, or countries covered by U.S. sanctions” [5]. OpenAI publishes a list of the countries and territories its API supports and warns that “Accessing or offering access to our services outside of the countries and territories listed below may result in your account being blocked or suspended” [6].

Note the phrase “offering access to.” If you have built anything on top of these APIs and let people sign up for it, you have inherited a geographic restriction that you did not write and probably have not looked at. The realistic worst case here is not a prosecution. It is a Tuesday morning where the account behind your product is suspended, your customers see errors, and you are explaining to a vendor’s trust and safety team who your users are.

The fix is boring and takes an afternoon. Read the supported-countries list for each API you resell access to, once. Put the country of use into your contract or your signup flow, not just the billing country, because the two diverge more often than you would expect. And when a client asks you to work around a geographic block on their behalf, treat that request as the answer to a question rather than a technical problem to solve.

The standard is whether you checked, not whether you knew

Small operators tend to assume the protective thing is to know as little as possible. The government’s published guidance says the opposite, in unusually plain language. The Bureau of Industry and Security’s Know Your Customer guidance sets out that “when ‘red flags’ are raised in information that comes to your firm, you have a duty to check out the suspicious circumstances.” Absent them, “there is no affirmative duty upon exporters to inquire, verify, or otherwise ‘go behind’ the customer’s representations” [7].

Arranging not to hear the bad news, though, is treated as worse than hearing it. The same guidance tells firms not to “cut off the flow of information that comes to your firm in the normal course of business,” offers as its worked example “do not instruct the sales force to tell potential customers to refrain from discussing the actual end-use, end-user, and ultimate country of destination for the product your firm is seeking to sell,” and states that “An affirmative policy of steps to avoid ‘bad’ information would not insulate a company from liability, and it would usually be considered an aggravating factor in an enforcement proceeding” [7].

Most of the listed red flags are about physical goods and will never appear in your inbox. Several transfer directly to a services business. The customer “is reluctant to offer information about the end-use of a product.” The product’s capabilities “do not fit the buyer’s line of business.” Delivery dates are vague, or deliveries are planned for out-of-the-way destinations, or a freight forwarding firm is named as the final destination. The customer “is willing to pay cash for a very expensive item when the terms of the sale call for financing,” or declines routine installation, training or maintenance services [7]. Rewrite those in your own terms and you get a short, recognisable list: the client who will not say what the output is for, the engagement whose deliverable does not match the business you can see, the request to issue credentials to a person in a country the contract never mentions, and the buyer who wants to prepay in a way that leaves no paper.

Screening a new client is free and takes about ten minutes

There is one government tool worth putting into your onboarding, and it costs nothing. The Consolidated Screening List is “a list of parties for which the United States Government maintains restrictions on certain exports, reexports, or transfers of items,” and it combines the screening lists of three departments: Commerce, through the Bureau of Industry and Security; State, through the Bureau of International Security and Non-proliferation and the Directorate of Defense Trade Controls; and Treasury, through the Office of Foreign Assets Control [8]. It has a free search engine whose fuzzy matching “allows a search without knowing the exact spelling of an entity’s name,” an API that “enables computers to freely access the CSL in an open, machine-readable format,” and downloads in CSV, TSV and JSON. All of the tools are updated automatically every day at 5:00 AM EST/EDT [8].

The practice that fits a small business is narrow. Screen the legal entity name and the name of the person signing, not the trading name on the website. Do it before the first invoice on any new counterparty outside your usual market, and again at renewal rather than treating the first check as permanent. Save the result with the date on it, in the client folder, next to the contract. That file is the whole point: it is the difference between “we checked and the list was clean on 5 September” and a shrug.

A hit is not a verdict. Fuzzy matching on common names produces false positives constantly, and the list is not the same thing as a finding about your client. A hit is a reason to slow down, ask for the entity’s registration details, and decide with more information than you had.

What still goes wrong

A clean screen is a snapshot, not a status. The Consolidated Screening List is updated every day [8], which is another way of saying the answer you got last quarter may no longer be the answer. Screening also catches names, and a counterparty can be controlled by a party you would care about without that party’s name appearing anywhere you can see. Neither problem is solvable by a small business on its own budget, which is a reason to date your checks rather than a reason to skip them.

The two rule sets in this guide are also genuinely different things, and complying with one tells you nothing about the other. A vendor’s supported-countries list is a commercial policy, and the stated consequence of ignoring it is your account being blocked or suspended [6]. Export law is enforced by a government, against people, with fines and prison terms attached [1][2]. A country can be on a vendor’s approved list and still be a bad idea for a specific transaction, and a client can be perfectly legal to serve while your API terms forbid you from serving them.

Finally, the honest limit. Everything here is the version that fits on one page for a business with no compliance function. It is not legal advice, and the moment your work touches hardware, controlled technical data, a defence or aerospace client, or anything that looks like re-exporting a restricted item, the correct next step is a trade lawyer rather than a checklist. The value of the checklist is that it keeps you out of the situations where you would need one.