Install Jentic One Beta

Connect the Compelling API to your agent

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

Build a research list of target accounts inside a workspace

Generate contacts for a list from Compelling's data

Add AI insight columns and generate their answers for accounts and contacts

Run a multi-step research workflow over a list

Create filtered views of a list for a specific segment

GET STARTED

Start building with Compelling API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Compelling API for, with concrete tasks.

★ Agent-Built Target List

An AI agent connected through Jentic can assemble a prospecting list end to end: it creates a list in a workspace, adds the target accounts, defines an insight column with a research question, and generates the answers for each account. The agent returns a researched list without a human opening the Compelling app.

Create a list in a workspace, add accounts, add an insight column, and generate its answers for each account

Account Research at Scale

Compelling's insight columns turn a research question into a generated answer per account, so a team can research hundreds of companies at once. An agent adds an insight column, such as funding stage or recent hiring, and generates answers across the whole list rather than researching each account by hand.

Add an insight column asking for each account's funding stage and generate answers across the list

Contact Generation

Once the accounts are set, Compelling can populate the people. The contacts generation operation produces contacts for a list of target accounts, so an agent fills in decision-makers to research and later export, keeping the account and contact layers in one workspace.

Generate contacts for a list of target accounts and review the returned people

CRM Export

Research is only useful once it reaches the team's system of record. Compelling exports a list and pushes its enriched records through a configured integration, so an agent delivers finished research into the connected CRM instead of handing back a raw file.

Export a research list and push the enriched records to the connected CRM

Key Endpoints

67 endpoints — the compelling api builds research lists of target accounts and contacts inside a workspace and enriches them with ai-generated insight columns.

METHOD

PATH

DESCRIPTION

POST

/workspaces

Create a workspace

POST

/workspaces/{workspace_id}/lists

Create a research list

POST

/workspaces/{workspace_id}/lists/{list_id}/accounts

Add an account to a list

POST

/workspaces/{workspace_id}/lists/{list_id}/accounts/insights

Add an AI insight column for accounts

POST

/workspaces/{workspace_id}/lists/{list_id}/accounts/insights/{insight_id}/answers

Generate answers for an insight column

POST

/workspaces/{workspace_id}/lists/{list_id}/contacts

Generate contacts for a list

POST

/workspaces/{workspace_id}/lists/{list_id}/workflows/{workflow_id}/run

Run a research workflow

POST

/workspaces

Create a workspace

POST

/workspaces/{workspace_id}/lists

Create a research list

POST

/workspaces/{workspace_id}/lists/{list_id}/accounts

Add an account to a list

POST

/workspaces/{workspace_id}/lists/{list_id}/accounts/insights

Add an AI insight column for accounts

POST

/workspaces/{workspace_id}/lists/{list_id}/accounts/insights/{insight_id}/answers

Generate answers for an insight column

POST

/workspaces/{workspace_id}/lists/{list_id}/contacts

Generate contacts for a list

POST

/workspaces/{workspace_id}/lists/{list_id}/workflows/{workflow_id}/run

Run a research workflow

Why Jentic?

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

Setup

Wiring Compelling by hand means handling its bearer workspace key, nesting every call under workspace and list ids, and polling long-running insight and workflow jobs. Through Jentic you install once, import Compelling from the API Directory, store the key once, and your agent calls it.

Permission scoping

Compelling puts the workspace and list ids in the URL path (/workspaces/{workspace_id}/lists/{list_id}/...), so a rule can pin your agent to one list: it can read and enrich that list and nothing else. You choose the operations it may call, so actions like resetting a workspace or deleting a list are not included unless you add them.

Credential isolation

Your Compelling workspace 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 'build a target account list' or 'generate research insights', and Jentic returns the matching Compelling operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Compelling API through Jentic.

What authentication does the Compelling API use?

The Compelling API authenticates with a bearer API key issued from your workspace settings, passed as an Authorization header per its OpenAPI spec. When you call it through Jentic, that key is stored once by your own Jentic One instance and injected at execution time, so it never reaches the agent's prompt or logs.

Can I generate AI research insights with the Compelling API?

Yes. You add an insight column to a list of accounts or contacts with a research question, then call the insight answers operation to generate an answer per record. This lets an agent research a whole list, such as each account's funding stage, in one pass rather than one company at a time.

What are the rate limits for the Compelling API?

The OpenAPI spec does not define numeric rate limits for the Compelling API, and research operations also consume workspace credits. Check the Compelling documentation at https://docs.compelling.ai for the current request limits and credit costs.

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

Yes. Write a rule that allows only the account-add and insight-generate operations on one list, so the agent can build and enrich that list but cannot reset the workspace or delete the list, and every call it makes is logged.

How do I generate contacts for a list with the Compelling API through Jentic?

Search Jentic with an intent like 'generate contacts for an account list', and Jentic returns the contacts generation operation at /workspaces/{workspace_id}/lists/{list_id}/contacts with its input schema so your agent passes the workspace and list ids. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Compelling MCP server?

You don't need an MCP server to give your agent Compelling. Jentic connects it directly from the API Directory: import the API, store your workspace key once, and your agent calls the list, account, contact, and insight operations on demand.

Compelling API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer67 EndpointsREST

For Agents

Build workspace research lists of accounts and contacts, generate AI insight columns and their answers, run research workflows, and export results or sync them to a CRM through Compelling.

Use for: Create a research list of target accounts in a workspace, Generate contacts for an account list, Add an AI insight column to a list of accounts, Produce answers for a contact insight column

Not supported: Does not handle email sending, payment processing, or deterministic data verification. Use for building and AI-enriching account and contact research lists only.

The Compelling API builds research lists of target accounts and contacts inside a workspace and enriches them with AI-generated insight columns. It generates contacts for a list, adds insight columns whose answers are produced on demand, runs multi-step research workflows, and exports the results or pushes them to a connected CRM. Lists, views, accounts, and contacts are each addressed by id so an agent can assemble and refine a target list programmatically. Authentication uses a bearer API key issued from your workspace settings.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

92%

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

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

23%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

28%

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

22%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

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

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

91%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Compelling API to your agent

Capabilities

Start building with Compelling API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Compelling API

Jentic AI Readiness Score

Compelling 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