Install Jentic One Beta

Connect the Clarify API to your agent

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

Create and update records across standard and custom objects in a workspace

Organize records into lists and publish or export them as CSV

Model your own data by adding custom objects, fields, and relationships to the schema

Link records to each other and list a record's related records

Attach files to records and request signed upload URLs

GET STARTED

Start building with Clarify API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Clarify API for, with concrete tasks.

★ Agent-Driven CRM Updates Through Jentic

An AI agent can read and write Clarify CRM records through Jentic instead of integrating the data model by hand. The agent creates records on the right object, links them to related records, drops them into a list, and leaves a comment with activity history, all against one workspace. Per-record access grants keep the agent working only where the developer intends.

Create a company record, link a contact record to it, and add the company to a named list in the workspace

Flexible Data Modeling With Custom Objects

Teams that outgrow a fixed CRM schema use Clarify to define their own objects, fields, and relationships. The schema operations add custom objects, add or reorder fields, set field visibility, and declare relationships between objects, so records can represent entities a standard CRM does not ship with.

Create a custom object for deals, add a status field and an amount field to it, then create a record on the new object

List Building and CSV Export

Clarify groups records into lists that can be published for sharing or exported as CSV for reporting. A workflow can assemble a targeted list from records on an object, publish it, and pull the rows as CSV to hand to a downstream tool or spreadsheet.

Create a list on the companies object, add matching records to it, and export the list rows as CSV

Per-Record Access Governance

Clarify controls who can see each record through per-object and per-record access grants. An operator can grant a user access to a specific record, create grants in bulk, and revoke them later, keeping sensitive records visible only to the people who need them.

Grant a user access to a specific record, confirm the grant appears in the record's access list, then revoke it

Key Endpoints

91 endpoints — the clarify api manages a customer data model built from objects, records, lists, and relationships inside a workspace.

METHOD

PATH

DESCRIPTION

POST

/workspaces/{workspace}/objects/{object}/records

Create a record

GET

/workspaces/{workspace}/objects/{object}/records/{id}

Get a record

PATCH

/workspaces/{workspace}/objects/{object}/records/{id}

Update a record

POST

/workspaces/{workspace}/objects/{object}/lists

Create a list

GET

/workspaces/{workspace}/schemas

List object schemas

POST

/workspaces/{workspace}/comments

Create a comment

GET

/workspaces/{workspace}/objects/{object}/records/{id}/relationships/{relationship}

List related records

GET

/workspaces

List workspaces

POST

/workspaces/{workspace}/objects/{object}/records

Create a record

GET

/workspaces/{workspace}/objects/{object}/records/{id}

Get a record

PATCH

/workspaces/{workspace}/objects/{object}/records/{id}

Update a record

POST

/workspaces/{workspace}/objects/{object}/lists

Create a list

GET

/workspaces/{workspace}/schemas

List object schemas

POST

/workspaces/{workspace}/comments

Create a comment

GET

/workspaces/{workspace}/objects/{object}/records/{id}/relationships/{relationship}

List related records

GET

Why Jentic?

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

Setup

Wiring the Clarify API by hand means passing your key in the Authorization header, threading the workspace and object into every path, and tracking which administrative operations need a bearer token instead. Through Jentic you install once, import Clarify from the API Directory, store the key once, and your agent calls it.

Permission scoping

Clarify puts the workspace id in the URL path (the /workspaces/ prefix), so a rule can pin your agent to one workspace and the record operations you choose. You choose the operations it may call, so destructive ones like deleting a custom object or removing a user are not included unless you add them.

Credential isolation

Your Clarify 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 create a CRM record or export a list, and Jentic returns the matching Clarify operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Clarify API through Jentic.

What authentication does the Clarify API use?

The Clarify API accepts an API key in the Authorization header or an HTTP bearer token, per its OpenAPI spec. Some administrative operations, such as managing API keys, invitations, and user roles, require the bearer token specifically, and a CLI sign-in settings endpoint is open. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time.

Can I create custom objects with the Clarify API?

Yes. The schema operations let you create custom objects, add fields and relationships to them, reorder fields and set their visibility, and delete objects you no longer need. Records you create then attach to those custom objects just like the standard ones.

What are the rate limits for the Clarify API?

The OpenAPI spec does not publish rate limits. Check the vendor documentation at https://www.clarify.ai for current limits.

How do I create a record with the Clarify API through Jentic?

Install Jentic One, then import Clarify from the API Directory and store your key once. Your agent searches by intent such as create a record, and Jentic returns the create-record operation with its input schema so the agent supplies the object and field values and gets the new record back. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Clarify API MCP server?

You don't need an MCP server to give your agent the Clarify API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the record, list, and schema operations on demand. The operations are discovered when the agent needs them, so they do not fill its context ahead of time.

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

Yes. Because the workspace id sits in the URL path, you can write a rule that pins your agent to one workspace and allows only the record and list operations it needs. Schema changes, user removal, and object deletion stay outside that set unless you add them, and every call the agent makes is logged.

Clarify API

AI ReadinessNon-Ready (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey, bearer91 EndpointsREST

For Agents

Create and update records on standard or custom objects, organize them into lists, model object schemas, and set per-record access inside a Clarify workspace. Link records, add comments, and export lists as CSV.

Use for: I want to create a new record on a custom object, Find all records in a list and export them to CSV, Add a custom field to an object schema, Link a contact record to a company record

Not supported: Does not handle payment processing, accounting, or outbound email delivery. Use for managing CRM records, objects, lists, and schemas within a workspace only.

The Clarify API manages a customer data model built from objects, records, lists, and relationships inside a workspace. It lets you create and update records on standard or custom objects, define the schema those objects use, link records together, and group them into lists you can publish or export as CSV. Collaboration features add comments, activity history, per-record access grants, and workspace membership controls. Meeting recordings, campaigns, and workflows extend the same workspace so an agent can work the CRM data and the processes around it from one API.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4

42%

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

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

Example Density

How richly the API is illustrated with examples.

46%

Example Validity

Percentage of examples that conform to their schemas.

30%

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

60%

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.

69%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

87%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

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: ASignals: 1

86%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Clarify API to your agent

Capabilities

Start building with Clarify API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Clarify API

Jentic AI Readiness Score

Clarify 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