Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the L'Addition, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.ciss9%2Fladdition" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.ciss9%2Fladdition" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with L'Addition API.
Timer universel
Initialisation du terminal de point de vente (TPV)
Ouverture de session
Consultation infos marchand
GET STARTED
For Agents
Programmatically timer universel, initialisation du terminal de point de vente (tpv). Covers 23 operations.
Use for: I need to timer universel, I want to initialisation du terminal de point de vente (tpv), Search for ouverture de session, Find all consultation infos marchand
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
API pour l'Addition. The API exposes 23 endpoints.
Paramétrage du TPV
Envoi des transactions
Informations d'un badge (carte/bracelet...)
Patterns agents use L'Addition API for, with concrete tasks.
★ Developer Tools Operations
Use the L'Addition to perform developer tools operations programmatically. The API provides 23 endpoints covering core functionality including timer universel, initialisation du terminal de point de vente (tpv), ouverture de session.
Call GET /time to timer universel
Automated Badge Management
Automate badge operations by combining multiple L'Addition endpoints. Agents can initialisation du terminal de point de vente (tpv) and then ouverture de session in a single workflow.
Call POST /init/{BuilderKey} to initialisation du terminal de point de vente (tpv), then verify the result
AI Agent Integration via Jentic
AI agents discover and call L'Addition endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'timer universel', load the operation schema, and execute with Jentic-managed credentials
23 endpoints — api pour l'addition.
METHOD
PATH
DESCRIPTION
/time
Timer universel
/init/{BuilderKey}
Initialisation du terminal de point de vente (TPV)
/session/{IDMarchand}/{TimestampUTC}/{HMAC}
Ouverture de session
/consultation/{IDMarchand}/{TimestampUTC}/{HMAC}
Consultation infos marchand
/teleparametrage/{BuilderKey}/{IDMarchand}/{Session}
Paramétrage du TPV
/transactions/envoi/{BuilderKey}/{IDMarchand}/{Session}
Envoi des transactions
/badge/infos/{BuilderKey}/{IDMarchand}/{Session}
Informations d'un badge (carte/bracelet...)
/badge/recherche/{BuilderKey}/{IDMarchand}/{Session}
Recherche d'un badge (carte/bracelet...)
/time
Timer universel
/init/{BuilderKey}
Initialisation du terminal de point de vente (TPV)
/session/{IDMarchand}/{TimestampUTC}/{HMAC}
Ouverture de session
/consultation/{IDMarchand}/{TimestampUTC}/{HMAC}
Consultation infos marchand
/teleparametrage/{BuilderKey}/{IDMarchand}/{Session}
Paramétrage du TPV
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the L'Addition API by hand means computing its HMAC-signed session paths, targeting the paiement.solutions host, and handling the init, session, and transaction calls with retries yourself. Through Jentic you install once, import the L'Addition API from the API Directory, and your agent calls it without you writing that plumbing.
Permission scoping
The URL path segments here are signature and session tokens rather than a resource id, so scope the agent to the operations it needs, such as starting a session with POST /init/{BuilderKey} or reading a session with GET /session/{IDMarchand}/{TimestampUTC}/{HMAC}. You choose the allowed set, so sending transactions with POST /transactions/envoi is not included unless you add it.
Credential isolation
This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'open a terminal session' or 'look up badge info', and Jentic returns the matching L'Addition operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using L'Addition API through Jentic.
What authentication does the L'Addition use?
The L'Addition uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I timer universel with the L'Addition?
Yes. Use the GET /time endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the L'Addition?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I timer universel through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'timer universel'. Jentic returns the matching L'Addition operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the L'Addition have?
The L'Addition exposes 23 endpoints covering badge, consultation, contact operations.
Can I limit what my agent is allowed to do with the L'Addition API?
Yes. Jentic One is self-hosted, so you decide which L'Addition operations your agent may call by defining your own rules on the instance you run. You can allow it to start a session with POST /init/{BuilderKey} and read a session with GET /session/{IDMarchand}/{TimestampUTC}/{HMAC} while leaving out sending transactions via POST /transactions/envoi. Because the signature and session values live in the URL path rather than a stored credential, scoping the allowed operation set is how you control exactly what the agent can do.
/transactions/envoi/{BuilderKey}/{IDMarchand}/{Session}
Envoi des transactions
/badge/infos/{BuilderKey}/{IDMarchand}/{Session}
Informations d'un badge (carte/bracelet...)
/badge/recherche/{BuilderKey}/{IDMarchand}/{Session}
Recherche d'un badge (carte/bracelet...)