Install Jentic One Beta

Connect the Conduyt API to your agent

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

Create and update contacts with tags, custom fields, and activity history

Track companies and the deals linked to them

Move deals through pipeline stages on a board

Run email sequences and drip campaigns against contacts

Trigger automations and workflows on CRM records

GET STARTED

Start building with Conduyt API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Conduyt API for, with concrete tasks.

★ Agent-Managed CRM Updates

An AI agent connected through Jentic can keep the CRM current from a conversation or an inbound event: it creates a contact, creates a deal linked to that contact, and previews the deal update with a dry run before committing. The Idempotency-Key header lets the agent retry a create safely without producing duplicates.

Create a contact, create a deal linked to it, and preview the deal update with a dry run before committing

Pipeline Reporting

Sales leaders need an up-to-date view of the pipeline. Conduyt lists deals filtered by stage and lists companies that have open deals, so an agent can assemble a stage-by-stage pipeline summary and flag the accounts with active opportunities without exporting the whole CRM.

List deals in the Negotiation stage and the companies that have open deals

Outbound Sequencing

Conduyt carries email sequences and drip campaigns beside the CRM records, so follow-up runs from the same data. An agent enrolls a new contact in an email sequence and then reads the contact's activities to confirm the enrollment took, keeping outreach tied to the contact record.

Enroll a new contact in an email sequence and read the contact's activities to confirm it

Safe Bulk Edits

Bulk changes to a CRM are risky, so Conduyt lets an agent rehearse them. Write operations accept a dry_run flag that returns the effect without persisting it, so an agent can validate a batch of contact updates first, then re-run with an Idempotency-Key to apply them exactly once.

Update a batch of contacts with a dry run first, then commit with an Idempotency-Key

Key Endpoints

915 endpoints — the conduyt api manages a full crm over its contacts, companies, deals, pipelines, tasks, and notes, with email sequences, drip campaigns, automations, forms, calendars, and invoices layered on top.

METHOD

PATH

DESCRIPTION

POST

/contacts

Create a contact

GET

/contacts

List contacts

POST

/companies

Create a company

GET

/companies

List companies

POST

/deals

Create a deal

GET

/deals

List deals

POST

/contacts

Create a contact

GET

/contacts

List contacts

POST

/companies

Create a company

GET

/companies

List companies

POST

/deals

Create a deal

GET

/deals

List deals

Why Jentic?

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

Setup

Wiring Conduyt by hand means handling its bearer cdy_ key, choosing between dry_run and committed writes, and setting an Idempotency-Key on creates across a very large surface. Through Jentic you install once, import Conduyt from the API Directory, store the key once, and your agent calls it.

Permission scoping

Conduyt puts record ids in the URL path (/contacts/{id}, /deals/{id}), so a rule can bound your agent to the operations you pick, such as reading contacts and deals, while create, update, and delete operations stay out unless you add them. Many writes also accept a dry_run flag so the agent can preview a change before it commits.

Credential isolation

Your Conduyt 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 contact' or 'list deals in a pipeline', and Jentic returns the matching Conduyt operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Conduyt API through Jentic.

What authentication does the Conduyt API use?

The Conduyt API authenticates with a bearer API key sent in the Authorization header, where keys carry a cdy_ prefix 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 filter deals by pipeline stage with the Conduyt API?

Yes. The list deals operation accepts filters including stage, assigned owner, and contact, and the list companies operation accepts a hasOpenDeals filter, so an agent can report the pipeline stage by stage and surface the accounts with active opportunities.

What are the rate limits for the Conduyt API?

The OpenAPI spec does not define numeric rate limits for the Conduyt API. Check the Conduyt documentation at https://conduyt.app for the current request limits that apply to your API key.

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

Yes. Write a rule that allows only the contact and deal read operations, so the agent can list and inspect your CRM records but cannot create, update, or soft-delete them, and every call it makes is logged. For any writes you do enable, the dry_run flag lets the agent preview the change first.

How do I create a contact with the Conduyt API through Jentic?

Search Jentic with an intent like 'create a CRM contact', and Jentic returns the create contact operation at /contacts with its input schema so your agent passes the contact fields and an Idempotency-Key. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Conduyt MCP server?

You don't need an MCP server to give your agent Conduyt. Jentic connects it directly from the API Directory: import the API, store your cdy_ key once, and your agent calls the contact, company, deal, and automation operations on demand.

Conduyt App Conduyt API

AI ReadinessFoundational (D+)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbearer915 EndpointsREST

For Agents

Create and update contacts, companies, and deals, move deals through pipelines, run email sequences and automations, and preview writes with a dry run through the Conduyt CRM.

Use for: Create a contact in my CRM, List deals in a specific pipeline stage, Find companies that have open deals, Add a tag to a contact

Not supported: Does not handle payment processing, email delivery infrastructure, or data warehousing. Use for managing CRM contacts, companies, deals, and their follow-up only.

The Conduyt API manages a full CRM over its contacts, companies, deals, pipelines, tasks, and notes, with email sequences, drip campaigns, automations, forms, calendars, and invoices layered on top. Contacts, companies, and deals are each addressed by id and support tagging, custom fields, and activity history. Many write operations accept an Idempotency-Key and a dry_run flag so a change can be previewed before it commits. Authentication uses a bearer API key with a cdy_ prefix.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D-Signals: 4

68%

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

Example Density

How richly the API is illustrated with examples.

95%

Example Validity

Percentage of examples that conform to their schemas.

29%

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

34%

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.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

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

42%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Conduyt API to your agent

Capabilities

Start building with Conduyt API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Conduyt App Conduyt API

Jentic AI Readiness Score

Conduyt 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