Getclarify Clarify API
55
AI ReadinessNon-Ready (C)55/100
Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey, bearer91 EndpointsREST
For Agents
Create, update, and merge CRM records in a Clarify workspace, group them into lists, and manage comments, access grants, and attachments. Authenticates with an API key or a user access token.
Use for: Create a new record in a workspace object, Add records to a list and publish it, Post a comment on a record and read its activity, Export a list's rows as CSV
Not supported: Does not process payments, send SMS, or host video meetings. Use for managing records, lists, and collaboration within a Clarify workspace only.
The Clarify API manages the records, lists, and collaboration inside a CRM workspace, where every object holds records that an agent can create, update, merge, and relate to one another. Records can be grouped into lists that are published or exported as CSV, annotated with comments, and tracked through an activity trail, while object and record access grants control who can see each one. It also covers custom object schemas, file attachments on records, and meeting recordings and transcripts, all scoped to a workspace in the URL path.
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.
1
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%2Fgetclarify.ai%2Fgetclarify" | sh2
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%2Fgetclarify.ai%2Fgetclarify" | 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.
Capabilities
What an agent can do with Clarify API.
Create, update, and merge records within a workspace object
Group records into lists and publish or export a list's rows as CSV
Post comments on a record and read its activity trail
Grant and revoke access to records and objects
Define custom object schemas for a workspace
Attach files to records and manage meeting recordings and transcripts
Use Cases
Patterns agents use Clarify API for, with concrete tasks.
★ Agent-Maintained CRM Records
An AI agent connected through Jentic creates and updates records inside a Clarify workspace object and merges duplicates it finds, so the CRM stays current without a person editing each record. Because records, their relationships, and their activity trail live behind the same workspace, the agent can read context before it writes.
Create a record in the given workspace object, then merge it with an existing duplicate if one is found
List Building and CSV Export
A workflow groups records into a list, publishes it, and exports the list's rows as CSV for use elsewhere, turning a segment of CRM records into a shareable file. The list stays tied to its object, so the export reflects the records currently in it.
Create a list for this object, add the matching records, publish it, and export its rows as CSV
Record Access Delegation
An operations workflow grants a teammate access to specific records and revokes it when the work is done, using the record and object access grant operations to keep visibility tight. This lets an agent hand out and pull back access without a workspace admin doing it manually.
Grant a teammate access to this record, then revoke the grant once the task is complete
Key Endpoints
91 endpoints — the clarify api manages the records, lists, and collaboration inside a crm workspace, where every object holds records that an agent can create, update, merge, and relate to one another.
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
Update records in bulk
POST
/workspaces/{workspace}/objects/{object}/records/{record}/merges
Merge records
POST
/workspaces/{workspace}/objects/{object}/lists
Create a list
POST
/workspaces/{workspace}/objects/{object}/lists/{list}/rows/csv
Export a list's rows as CSV
POST
/workspaces/{workspace}/comments
Create a comment
POST
/workspaces/{workspace}/schemas/objects
Create a custom object
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
Update records in bulk
POST
/workspaces/{workspace}/objects/{object}/records/{record}/merges
Merge records
POST
/workspaces/{workspace}/objects/{object}/lists
Create a list
POST
/workspaces/{workspace}/objects/{object}/lists/{list}/rows/csv
Export a list's rows as CSV
POST
/workspaces/{workspace}/comments
Create a comment
POST
/workspaces/{workspace}/schemas/objects
Create a custom object
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Clarify API
- Non-Ready (C)55/100
36
Foundational Compliance45
Developer Experience & Jentic Compatibility57
AI-Readiness & Agent Experience87
Agent Usability55
Security90
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
36
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.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
45
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: DSignals: 4
5%
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.
57
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.
0%
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.
87
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.
55
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).
90
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
90%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Clarify API by hand means choosing between an API key and a bearer user access token, carrying it in the Authorization header, and threading workspaces, objects, records, and lists together yourself. Through Jentic you install once, import Clarify from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Clarify puts the workspace id in the URL path (/workspaces/{workspace}/...), so a rule can pin your agent to one workspace: it can read and create records there and reach nothing outside it. You choose which operations it may call, so destructive ones like deleting records or revoking access grants are not included unless you add them.
Credential isolation
Your Clarify API key or access token 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 as CSV', and Jentic returns the matching Clarify operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Clarify API through Jentic.
Is there a Clarify 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 credential once, and your agent can create records, build lists, and read activity straight away, with no extra server to run and no tool definitions to load into the agent's context.
Can I limit what my agent is allowed to do with the Clarify API?
Yes. Write a rule that allows only the record read and create operations under one workspace id, so the agent can add and read records in that workspace and touch nothing else, and every call it makes is logged. Destructive operations like deleting records or revoking access grants are left out unless you add them.
What authentication does the Clarify API use?
The Clarify API accepts two credentials per its OpenAPI spec: an API key sent in the Authorization header, and a bearer user access token also sent in the Authorization header, where some person-acting endpoints accept only the bearer token. Through Jentic the credential is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.
Can I export a Clarify list as CSV?
Yes. You group records into a list, publish it, and then call the operation that exports the list's rows as CSV, so a segment of CRM records becomes a shareable file. The export reflects the records currently in the list under that object.
What are the rate limits for the Clarify API?
The OpenAPI spec does not specify rate limits for the Clarify API. For current limits and token details, see the Clarify documentation at https://www.clarify.ai.
How do I keep CRM records current through Jentic?
Import the Clarify API from the Jentic API Directory, then have your agent issue a request such as 'create a record in this workspace object'. Jentic matches the intent to the create-record operation and returns its input schema so the agent sends the right fields, with your stored credential injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED