# Kelki Agent API terms of use Translation. This is an English translation provided for convenience. The French version prevails: [Conditions d'utilisation de l'API](https://kelki.ai/developers/fr/terms/). Version of 12 November 2026. These terms apply to any business that integrates the Kelki Agent API into its application or service. They form a whole with the [data processing agreement](https://kelki.ai/developers/en/terms/data-processing/) and the [acceptable use policy](https://kelki.ai/developers/en/terms/acceptable-use/). In short. The API is free for you. It serves one purpose only: letting your users ask to be called back by a professional of the right trade, near them. Nothing is sent without the person's consent, and every real Request is confirmed by the person themselves, through an e-mail from Kelki. You receive no contact details in clear and Kelki sells you no data. ## 1. Parties and definitions Kelki means D.DESIGN & CONSEIL, a French simplified joint-stock company (société par actions simplifiée, SAS), registered office 4 rue de Bellefond, 75009 Paris, registered with the Paris Trade and Companies Register (RCS) under number 794 023 564 (SIRET 794 023 564 00022, intra-EU VAT number FR91 794 023 564), publisher of the Kelki service. Contact: [contact@kelki.ai](mailto:contact@kelki.ai). The Partner means the legal entity (or sole trader) that opens a developer account and uses the API for its professional activity. These terms are not addressed to consumers. - API: the Kelki Agent programming interface, its documentation, its sandbox, the developer space and the webhooks. - Person: the Partner's user who describes a need and asks to be called back. - Request: a Person's call-back request (trade, service, timing, place, contact details, any additional details). - Professional: the independent business of the trade concerned, working in the Person's area, to which Kelki transmits the Request. - Consent Text: the text the Person accepts before sending, in its version in force, currently version `v2026-10-18`: « J'accepte que ma demande et mes coordonnées soient transmises à un ou plusieurs professionnels du métier de mon secteur, qui pourront me rappeler à ce sujet. » (“I agree that my request and my contact details be sent to one or more professionals of the trade in my area, who may call me back about it.”) - Sandbox: the test environment (`kk_test_` keys); production: the real environment (`kk_live_` keys). ## 2. Purpose of the service The API lets the Partner offer its users, from its own service, the Kelki flow: find the trade that matches a need, choose a service and a timing from Kelki's lists, check the place, then send a Request that Kelki transmits, after confirmation by the Person, to one or more Professionals of the trade in their area, who call them back. Kelki performs no service. The service contract is concluded directly between the Person and the Professional, as for the website form (see the [legal notice](https://kelki.ai/mentions-legales/) and the [website terms of use](https://kelki.ai/conditions-d-utilisation/)). ## 3. Access, accounts and environments - Self-service sandbox. The developer account gives access to the sandbox: real catalog, same validations, no real Request, no e-mail sent. Enter only dummy data (“Exemple” names, `example.com` domain). - Production upon approval. Real access is opened by Kelki after reviewing the Partner's service (description, screens of the flow, contact details of a person in charge). Kelki may refuse or withdraw this access, giving reasons for its decision. - Accurate information. The Partner provides accurate, up-to-date information, and appoints a technical contact and an incident contact. - Displayed name. The Partner's name shown in the confirmation e-mail (“… with App name”) is set by Kelki, without link or address, to avoid any confusion or phishing. ## 4. Free of charge and business model Access to the API is free for the Partner. Kelki does not invoice the Partner and pays it no remuneration. Kelki is paid, as for its website, by the Professionals who buy the Requests. No data is sold or transferred to the Partner. Should Kelki decide to change this model (for example revenue sharing), the new terms would be communicated at least three months in advance and would only apply to Partners who accept them. ## 5. The Person's consent and e-mail confirmation These rules are the reason the API exists. Failing to respect them justifies immediate suspension (article 11). - One Request, one Person who wants it. The Partner only sends a Request if the Person wanted it themselves, for their own need, with their own contact details (or those of a person who expressly authorised them). - Summary, then Consent Text, word for word. Before sending, the Partner shows the Person the summary (trade, service, timing, place, contact details), then the Consent Text as provided by the API, without changing, shortening or translating it, with a checkbox left unticked by default, separate from its own terms and from any other box. - E-mail confirmation of every real Request. In production, every Request receives a Kelki e-mail “Confirmer ma demande” (confirm my request). It is transmitted to Professionals only after the Person clicks the button on that page. Without confirmation within 48 hours, it is abandoned and its contact details are erased. The confirmation link is never given to the Partner; the Partner never tries to confirm on the Person's behalf. - Informing the Person. Next to the send button, the Partner displays the notice provided in annex 1 of the [data processing agreement](https://kelki.ai/developers/en/terms/data-processing/#annex-1), with the link to Kelki's privacy policy. - No attestation instead of the Person. At launch, no other confirmation method is open: Kelki does not recognise consent “attested” by the Partner. ## 6. Trades offered and exclusions - The Partner only uses the trades, services, timings and places returned by the API, on the same terms as the form and the Kelki connector for AI assistants. - Health excluded. Health trades are not offered by the API. The Partner does not misuse another trade to pass a health need through it and never invites the Person to describe their state of health or any other sensitive data. - Trades under review excluded. Trades not yet approved by Kelki are not offered. The list changes: the Partner re-reads the catalog instead of hard-coding it. - Kelki may withdraw a trade, a service or a country at any time, without notice where a legal or security reason requires it. ## 7. Technical limits The API is free; its limits act as a safeguard. Values in force (the plan is assigned by Kelki; it may be raised case by case): | Plan | Requests / min (per key) | Requests / day (per account) | Real Requests / day | Agent messages / day | Webhooks | | Découverte (sandbox only) | 30 | 2,000 | 0 | 50 | 2 | | Standard | 120 | 20,000 | 50 | 500 | 5 | | Partenaire | 600 | 200,000 | 500 | 5,000 | 10 | Limits shared by all Kelki channels also apply: at most 3 Requests per 24 hours for the same phone number or e-mail address, a global cap on Requests awaiting confirmation per hour, and limits per IP address. The Partner does not work around these limits (several accounts, multiplied keys, rotating addresses). A `429` response is respected by waiting for the time given by `Retry-After`. ## 8. Security and keys - Keys and secrets are personal to the Partner, kept server-side, never in a web page, a mobile app, a code repository or a log. Only a read-only key may be used from a browser, for the declared origins. - The Partner replaces an exposed key without delay (rotation in the developer space) and tells Kelki. - Webhooks are received over HTTPS and their signature is checked before any processing. - The Partner reports to Kelki any security incident affecting the integration (key leak, compromise, doubt about Requests sent) no later than 24 hours after becoming aware of it, at [contact@kelki.ai](mailto:contact@kelki.ai). - Security testing of the API is only done with Kelki's written consent. A vulnerability found in good faith is reported to Kelki, without exploiting or publishing it before it is fixed. ## 9. Personal data Kelki is the controller of the Requests (putting the Person in touch with Professionals). For collecting and sending Requests through the API, the Partner acts on Kelki's behalf, as a processor within the meaning of article 28 of the GDPR: the [data processing agreement](https://kelki.ai/developers/en/terms/data-processing/) sets out its obligations and the reasons for this qualification. The Partner remains solely responsible for the processing it carries out on its own behalf (its users' accounts, bookings, invoicing…). In return, the Partner only receives statuses and masked contact details. It never receives a Professional's contact details or the identity of the Professional who took the Request. ## 10. Intellectual property and catalog - For the term of the contract, Kelki grants the Partner a personal, non-exclusive, free and non-transferable right to use the API and its responses solely to offer the Request flow to its users. - The lists of trades, services, timings, places, the texts and the database containing them remain Kelki's property (articles L. 112-3 and L. 341-1 et seq. of the French Intellectual Property Code). The Partner does not extract them in bulk, does not republish them and does not use them to build a competing service. - The Partner may mention Kelki (name and logo provided by Kelki) to present the service, without suggesting a partnership broader than these terms. ## 11. Suspension and termination - Kelki may suspend a key, the creation of real Requests or an account, without notice, in the event of a breach of articles 5, 6, 8 or of the [acceptable use policy](https://kelki.ai/developers/en/terms/acceptable-use/), of a risk to Persons, Professionals or security, or of an abnormal rate of Requests never confirmed or reported. Kelki informs the Partner and gives the reasons. - Either party may end the contract at any time, in writing, with 30 days' notice. Kelki may end it without notice in the event of a serious or repeated breach. - At the end of the contract, the keys are revoked; the Partner deletes the data received on Kelki's behalf under the conditions of the data processing agreement. ## 12. Availability and liability - The API is provided free of charge, under a best-efforts obligation. Kelki guarantees neither permanent availability nor that a Professional will call the Person back. The status of the services is published on Kelki's status page. - Kelki may change the API; breaking changes go through a new version, the old one remaining served for at least 12 months after the announcement. - Each party is liable for direct and foreseeable damage caused by its fault (articles 1231-1 and 1231-3 of the French Civil Code). Kelki is not liable for the performance of services by Professionals, nor for the operation of the Partner's service. - The Partner indemnifies Kelki against third-party claims resulting from its breach of these terms (in particular sending Requests without the Person's consent). - These limits do not apply in the event of gross negligence or wilful misconduct, nor to obligations relating to personal data. ## 13. Changes to the terms Kelki may change these terms. Changes are announced in the developer space and by e-mail to the Partner's contact at least 30 days before they take effect, except for changes required by law or security. A Partner who refuses them may terminate free of charge before that date. ## 14. Governing law and disputes These terms are governed by French law. The parties first seek an amicable solution. Failing that, any dispute falls within the exclusive jurisdiction of the Paris economic activities court (tribunal des activités économiques de Paris). ## Reference texts - Regulation (EU) 2016/679 (GDPR), articles 4, 6, 7, 9, 13, 28, 32 and 33; French Law no. 78-17 of 6 January 1978 as amended. - French Civil Code, articles 1103, 1104, 1231-1 and 1231-3; French Intellectual Property Code, articles L. 112-3 and L. 341-1 et seq. - CNIL, technical recommendation on data sharing through APIs (2023); CNIL, “La prospection B to C : quelles règles pour transmettre des données à des partenaires ?”. ## About this page - URL : https://kelki.ai/developers/en/terms/ - Language : en - fr : https://kelki.ai/developers/fr/terms/ - en : https://kelki.ai/developers/en/terms/ - x-default : https://kelki.ai/developers/ - Portal : https://kelki.ai/developers/llms.txt