Install Jentic One Beta

Connect the Projet - Client Import API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Projet - Client Import 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%2Fobat.fr%2Fobat" | 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%2Fobat.fr%2Fobat" | 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 Projet - Client Import API.

List the existing client records in Obat Sales

Analyze an uploaded CSV and flag each row as new, duplicate, or invalid

Create the selected clients in Obat Sales from the reviewed analysis

Use Cases

Patterns agents use Projet - Client Import API for, with concrete tasks.

★ AI Agent Client Import

An AI agent connected through Jentic imports a batch of clients into Obat Sales: it analyzes the uploaded CSV, reads which rows are new, and confirms those rows to create the clients. The analyze-then-confirm flow means the agent never creates records blindly from a raw file.

GET STARTED

Start building with Projet - Client Import API

Explore with Jentic One

View OpenAPI Document

Duplicate Detection Before Import

Before importing, a system uploads a CSV and reads the analysis that flags each row as new, duplicate, or invalid, so duplicates and bad rows are caught before any client is created. This keeps the Obat client list clean.

Upload a CSV and read which rows are flagged as duplicate or invalid

Existing Client Review

An agent lists the clients already in Obat Sales to decide which CSV rows are genuinely new before importing. This gives context for the import decision without leaving the API.

List the existing clients to decide which CSV rows to import

Key Endpoints

3 endpoints — the obat client import api imports customer records into obat sales from a csv file.

METHOD

PATH

DESCRIPTION

GET

/client/list

List existing clients

POST

/client/import

Analyze a CSV file of clients

POST

/client/send

Confirm and create the selected clients

GET

/client/list

List existing clients

POST

/client/import

Analyze a CSV file of clients

POST

/client/send

Confirm and create the selected clients

Why Jentic?

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

Setup

Wiring the Obat Client Import API by hand means obtaining the Obat JWT cookie, uploading the CSV, and sequencing analysis before the confirm step yourself. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The Obat Client Import API carries the CSV file and the selected rows in the request body, so rules bound which operations your agent may call, not which clients it creates. You choose the operations it may use, such as listing clients and analyzing a CSV, so confirming and creating clients is not included unless you add it.

Credential isolation

Your Obat JWT credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'import clients from a CSV' or 'list existing clients', and Jentic returns the matching Obat operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Projet - Client Import API through Jentic.

What authentication does the Obat Client Import API use?

It authenticates with an Obat JWT passed in the `jwt_payload` cookie, as declared in its OpenAPI spec. Through Jentic that credential is stored encrypted by your own Jentic One instance and injected at call time, so it never appears in the agent's prompt or logs.

Can I detect duplicate clients before importing with the Obat Client Import API?

Yes. The import operation analyzes an uploaded CSV and flags each row as new, duplicate, or invalid, so you can review the analysis and choose which rows to create before any client is added.

What are the rate limits for the Obat Client Import API?

The OpenAPI spec does not specify rate limits for the Obat Client Import API. Check your Obat account documentation for any limits before running large client imports.

Can I limit what my agent is allowed to do with the Obat Client Import API?

Yes. Write a rule that allows only the client-list and CSV-analysis operations, so the agent can review existing clients and check an import file but cannot confirm and create new clients, and every call it makes is logged.

How do I import clients with the Obat Client Import API through Jentic?

Search Jentic for 'import clients from a CSV', add the Obat Client Import API from the directory, and store your Obat credential once. Your agent analyzes the CSV and confirms the rows to import. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there an Obat Client Import API MCP server?

You don't need an MCP server to give your agent the Obat Client Import API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the list, analyze, and confirm operations. That keeps extra tool definitions out of the agent's context.

Obat Fr Projet - Client Import API

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Community OpenAPI document · agent-readyCRMContact ManagementapiKey3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List existing Obat clients, analyze a CSV of clients and flag each row as new, duplicate, or invalid, and create the selected clients in Obat Sales.

Use for: List the existing clients in Obat, Analyze a CSV file of clients for import, Check which rows in my CSV are duplicates, Import the selected clients into Obat Sales

Not supported: Does not handle invoicing, quotes, or project management in Obat. Use for importing client records from CSV only.

The Obat Client Import API imports customer records into Obat Sales from a CSV file. It lists existing clients, analyzes an uploaded CSV and flags each row as new, duplicate, or invalid, and then creates the selected clients from that analysis. The flow lets a user review the analysis and choose which rows to import before any client is created.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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: A-Signals: 4

70%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: B-Signals: 4

70%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

73%

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: C-Signals: 1

50%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Projet - Client Import API to your agent

Capabilities

Use Cases

Start building with Projet - Client Import API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Obat Fr Projet - Client Import API

Jentic AI Readiness Score

Projet - Client Import API

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