Export Controls API: BIS Advisory Opinions and DDTC Commodity Jurisdiction Determinations

Short answer: the export control corpus you can query as JSON has three pieces, all under corpusType=AGENCY_GUIDANCE. 5,903 DDTC Commodity Jurisdiction determinations (ddtc_commodity_jurisdiction, 2010 to present, taken from DDTC's own XLSX export), 33 BIS Advisory Opinions (bis_advisory_opinion, 2003 to 2023), and 7 DDTC guidance documents (ddtc_guidance). Those sit next to the regulations themselves, 15 C.F.R. for the EAR and 22 C.F.R. for the ITAR, in the same search index. The CJ set is the interesting one: it is more than a decade of the US government answering, item by item, the single question every hardware exporter has to answer first.

TL;DR

• The first question is jurisdiction, not licensing. Commerce (BIS) under the EAR, or State (DDTC) under the ITAR. The answer changes the license regime, the penalty statute, and which employees may touch the technical data.
• Commodity Jurisdiction is the formal way to ask. 22 C.F.R. § 120.4 says the CJ procedure is used "if doubt exists" about whether an article or service is covered by the US Munitions List. § 120.12 sets the request procedure.
• 5,903 CJ determinations, 2010 to present, is a decade-plus of published answers to that exact question, and DDTC publishes it itself as a spreadsheet export.
• BIS Advisory Opinions are a small, honest archive, not a live feed. 33 documents covering 2003 to 2023. BIS's own advisory opinions page runs from May 2003 to September 2023 (checked August 2026). Do not build a monitor on it.
• Versioning is the amendment record, not a date parameter. A citation resolves to one text, the one in force now. Around it sit amendment history, a yearFrom/yearTo currency filter, and change events per refresh.
• Results carry the publisher's own source URL where the publisher exposes one. The sourcing rule is the government publisher, never a commercial aggregator.

The trade-controls entry in our federal agency guidance series.

For related coverage, see Federal Agency Guidance API: 34 Sub-Regulatory Sources in One Endpoint, DOJ Justice Manual API: 1,548 Sections of Federal Prosecution Policy for how these cases get charged, and The Long-Tail Regulators: CFTC, FCC, FERC, DOE, and CPSC Guidance in One API.

The question that decides everything

A trade compliance team does not start with "which license do I need." It starts with which agency owns my item.

If the item is on the US Munitions List, it is ITAR controlled and DDTC at the State Department owns it. If it is not, it is almost certainly subject to the EAR and BIS at Commerce owns it. Two different rulebooks, two different penalty statutes, two different answers to whether a green card holder on your team may read the design file.

Get that wrong at the start and every downstream control is wrong too. You will have built an export compliance program around the wrong regulation.

All C.F.R. citations above were checked against eCFR in August 2026.

Commodity Jurisdiction is the mechanism, and it is written down

The ITAR does not leave the jurisdiction question to vibes. It gives you a procedure.

22 C.F.R. § 120.4(a) says the commodity jurisdiction procedure is used with the US Government if doubt exists as to whether an article or service is covered by the USML, and that it may also be used to ask for redesignation of something already on the list. § 120.4(b) points to § 120.12 for how to file. § 120.11 sets the order of review, the sequence you are supposed to walk before you conclude anything.

The EAR has a parallel move on its side. 15 C.F.R. § 748.3 lets you ask BIS for a classification (an ECCN down to the paragraph) or, for a broader interpretive question, an advisory opinion under § 748.3(c). The regulation is blunt about the boundary: people requesting classifications and advisory opinions "should have determined that the items at issue are not subject to the exclusive export control jurisdiction of one of the other U.S. Government agencies."

Translation: BIS will not settle an ITAR question for you. DDTC will. That is what CJ is for.

Why 5,903 CJ determinations is an unusual dataset

Most agency guidance corpora are thin because agencies publish sparingly. The CJ set is the opposite.

DDTC publishes its determinations as a spreadsheet export, and the corpus holds 5,903 of them covering 2010 to the present. Each one is a real company asking about a real item and the government writing down which side of the line it fell on.

That gives you something no treatise gives you: a base rate. Not "here is how the order of review works" but "here is what happened the last several hundred times somebody asked about a component of this kind."

Three ways compliance teams actually use it:

• Precedent search before you file. Before spending months on a CJ request, search the set for items described the way yours is. If forty similar determinations came back one way, you have a strong prior and a much better drafted request.
• Sanity check on an outside opinion. Counsel says the bracket is EAR99. The published determinations on similar brackets are a cheap second read.
• Watching the ITAR to EAR migration. The 600 series ECCNs exist because items moved off the USML. 15 C.F.R. § 738.2 assigns the 600 to 699 range to Wassenaar Munitions List or former USML items controlled for national security and other reasons. CJ determinations are where that migration shows up item by item.

BIS Advisory Opinions: small, real, and closed at 2023

The corpus holds 33 BIS advisory opinions covering 2003 to 2023. That is small, and the smallness is the point worth understanding.

BIS does not publish every advisory opinion it issues. Its own page says it has "selected certain advisory opinions that may be of general interest to the public," and that some are redacted to avoid releasing identifying information protected under Section 1761(h) of the Export Control Reform Act of 2018. What is published runs from May 2003 to September 2023 (BIS advisory opinions page, checked August 2026).

Citation form is the first thing developers get wrong here. BIS advisory opinions have no serial number. They are identified by issue date and subject line, and that is how they appear in the corpus.

Two real entries from the published list, as an illustration of shape:

• 09/25/23, export guidance and BIS interpretation of "gene" related to ECCN 1C353.
• 06/09/23, additional deemed export authorization not required for release of licensed technology and software to permanent and regular employees, as defined in 15 C.F.R. § 734.20(d)(2), in the United States.

That second one is exactly the "who can I hire" question in its EAR form. Under 15 C.F.R. § 734.15, releasing controlled technology to a foreign person is a release, and § 734.13 makes that release an export. On the ITAR side the parallel definitions are 22 C.F.R. § 120.63 (foreign person) and § 120.64 (regular employee). Same hiring decision, two different rulebooks, and which one applies is decided by the jurisdiction question.

DDTC Guidance: 7 documents, high value per document

ddtc_guidance is 7 documents. Small count, but these are the operational documents, including the Guidelines for Preparing Agreements and the ITAR Risk Matrix.

The Guidelines matter to anyone drafting a Technical Assistance Agreement or Manufacturing License Agreement, because DDTC tells you what it expects in the clauses before you submit. The Risk Matrix matters to compliance programs that need a defensible way to grade exposure.

Seven documents is not a corpus you search. It is a corpus you retrieve whole and keep in context. Fetch them by actId and cache them.

The three source codes, and how to query them

All three live under corpusType=AGENCY_GUIDANCE, filterable with source=. The corpus types reference lists every token.

A precedent search against the CJ set. Search costs 4 credits per call, and you can run it in the API playground first.

curl -X POST https://api.vaquill.ai/api/v1/us/statutes/search \
  -H "Authorization: Bearer vq_key_..." \
  -H "Content-Type: application/json" \
  -d '{
    "query": "inertial measurement unit accelerometer bias stability",
    "corpusType": "AGENCY_GUIDANCE",
    "source": "ddtc_commodity_jurisdiction",
    "limit": 25
  }'

Widen it to both agencies in one call by passing a list:

{
  "query": "specially designed part for a commercial derivative aircraft",
  "corpusType": "AGENCY_GUIDANCE",
  "source": ["ddtc_commodity_jurisdiction", "bis_advisory_opinion"],
  "matchType": "any",
  "limit": 50
}

Three API behaviors that matter when you are automating this:

• actId is stable and not guessable. Take it from the search response and use it for retrieval. Hand built ids mostly 404.
• Unknown filter values return 422, not an empty result set. A typo in a source code fails loudly, and the error message lists every valid code.
• Paging is cut from one ranking. Results do not repeat or vanish between pages, and page five costs the same as page one.

A worked ECCN to guidance chain

Take a real chain end to end, using only citations you can check.

Step 1. Learn what an ECCN encodes. 15 C.F.R. § 738.2 defines the structure. The CCL has 10 categories, 0 through 9. Category 3 is Electronics, 5 is Telecommunications and Information Security, 9 is Aerospace and Propulsion. Within each category, five groups: A equipment, B test and production equipment, C materials, D software, E technology.

So in 3A001, the 3 is Electronics and the A is equipment. The last three digits carry the reason for control. Per § 738.2(d)(1), 000 to 099 is National Security, 100 to 199 is Missile Technology, and 600 to 699 is Wassenaar Munitions List or former USML items.

Step 2. Pull the regulation text. The structural rules and the entries themselves are in the CFR corpus, which refreshes daily.

{
  "query": "Commerce Control List structure categories groups ECCN",
  "corpusType": "CFR",
  "titleNumber": "15",
  "part": "738",
  "limit": 5
}

Step 3. Ask whether anyone else already asked. Search bis_advisory_opinion for the ECCN. The published set includes opinions on the scope of ECCN 1C353, ECCN 5E001.b.3, and ECCN 2B350, among others, so an ECCN string is a genuinely useful query term here.

Step 4. If doubt exists about the USML, that is a CJ question, not a BIS question. Search ddtc_commodity_jurisdiction for the article description, then read 22 C.F.R. § 120.4 and § 120.12 from the CFR corpus in the same session.

Step 5. Cross the line into hiring. If the answer is EAR, the release rules are 15 C.F.R. §§ 734.13 and 734.15. If it is ITAR, they are the 22 C.F.R. Part 120 definitions. Pull both by citation and put them in front of whoever writes the access policy.

Where the answer lives outside this corpus

Say the limits plainly, because a compliance team that discovers them after integration has a real problem.

• No point in time query. Ask for a citation and you get its live text, one version, with no as_of=DATE to reach an older one. What exists is amendment history with lastAmendedYear, a yearFrom/yearTo currency filter, change events per refresh, and per section diffs on watched boards, explained in full here. If you need to prove what 22 C.F.R. § 121.1 said on a date three years ago, this is not that system.
• The CJ set is a published extract, not a case tracker. It reflects what DDTC exports. It will not tell you about a pending request.
• BIS advisory opinions stop at 2023 and are a selected, partly redacted subset by BIS's own description.
• Nothing here is legal advice or a determination about your item. It is the government's published record, retrievable by citation with the publisher's own source URL attached.

Who this is wrong for

If you need a docket tracker for pending CJ requests, this is the wrong tool. If you need historical versions of the USML to reconstruct a compliance posture from 2019, this is the wrong tool. If your whole need is "read today's 22 C.F.R. Part 121," the eCFR website is free and you should just use it.

It earns its place when you need the regulations, the determinations, and the guidance in one query surface with stable ids, so an internal tool or an agent can move between them without a human copying citations across four websites. Defense suppliers usually want the FAR and DFARS clause corpus sitting beside it.

The collection layer behind it is published at open-us-law, so the sourcing is readable rather than asserted.

FAQ

What is the difference between EAR and ITAR jurisdiction?

The ITAR (22 C.F.R. Parts 120 to 130) covers defense articles and services on the US Munitions List and is administered by DDTC at the State Department. The EAR (15 C.F.R. Parts 730 to 774) covers dual use and other items and is administered by BIS at Commerce. The two regimes have different license rules, different penalty provisions, and different rules on releasing technical data to foreign persons.

What is a Commodity Jurisdiction determination?

It is DDTC's formal answer to whether a specific article or service is covered by the US Munitions List. 22 C.F.R. § 120.4 says the procedure is used when doubt exists about USML coverage, and § 120.12 sets out how to submit the request. It can also be used to ask for redesignation of something already on the list.

How many CJ determinations can I query?

The corpus holds 5,903 determinations covering 2010 to the present, taken from DDTC's own XLSX export and filterable with source=ddtc_commodity_jurisdiction under corpusType=AGENCY_GUIDANCE.

Are BIS advisory opinions binding?

No. A BIS advisory opinion is BIS's written view on how the EAR applies to a described fact pattern. 15 C.F.R. § 748.3(a) is explicit that responses about whether a license is required or likely to be granted do not bind BIS to issuing a license later. Treat them as strong interpretive guidance, not as authorizations.

Why does the BIS advisory opinion set stop at 2023?

Because that is where BIS's own published selection currently ends. BIS publishes selected opinions of general public interest, some redacted under Section 1761(h) of the Export Control Reform Act of 2018, and the published list runs from May 2003 to September 2023 as of August 2026. The corpus reflects the publisher rather than filling the gap from somewhere else.

How do I cite a BIS advisory opinion?

By issue date and subject, because BIS does not assign serial numbers to them. For example, the 09/25/23 opinion on export guidance and BIS interpretation of "gene" related to ECCN 1C353. In the API, retrieve by the actId returned in a search response rather than by constructing an identifier.

Can I query historical versions of the USML or the CCL?

Versioning here runs off the amendment record rather than a date parameter. Each citation carries the text in force now and nothing behind it, because no as_of=DATE parameter exists. What is available is amendment history per section, a yearFrom/yearTo currency filter that keys on the last amendment year the publisher credits, change events captured on each refresh, and per section diffs on watched boards.

What does an ECCN like 3A001 actually mean?

Under 15 C.F.R. § 738.2, the first digit is the CCL category (3 is Electronics), the letter is the product group (A is equipment, assemblies and components), and the last three digits identify the reason for control. The 600 to 699 range marks Wassenaar Munitions List or former USML items, which is where ITAR to EAR transitions land.

Where does the export control data come from?

DDTC's own published XLSX export for the CJ determinations, BIS's own advisory opinions page for the EAR opinions, DDTC's published guidance documents, and eCFR for 15 C.F.R. and 22 C.F.R. Every result carries the publisher's source URL, and no commercial aggregator is used as a source or a fallback.

Priyansh Khodiyar

Co-Founder & CTO

Priyansh leads engineering and AI at Vaquill, from the matter workbench to drafting, document comparison, document matrix, and citation-verified research.