canonical: https://jentic.com/apis/clarify.ai/clarify

# Clarify API

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- Grant and revoke per-record and per-object access for users
- Comment on records and track activity across objects and schemas

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Records** — Create, read, update, delete, merge, and bulk-edit records on standard and custom objects
- **Lists** — Build lists from object records, publish or unpublish them, and export rows as CSV
- **Schemas** — Define custom objects, fields, field order and visibility, and object relationships
- **Record Relationships and Attachments** — Link records to each other and attach uploaded files with signed upload URLs
- **Access and Users** — Per-object and per-record access grants, workspace users, roles, and invitations
- **Collaboration** — Comments, activity history, meeting recordings, campaigns, and workflows

## AI readiness

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.

- **Score:** 55 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 36 / 100
  - Developer Experience & Jentic Compatibility: 45 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 87 / 100
  - Security: 55 / 100
  - AI Discoverability: 86 / 100
- **View full report:** https://jentic.com/apis/clarify.ai/clarify/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Attio** — A modern CRM built on flexible objects, records, and lists, much like Clarify's data model.
- **Affinity** — A relationship-intelligence CRM focused on people, organizations, and deal flow.
- **Airtable** — A flexible records database you can sync alongside Clarify for spreadsheet-style views.

## FAQ

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