Install Jentic One Beta

Connect the GestionDiag API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GestionDiag API, 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%2Fgestion-diagnostic.fr%2Fgestiondiag" | sh

Step 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%2Fgestion-diagnostic.fr%2Fgestiondiag" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with GestionDiag API.

Create, list, duplicate, and archive diagnostic appointment dossiers

Manage appointment dates and raise callback requests for a dossier

Keep client records and their contacts up to date

Manage technicians along with their calendar access and certifications

Upload, retrieve, and delete diagnostic reports against a dossier

GET STARTED

Start building with GestionDiag API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GestionDiag API for, with concrete tasks.

★ Agent-Driven Dossier Intake

An AI agent connected through Jentic can open and route diagnostic jobs without a developer wiring the login token exchange. The agent creates a client record if needed, opens a dossier, sets the appointment date, and emails the assigned technician. Jentic injects the bearer token at call time so the credential never reaches the agent.

Create a client record, open a dossier for them, set its appointment date, and email the assigned technician

Report Collection and Delivery

Once a technician finishes a visit, the report needs attaching to the right dossier. The agent uploads the diagnostic report against the dossier id, retrieves the stored reports to confirm, and tags the file. This keeps each dossier's paperwork complete and findable.

Upload a diagnostic report to a dossier, retrieve the dossier's reports to confirm, and tag the uploaded file

Technician and Scheduling Admin

Operations teams keep the technician roster and appointments current. The agent lists technicians, checks a technician's certifications and calendar access, and updates the appointment date on a dossier accordingly. This keeps qualified technicians matched to the right jobs.

List technicians, read a technician's certifications, then set a dossier's appointment date for that technician

Key Endpoints

36 endpoints — the gestiondiag api runs a field-service back office for diagnostic businesses, organising client records, appointment dossiers, and the technicians who carry out the work.

METHOD

PATH

DESCRIPTION

POST

/rendez-vous/liste

List dossiers

POST

/rendez-vous/

Create a new dossier

PUT

/rendez-vous/gestion-rdv

Set or change the appointment date

GET

/rendez-vous/{id}

Get a dossier by id

POST

/compte_client/ajout

Create a client record

POST

/techniciens/ajout

Create a technician

POST

/upload/{rdv_id}

Upload a report to a dossier

POST

/rendez-vous/liste

List dossiers

POST

/rendez-vous/

Create a new dossier

PUT

/rendez-vous/gestion-rdv

Set or change the appointment date

GET

/rendez-vous/{id}

Get a dossier by id

POST

/compte_client/ajout

Create a client record

POST

/techniciens/ajout

Create a technician

POST

/upload/{rdv_id}

Upload a report to a dossier

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring GestionDiag by hand means posting the user mail and password to the login endpoint for a JWT bearer token, refreshing it on a 401, and remembering which dossier endpoints also take a query security token, all yourself. Through Jentic you install once, import GestionDiag from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

GestionDiag puts the dossier, client, and technician ids in the URL path, for example /rendez-vous/{id} and /compte_client/{Client_ID}, so a rule can pin your agent to reading individual records. You choose which operations it may call, so destructive ones like archiving a dossier or deleting a client, technician, or report are not included unless you add them.

Credential isolation

Your GestionDiag bearer token and security token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a diagnostic dossier' or 'set an appointment date', and Jentic returns the matching GestionDiag operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using GestionDiag API through Jentic.

What authentication does the GestionDiag API use?

Per its OpenAPI spec, the GestionDiag API uses a JWT bearer token obtained from the login endpoint and sent in the Authorization header. Some dossier endpoints also accept a security token passed as a query parameter for secured access. Through Jentic both credentials are stored encrypted by your own instance and injected at call time, so they never reach the agent.

Is there a GestionDiag MCP server?

You don't need an MCP server to give your agent GestionDiag. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like creating a dossier or uploading a report on demand, without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with GestionDiag?

Yes. Write a rule that allows only the dossier read and report-upload operations under the records you choose, so the agent can intake jobs and attach reports but cannot archive a dossier or delete a client, technician, or report unless you add those operations, and every call it makes is logged. This matches an intake bot that opens jobs without destructive power.

Can I schedule appointment dates with the GestionDiag API?

Yes. Use the appointment-date operation to set or change the date on a dossier, and raise a callback request when a client needs rescheduling. You can read a technician's calendar access to match the visit to an available technician.

What are the rate limits for the GestionDiag API?

The OpenAPI spec does not specify rate limits. Check the GestionDiag documentation on SwaggerHub at https://app.swaggerhub.com/apis/CONTACT_125/gestiondiag-api-rendez-vous for current limits before running bulk dossier jobs.

How do I open a diagnostic dossier with the GestionDiag API through Jentic?

Search Jentic for 'create a diagnostic dossier', which returns the client and dossier operations with their input schemas. The agent creates the client record, opens the dossier, sets its appointment date, and emails the technician, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Gestion Diagnostic Fr GestionDiag API

AI ReadinessFoundational (C)56/100

See full scorecard

Community OpenAPI document · agent-readyCRMContact Managementbearer, apiKey36 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage diagnostic client records, appointment dossiers, technicians, and uploaded reports for a field-service business. Authenticates with a JWT bearer token, with an optional query security token on some dossier endpoints.

Use for: I need to create a new diagnostic dossier for a client, Set the appointment date for a dossier, List all open dossiers, Upload a diagnostic report to a dossier

Not supported: Does not handle invoicing, payments, or the diagnostic measurements themselves. Use for managing diagnostic client records, appointment dossiers, technicians, and reports only.

The GestionDiag API runs a field-service back office for diagnostic businesses, organising client records, appointment dossiers, and the technicians who carry out the work. It creates, lists, duplicates, and archives dossiers, manages appointment dates and callback requests, and keeps client profiles and contacts up to date. It also manages technicians with their calendar access and certifications, uploads and retrieves diagnostic reports against a dossier, and tags dossiers and files. User requests authenticate with a JWT bearer token from the login endpoint, and some dossier endpoints also accept a security token as a query parameter.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

90%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

42%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

37%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

81%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: DSignals: 1

45%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GestionDiag API to your agent

Capabilities

Start building with GestionDiag API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Gestion Diagnostic Fr GestionDiag API

Jentic AI Readiness Score

GestionDiag - OpenAPI 3.0

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness