Install Jentic One Beta

Connect the Clment REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clment REST 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%2Fclment.com%2Fclment" | 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%2Fclment.com%2Fclment" | 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 Clment REST API.

Upload a contract from a file or URL and read its extracted text and versions

Start an AI review against a rulebook and act on its findings

Generate a redline and download it by token

Ask a question across your contracts or run a full-text search

Track key dates and set reminders on them

GET STARTED

Start building with Clment REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Clment REST API for, with concrete tasks.

★ Agent-Run Contract Review

An AI agent uploads a contract, starts a review against a rulebook, and reads the findings through Jentic, then generates a redline when changes are needed. The region-specific bearer key scopes access to one workspace, and a rule can keep the agent on uploading and reviewing while deletes and bulk operations stay out. The agent finds each operation by intent and calls it directly.

Upload a vendor contract, start a review against the standard rulebook, and list the findings it returns.

Contract Search and Q&A

A workflow searches a contract portfolio and asks natural-language questions across it, pulling the extracted text and activity for each matching contract. Clment returns results scoped to the workspace key and keeps document versions so answers cite the right revision. Teams use this to answer obligation and renewal questions without opening every file.

Search contracts for 'auto-renewal' and ask what notice period each requires, citing the version.

Key-Date and Obligation Tracking

A workflow lists the key dates across a contract portfolio, adds custom dates to a contract, and sets reminders so a renewal or deadline is not missed. Clment stores dates per contract and surfaces portfolio KPIs in a dashboard summary. Teams use this to stay ahead of obligations across many agreements.

List the key dates due in the next 30 days and set a reminder on each renewal.

Key Endpoints

57 endpoints — the clment rest api gives programmatic access to a contract workspace: it lists, uploads, and reads contracts, tracks their document versions and activity, and manages the tags and lifecycle status across many contracts at once.

METHOD

PATH

DESCRIPTION

GET

/contracts

List contracts

POST

/contracts/upload

Upload a contract file

GET

/contracts/{id}

Get a contract

POST

/contracts/{id}/review

Start an AI review

GET

/reviews

List reviews

POST

/ask

Ask a question across your contracts

GET

/search

Search contracts

GET

/dates

List key dates

GET

/contracts

List contracts

POST

/contracts/upload

Upload a contract file

GET

/contracts/{id}

Get a contract

POST

/contracts/{id}/review

Start an AI review

GET

/reviews

List reviews

POST

/ask

Ask a question across your contracts

GET

/search

Search contracts

GET

/dates

List key dates

Why Jentic?

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

Setup

Wiring the Clment API by hand means generating a clm_sk_live_ key, sending it as a bearer token, and picking the right regional host among the US, EU, UK, CA, AU, and NZ endpoints. Through Jentic you install once, import Clment from the API Directory, store the key once, and your agent calls it.

Permission scoping

Clment carries the contract id and review id in the URL path, so a rule can pin your agent to reading, searching, and reviewing specific contracts. You choose the operations it may call, so destructive ones like deleting a contract or a bulk-delete are not included unless you add them.

Credential isolation

Your Clment key 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 'start a contract review' or 'search our contracts', and Jentic returns the matching Clment operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Clment REST API through Jentic.

What authentication does the Clment API use?

The Clment API authenticates with a bearer token in the Authorization header, per its OpenAPI spec, using keys that start with clm_sk_live_. You generate a key in the app under Settings, and it is scoped to one workspace. Keys are region-specific, with separate hosts for the US, EU, UK, CA, AU, and NZ. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only at call time.

Can I run AI contract reviews with the Clment API?

Yes. You upload a contract, start a review against a rulebook, and read its findings, then apply decisions, add comments, and generate a redline. You can also ask questions across your contracts and search them by full text.

What are the rate limits for the Clment API?

The OpenAPI spec does not specify rate limits for the Clment API; the credits and limits for the current period are reported by the usage endpoint. Check the vendor's documentation at https://clment.com/help/api for current limits.

Can I limit what my agent is allowed to do with the Clment API?

Yes. Write a rule that allows the read, search, and review operations but not deletes or bulk changes, so the agent can analyze contracts without removing any. Contract and review ids travel in the URL path, so the rule binds cleanly, and every call it makes is logged.

Is there a Clment MCP server?

You don't need an MCP server to give your agent the Clment API. Jentic connects it directly from the API Directory: import it, store your region-specific key once, and your agent calls the contract, review, and search operations. You skip loading another server's tool definitions into the agent's context.

How do I run a contract review through Jentic?

Add the Clment API from the Jentic API Directory and store your region-specific key once. Your agent then searches by intent such as 'start a contract review' and Jentic returns the matching operation with its input schema, so it can upload the contract and read the findings. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Clment REST API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageDocument Managementbearer57 EndpointsREST

For Agents

List, upload, and read contracts, run AI reviews against rulebooks, generate redlines, and search or ask questions across a contract workspace. Authenticated with a region-specific bearer key.

Use for: Upload a contract and start an AI review against our rulebook, Search our contracts for a renewal clause, Ask a question across all our contracts, List the key dates coming up and set a reminder

Not supported: Does not provide e-signature, billing, or CRM. Use for contract storage, AI review, search, and key-date tracking only.

The Clment REST API gives programmatic access to a contract workspace: it lists, uploads, and reads contracts, tracks their document versions and activity, and manages the tags and lifecycle status across many contracts at once. It starts AI reviews against rulebooks, returns findings with decisions and comments, generates redlines, and can answer a question across your contracts or search them by full text. Key dates carry reminders, chat sessions hold saved conversations, and the API converts a PDF to Word. Keys are issued per region, with hosts for the US, EU, UK, CA, AU, and NZ.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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: BSignals: 4

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: D+Signals: 4

49%

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.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Clment REST API to your agent

Capabilities

Start building with Clment REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Clment REST API

Jentic AI Readiness Score

Clment REST 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