Developer API Terms

1. About these terms

1.1 These Developer API Terms (the "API Terms") apply when you use the Taxxa Developer API (the "API"). "We" and "Taxxa AI" mean Taxxa AI and its Affiliates. "You" means the Subscriber whose workspace has API access.

1.2 The API Terms add to the Terms and Conditions (the "GTCs"). The API is part of the Services. Words with capital letters that the API Terms do not define have the meaning that the GTCs give them.

1.3 The Developer API Acceptable Use Policy and the Developer API Data Processing Addendum are part of the API Terms.

1.4 If the API Terms and the GTCs do not agree about the API, the API Terms apply. If an Offer document for the API does not agree with the API Terms, the Offer document applies.

2. Access and API keys

2.1 We turn on API access for a workspace after we agree on it with you in an Offer document.

2.2 Workspace admins create and revoke API keys in Taxxa under Control Room > API. Each key belongs to one workspace.

2.3 API keys are secrets. Keep them on your servers. Do not put a key in browser code, mobile apps, public code repositories or logs. Do not share a key with another organization.

2.4 You are responsible for all calls made with your keys, and for the fees of those calls, until you revoke the key.

2.5 If you think that a key is exposed, revoke it at once and tell us at contact@taxxa.ai. A revoked key stops working within two minutes.

2.6 We can block or revoke a key if it is exposed, if it is used against the API Terms, or if it puts the Services at risk. We tell you when we do this, unless the law or a security risk prevents it.

3. What you can do with the API

3.1 We give you a limited, non-exclusive, non-transferable and revocable right, for the Term, to call the API and to use its results in your own products and services for your end users. For API results, this right replaces the limit to internal business operations in clause 8.2.1 of the GTCs.

3.2 Clause 2.3.1 (v) of the GTCs does not prevent calls to the API with a valid key. All other use limits of the GTCs and the Acceptable Use Policy apply.

3.3 You must not resell or sublicense access to the API itself, for example as a search API or an answer API for other developers.

3.4 Your end users do not get rights against us. You are responsible for your products, for your terms with your end users, and for how your end users use API results.

4. What the API does

4.1 The API searches the Taxxa public knowledge base and answers questions from it. The endpoints are /v1/search, /v1/chat/completions (models taxxa-fast and taxxa-thinking), /v1/countries, /v1/facets and /v1/models. The API documentation describes them.

4.2 Answers use only the public knowledge base, with citations to official sources. Answers do not use web search, workspace documents or other data in your workspace.

4.3 We can add endpoints, fields and models. Inside version v1 we do not remove or rename fields. We tell you at least 90 days before we remove an endpoint, a model or a version, unless a law, a security risk or a change by a supplier makes this impossible.

5. Prices and billing

5.1 The API prices are in euros and do not include VAT:

5.2 An answer costs the request price plus its input and output tokens. Calls to /v1/countries, /v1/facets and /v1/models are free. A request that fails with an error is not billed. If a request stops before it completes, for example because your client closes the connection, you pay for the tokens that the models used until it stopped.

5.3 We measure usage and bill it each month in arrears. The Offer document can add other fees, for example a development fee.

5.4 Our usage records decide the amount that we bill, unless you show that they are wrong. Workspace admins can see usage in Control Room > API.

5.5 Each workspace has a monthly spend cap. The default cap is €500. Workspace admins can change the cap in Control Room > API. When the workspace reaches its cap, the API refuses new billable requests until the next calendar month (UTC) or until an admin raises the cap. Requests that are open when the workspace reaches the cap can complete, so the amount for a month can be a little higher than the cap. You must pay for that usage.

5.6 The payment terms in clause 3.2 of the GTCs apply. If an invoice stays unpaid after the payment retries end, we can suspend API access until you pay. A suspension does not change the fees that are due.

5.7 We can change the API prices. We tell you at least 30 days before a change. The new prices apply from the first full billing month after the notice ends.

6. Limits

6.1 The current limits are:

• 60 requests a minute for each API key.
• 300 requests a minute for each workspace, for all its keys.
• 15 requests open at the same time for each workspace.

6.2 When you reach a limit, the API returns status 429 with a Retry-After header. The API documentation shows the current limits.

6.3 We can change the limits to protect the Services. If we lower a limit for all customers, we tell you at least 30 days before, unless an attack or a security risk makes a faster change necessary. You can ask us for higher limits at contact@taxxa.ai.

7. Availability and support

7.1 Clause 2.1.2 of the GTCs applies to the API. We do not give a service level agreement (SLA) or service credits for the API, unless the Offer document gives them.

7.2 For support, write to contact@taxxa.ai. Include the request id and the time of the call if you have them.

8. AI output

8.1 Search results and answers come from automated systems. They can be wrong, incomplete or out of date, also when they show citations. Laws, guidance and rates change.

8.2 API results are not legal, tax, accounting or financial advice. Clause 6.1 of the GTCs applies to all API results.

8.3 When you show an answer to an end user, you must:

• Show the citations of the answer with it, as links to the sources.
• Tell the end user that the answer comes from AI and can be wrong.
• Not show the answer as advice from Taxxa AI or from a professional, unless a qualified person has reviewed it.

8.4 You are responsible for the decisions that you and your end users make with API results.

9. Knowledge base content

9.1 The knowledge base contains texts from official sources, for example laws, tax authority guidance, court decisions and collective agreements. We add structure, passages, metadata and citations to these texts.

9.2 Some source texts are free to use by law. Other source texts have rights of their publishers. The API Terms do not give you more rights in a source text than the law or its publisher gives.

9.3 Taxxa AI and its licensors own the rights in the knowledge base as a collection, including its selection, structure, passages, metadata and search index.

9.4 You can show search results, quotes and answers to your end users in your products, with their citations. You can keep them in the records of your product, for example in the history of an end user.

9.5 You must not:

• Copy the knowledge base or a substantial part of it.
• Make a dataset, index or service that replaces the knowledge base.
• Sell or license knowledge base content in bulk.
• Use API results to train or fine-tune AI models, unless we agree to it in writing.

9.6 If we must remove a text from the knowledge base for a legal reason, we can ask you to stop using the copies of it that you keep. You must then do so without undue delay.

10. Data

10.1 The API keeps no queries, messages, search results or answers after it responds. We keep usage records: counts, tokens, amounts, model, status, API key id and request id.

10.2 Send personal data in queries and messages only when you need to. When you do, we process it as your processor under the Developer API Data Processing Addendum.

10.3 We do not use API queries, messages or answers to train AI models.

11. Suspension

11.1 We can suspend an API key or the API access of a workspace at once, without the notice in clause 2.3.2 of the GTCs, if:

• A key is exposed.
• The use puts the Services, other customers or the knowledge base at immediate risk.
• The use breaks section 2 or section 4 of the Acceptable Use Policy.
• The law requires it.

11.2 We tell you as soon as possible and we turn access on again when the reason ends. For other breaches, clause 2.3.2 of the GTCs applies.

12. Term and termination

12.1 The API Terms apply while your workspace has API access.

12.2 You can stop API access at any time. Revoke your keys and ask us to turn off API access. You pay for the usage until access stops. The Offer document can set a minimum term or fees that we do not refund.

12.3 We can stop API access with 30 days' written notice. We can stop it at once for cause, as clause 4.2 of the GTCs describes.

12.4 When API access stops, all keys of the workspace stop working and we invoice the usage that is not invoiced yet. Sections 9.5, 9.6, 12.4 and 13 continue to apply.

12.5 When API access stops, the other Services continue, unless the Offer document or the GTCs say otherwise.

13. Liability

13.1 Clause 6.3 of the GTCs applies to the API. The fees in clause 6.3.2 of the GTCs include the API fees that you paid or owe.

13.2 We are not liable for your products, or for how your end users use API results.

13.3 Clause 5.2 of the GTCs also covers claims from your end users and other third parties about your products that use API results, unless the claim comes from our breach of the API Terms.

14. Changes, law and disputes

14.1 We can change the API Terms as clause 10.10 of the GTCs describes. We tell workspace admins by email about a material change.

14.2 Clause 11 of the GTCs applies to the API Terms: Finnish law, and arbitration by the Finland Arbitration Institute (FAI) in Helsinki, in English.