Laki.ai Developer Addendum

Version 1 – 6 October 2026

1.Agreement and scope

1. 1.1.
   This Developer Addendum applies when the Customer's authorised representative accepts it for a Developer Subscription or the parties expressly incorporate it into an Order Document. It permits the Customer to integrate the documented Laki.ai headless API into a product it develops and operates (the Product) for the Product's users (End Users).
2. 1.2.
   The Agreement includes this Addendum, the accepted Subscription or Order Document, the Organization Customer Terms, version 4 of 3 September 2026 (Organization Terms), and the DPA, version 3 of 1 September 2026. Acceptance adopts version 4 for the Customer's Agreement and replaces version 3 where previously applicable, including without a Microsoft Copilot purchase. This expressly supplements sections 1.2 and 1.6 of the Organization Terms. A Team role alone does not establish authority to accept.
3. 1.3.
   The DPA prevails in conflicts concerning personal data processing. For other conflicts, an Order Document prevails to the extent it expressly agrees a deviation, followed by this Addendum for Developer use and then the Organization Terms. Otherwise the Organization Terms, including confidentiality, liability, governing law and disputes, apply. Existing negotiated integration agreements are amended only by express agreement; access to shared management functions does not amend them.

2.Integration and output rights

1. 2.1.
   During the Subscription, the Customer may integrate the API into the Product and provide its functionality to End Users. This includes developing, testing, evaluating and operating the integration, including a legal-research or AI Product with functionality overlapping Laki.ai. These permissions replace the internal-use restriction in section 2.3 and the restrictions in section 2.4(c)–(d) of the Organization Terms to the extent necessary for the permitted integration.
2. 2.2.
   The Product uses the Customer's organization API keys from its backend. End Users need no Laki.ai account, Team membership or paid seat. This permitted use of backend keys is an exception to sections 2.3, 2.4(a) and 5.1 of the Organization Terms. People managing the organization retain personal management accounts. The Subscription grants no paid personal, ChatGPT, Claude or Microsoft access.
3. 2.3.
   To the extent the Service Provider can grant the rights, the Customer may use, modify, store, copy, display and supply outputs within the Product and allow End Users to use and retain them for their own purposes. These rights in outputs lawfully obtained during the Subscription continue after it ends. Source material and third-party rights remain subject to their applicable terms. This supplements section 4.2 and the work-product limitation following section 2.4 of the Organization Terms.
4. 2.4.
   The Customer may not disclose API keys to End Users, sell standalone access to Laki.ai's API, or use the Service or outputs to train or fine-tune AI models or systematically extract or reconstruct Laki.ai's corpus or service. Ordinary integration testing and evaluation under section 2.1 remain permitted. Other restrictions in section 2.4 of the Organization Terms continue to apply, including security and lawful-use restrictions.
5. 2.5.
   The Customer may accurately describe the integration but may not imply endorsement or a partnership or present the Product as a Laki.ai-operated service or a substitute for a qualified legal professional. The public-sector and adjudicative-use restrictions in section 2.5 of the Organization Terms also apply to use through the Product.

3.Customer and End User responsibilities

1. 3.1.
   The Customer is responsible for the Product, its End User relationship, access controls, notices and lawful use of the integration. It must require End Users to comply with the use restrictions applicable to them and take reasonable steps to address known misuse. End Users do not become parties to this Agreement merely by using the Product.
2. 3.2.
   The Customer must require End Users to check material information against original sources with qualified human judgement before relying on it. The Product must clearly communicate that requirement and that outputs are AI-assisted and may be incorrect, incomplete or outdated, and make the returned source references available. Permitted automated delivery does not require the Customer to review every output before displaying it; this replaces the review-before-incorporation requirement following section 2.4 of the Organization Terms. The Customer's own verification duty under section 2.1 remains when it relies on an output. The Customer must not misrepresent a generated output as an official source or remove source notices required by the applicable source terms.
3. 3.3.
   The Customer must protect backend keys, limit access to authorised personnel and systems, revoke compromised or unnecessary keys promptly, and report suspected compromise to the Service Provider. A key without an expiry remains the Customer's responsibility until revoked or access otherwise ends.

4.Research data

1. 4.1.
   Sections 3 and 7 of the Organization Terms and the DPA apply to research inputs and outputs sent through the Product. Customer-authorised API requests constitute documented processing instructions under the DPA. The Customer must ensure that it may submit the data, including having any required upstream controller authorisation where it acts as processor. The permitted and prohibited data categories remain those in the Organization Terms and DPA.
2. 4.2.
   The Service Provider processes research inputs and outputs to perform the requested operations and does not retain them as a research history or use them for model training or general improvement. Content-free operational metadata may be retained as described in the Organization Terms. The Customer is responsible for any lawful storage of research inputs or outputs by the Product and its selected service providers; that storage is separate from Laki.ai's processing. End User identifiers are optional for this Subscription and do not determine its price.

5.Price, payment and cancellation

1. 5.1.
   The accepted offer states the fixed monthly price in euros and whether VAT is included or added. It is one organization Subscription: changes in Team membership or End User numbers do not change the charge, and there are no per-call or usage-overage charges. Organization Capacity, seat adjustments and automatic cancellation of personal subscriptions under sections 5.2–5.4 of the Organization Terms do not apply. The accepted tax treatment replaces the default VAT-inclusive treatment in section 5.2.
2. 5.2.
   The Subscription is charged in advance by card through Stripe and renews monthly. The Customer can manage its payment method and invoices through the billing portal. Its purchased commercial terms remain applicable unless changed under section 6.4 of the Organization Terms; changing or withdrawing an unpurchased offer does not change an existing Subscription. During payment recovery, existing keys may continue working while new key creation is unavailable. Access ends if entitlement lapses, subject to mandatory rights and section 7.
3. 5.3.
   An authorised owner or administrator may cancel renewal through organization billing or the billing portal without contacting support. Ordinary cancellation takes effect at the end of the paid period, with API access continuing until then and no automatic partial-period refund. Section 7 governs switching and retrieval; mandatory termination and refund rights remain unaffected. An Order Document may expressly provide different billing and termination terms, subject to mandatory law.

6.Fair use and support

1. 6.1.
   The fixed fee is subject to fair use and documented technical limits. The Customer must respect rate-limit responses and avoid traffic that threatens service security or availability. Limits apply across the organization's keys. A limit does not create an overage charge. Material adverse changes are governed by section 6.4 of the Organization Terms; urgent restrictions remain subject to its section 6.1.
2. 6.2.
   Integration documentation and support are available through Laki.ai's developer documentation and info@laki.ai. The Customer supports its End Users. Unless an Order Document expressly agrees otherwise, no dedicated response time, service level or custom integration work is included; section 8 of the Organization Terms applies.

7.Switching, retrieval and deletion

1. 7.1.
   The Customer may switch to another provider or its own infrastructure, or request erasure. Routine export and cancellation are self-service. For a coordinated switch, the Customer may contact info@laki.ai and identify the destination or erasure choice. The transition starts on receipt of the request or a later date requested by the Customer; no additional notice period is required. The Service Provider provides reasonable switching assistance, relevant information about known continuity risks, and maintains the agreed functions, continuity and security during the transition, including beyond a scheduled paid-period end. The parties cooperate in good faith.
2. 7.2.
   The transition is completed without undue delay and within 30 calendar days after it starts, subject to the following extensions. If that is technically infeasible, the Service Provider explains the reasons within 14 working days of the request and specifies an alternative transition no longer than seven months. The Customer may extend the transition once for a period appropriate to its purposes. The Agreement ends for the Developer Subscription on successful completion of switching. If the Customer chooses erasure instead, it ends on receipt of that request or a later date requested by the Customer. The Service Provider confirms termination to the Customer. Other separately purchased services are unaffected. These rules override sections 5.5 and 6.3 of the Organization Terms where necessary.
3. 7.3.
   The Customer can download a structured, commonly used, machine-readable export of its organization profile and legal details, memberships, accepted agreements and commercial terms, subscription details, API-key metadata and retained customer-related usage metadata. There are no retained research histories to export. Credentials, secret hashes, other customers' data and the Service Provider's protected internal diagnostics, provider-cost data, software and corpus are excluded; exclusions do not obstruct or delay switching. Rights to source material available independently of the Subscription are unaffected. The Developer export documentation provides an up-to-date online register of data structures, formats and relevant standards, together with interface information and known technical limitations. The Service Provider also supplies any other exportable data or digital assets required by applicable law.
4. 7.4.
   API expiry does not itself remove access to organization management or export. After a completed switch or ordinary termination, the Customer has 30 calendar days, or a longer agreed period, to retrieve its exportable data. The Service Provider then erases the exportable data and digital assets of the ended Developer service, provided switching has successfully completed where applicable, or erases them earlier on the Customer's express instruction, subject to the DPA and storage required by law. Shared organization records needed for the Customer's continuing services and billing or agreement records required by law are retained only for those purposes and their applicable retention periods. A request to delete the organization must clearly identify any earlier erasure instruction; ordinary cancellation is not such an instruction. This replaces conflicting effects of organization deletion under section 5.6 of the Organization Terms.
5. 7.5.
   There are no switching, export or exit fees or early-termination penalties. During a switching transition, the purchased monthly price and billing cycle continue to apply, including where the transition extends beyond the current paid period. Amounts already paid cover the corresponding service period without duplicate charges. Termination under section 7.2 stops further renewals; a monthly period that has begun is not automatically prorated or refunded. Billing does not extend the termination date or make payment for a new period a condition of completing the switch. This section does not reduce mandatory switching, interoperability, data-protection, termination or refund rights.