Classification flow (skill + human review)

The classification skill collects item information, fetches regulatory data, proposes jurisdiction and ECCN, and asks you to confirm. The report is built from a template with no data stored via the API.

Steps

1. Collect item info — The skill asks for item details (description, specs, end use, destination, etc.). You can provide a source document (file or paste) or pull from your CRM if you use integrations (see Integrations).
2. Get regulatory data — The skill optionally calls GET https://api.exchek.us/api/ecfr/774 and /api/ecfr/121 to retrieve Part 774 (CCL) and Part 121 (USML) structure. If the API returns 503, it can use the eCFR developer API (title-15.json, title-22.json) and extract the relevant parts.
3. Classify — Using the classification system prompt and Order of Review, the AI determines jurisdiction (BIS vs ITAR) and proposes an ECCN. It presents jurisdiction and rationale and asks you to confirm before proceeding. Then it presents the proposed ECCN and justification and asks you to approve (or give feedback to refine).
4. Build the report — After you approve, the AI fills the report template (item info, jurisdiction, ECCN, justification, export restrictions, license requirements, audit log, citations) and outputs the classification memorandum. It does not call any API to generate or store the report.
5. Push to CRM (optional) — Optionally push ECCN and jurisdiction to your CRM. See Integrations.
6. Suggest donation — The skill may suggest an optional donation. See Funding / donation.

All classification and report generation happen in-skill. The only API calls are the optional snapshot endpoints for 774/121 data. Human oversight is required for jurisdiction confirmation and final ECCN approval.