FreightParse HS Code API Terms
Version 1.2, 2 November 2026. In force from 2 November 2026.
These API Terms add the terms of the HS code API at freightparse.com/api/ to the FreightParse Licence Terms (version 2.2, 2 November 2026, freightparse.com/legal/licence-terms.html) and the Code Services Addendum (version 1.1, 2 November 2026, freightparse.com/legal/code-services.html). Both apply to the API in full and are not repeated here. These API Terms rank below them: where they differ, the Addendum and the Licence Terms prevail. In these API Terms the Customer is the business the key is made for, and we and us are as in the Licence Terms.
H1. What the API does. For a product description the Customer sends, the API suggests the 6-digit HS code and the 8-digit EU CN code, with the official text of the tariff lines. It flags a description that leaves out what decides the code, and may ask one or two questions about it. Every code is a suggestion, not a ruling. The Customer decides which code it files or passes on, and is responsible for the code on its declaration (Addendum T3 and T4; Licence Terms clause 7.3).
H2. Keys and limits.
- We make one key for each customer, on request to danil@freightparse.com or through the checkout on freightparse.com/api/, which sends the key by e-mail to the address given there, and give it with links to the Licence Terms, the Addendum and these API Terms. The agreement for the API is formed when the Customer first uses the key (Addendum T1).
- The Customer keeps the key secret, on its own server and never in a web page, an app or public code, and tells us at once if it leaks. We then revoke it and make a new one. Every product sent with the key is counted for the Customer.
- Each plan has limits on the products a key can send in a minute, a day and a month (H3). A request over a limit is refused with status 429 and counts nothing.
- We may suspend a key that is abused, for example by flooding the API, getting round a limit, sharing the key with another company or sending personal data, or whose invoice is unpaid 14 days after a written reminder (the period in Licence Terms clause 6.6). A suspended key is refused with status 403. We tell the Customer by e-mail when we suspend a key and why, and the Customer can ask us to resume it once the cause is put right.
H3. Plans, limits and prices. All prices are in euro and exclude VAT (Licence Terms clause 6.1). Products are counted for each key, and days and months are UTC.
| Plan | Products a minute, a day and a month | Price |
|---|---|---|
| Free | 30, 200 and 500 | Nothing. The key stops at 500 products a month. |
| Standard | 60, 1,000 and 10,000, unless agreed otherwise | The first 500 products of a month are free. The 501st to the 1,000th cost EUR 0.25 each, and every product from the 1,001st costs EUR 0.15. |
| Platform, by written agreement | As agreed in writing | The first 500 products of a month are free. Above 500, EUR 0.05 for each product, with a minimum of EUR 49 for a month in which the key passes 500 products. |
- The standard prices are the ones published on freightparse.com/api/. A key moves to another plan when the Customer asks in writing and we confirm by e-mail.
- A product is one description that the API answers after asking the language model: with a code, with "no line of the tariff fits" or with "no word of it is in the tariff". The answer shows the count as
units. The same description sent in two requests counts twice, because nothing is kept between requests. - Nothing is counted for a request we refuse before the model (a bad request, a limit, a busy API); for a description we could not answer, or that a batch had no time to run, which the Customer sends again; for a copy of a product already in the same batch (the same description, material and use, whatever the capitals, accents and spaces); or for an answer to one of our questions that the tariff settles by itself. An answer to one of our questions that needs the model again counts one product.
H4. Billing. We invoice each month after it ends, for the products counted in it, and the Customer pays within 14 days of the invoice date (Addendum T9; Licence Terms clause 14A.3 says the same for the monthly plan). A month of no more than 500 products is not invoiced. The count is the one in our usage file. An objection under Licence Terms clause 6.3 names the request_id of the requests concerned.
For a key bought through the checkout, the plan runs from month to month until it is cancelled. After each month we charge the payment method given in the checkout for the products counted in it, and send the invoice by e-mail; a month of no more than 500 products is not charged. The Customer can cancel at any time through the link in the key's e-mail or by writing to us: the key then moves to the free plan, and the products of that month are charged after it ends. If a payment fails, the key moves to the free plan until the invoice is paid.
H5. Data.
- The Customer sends only descriptions and codes: the description of each product, with its material and use if it chooses, the codes of its answers to our questions and, if it chooses, its own item ids. No prices, no names, no addresses and no other personal data (Addendum T6, under Licence Terms clause 10.4).
- Each description, with its material and use if sent, goes to our server in the EU and from there to Google's Gemini model on Vertex AI, in Google's EU multi-region. Under Google's terms the data is not used to train its models. A request flagged by Google's automatic abuse checks may be kept for up to 90 days, in the EU (Addendum T7).
- Nothing is kept between requests: no description, code or answer (Addendum T8). The records we keep of the API's use are only these:
| Record | What it holds | How long |
|---|---|---|
| Service log, in the server's system journal | For each request: the status, the route, the time taken, the request id, the key's id, the numbers of products, units, failures and model calls, the tokens used, and a short outcome or error code. Never a description, a code, an answer, an item id, the key or an address. | Until the journal needs the space: about 30 days on 8 October 2026. |
| Web server log for the API | The time, the request id, the method, the path without its query string, the status, the sizes and the times. No address and no header, so never the key. The web server's error log can record the address of a computer whose request failed. | 14 days. |
| Usage file | For each request that counted products: the time, the key's id, the route, the number of products and the request id. | At least seven years, as Dutch tax law requires for the records behind an invoice. |
| Key file | The key's id, the Customer's name, the limits, the plan and when it changed, the status, the date made, a short note of ours and a hash of the key. | Until the key ends (H8). |
H6. Availability. We run the API on a best-effort basis, with no service level: no promise of uptime, speed or response time (Licence Terms clause 8.4). A request that fails counts nothing, and the Customer sends it again. The EU changes the Combined Nomenclature on 1 January every year, and the API answers with the edition we have loaded. We aim to load each new edition for 1 January but do not promise it. The Customer checks its stored codes again after each 1 January.
H7. Liability, law and court. Liability is as in Code Services Addendum T5 and Licence Terms clause 9: the cap, the loss we do not cover, and the products given free of charge. Dutch law applies and the court in Rotterdam decides (Licence Terms clause 17). These API Terms change none of that.
H8. Changes and ending. We announce a change of the prices by e-mail at least 30 days before it applies, as Licence Terms clause 14A.2 does for the monthly plan, and the Customer can stop before then. Either side can end the HS code API at any time by e-mail, from the day it is sent or a later day it names. We then revoke the key. The Customer pays for the products counted until then.