Install Jentic One Beta

Connect the Breakcold Public API to your agent

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

List the workspaces your bearer token is authorized to reach

Search CRM records across contacts, companies, and deals

Create a new CRM record from data your agent has gathered

Use Cases

Patterns agents use Breakcold Public API for, with concrete tasks.

★ Agent-captured lead to CRM record

An AI agent that qualifies a prospect can create a Breakcold record directly, writing the contact or company straight into the workspace the sales team already works in. The agent first lists its authorized workspaces so it writes to the right one.

GET STARTED

Start building with Breakcold Public API

Explore with Jentic One

View OpenAPI Document

CRM record search

A support or sales agent can search Breakcold records to find an existing contact, company, or deal before acting, avoiding duplicate records. Search runs across the record types the workspace holds.

Search Breakcold records for a company named Acme and return the matching record

Workspace-aware automation

An automation that serves several teams can list the workspaces its key is authorized for and route each new record to the correct one, so records never land in the wrong team workspace.

List the authorized workspaces and report which ones the current token can write records to

Key Endpoints

3 endpoints — the breakcold api reads and writes crm records across the workspaces a key is authorized to reach, and lets you search those records or create a new one from data your agent has gathered.

METHOD

PATH

DESCRIPTION

GET

/workspaces

List authorized workspaces

GET

/records

List or search CRM records

POST

/records

Create a CRM record

GET

/workspaces

List authorized workspaces

GET

/records

List or search CRM records

POST

/records

Create a CRM record

Why Jentic?

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

Setup

Wiring Breakcold by hand means handling its bearer-token auth and figuring out which workspace a token may write to before you create anything. Through Jentic you install once, import Breakcold from the API Directory, store the token once, and your agent calls it.

Permission scoping

You choose which Breakcold operations the agent may call, so you can allow workspace listing and record search while leaving record creation out until you add it.

Credential isolation

Your Breakcold 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', and Jentic returns the matching Breakcold operation with its input schema so the agent writes to the right workspace without browsing the docs.

FAQs

Specific to using Breakcold Public API through Jentic.

What authentication does the Breakcold API use?

The Breakcold API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. A token is tied to the workspaces it is authorized for, which you can list before writing any record.

Is there a Breakcold MCP server?

Breakcold offers a hosted MCP server that exposes the same contract. You can also connect Breakcold directly through Jentic: your agent gets the record and workspace operations from the spec without loading another server's tool definitions into its context, your token is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.

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

Yes. Write a rule that allows only workspace listing and record search, so the agent can read your CRM but cannot create records until you add the create operation, and every call it makes is logged.

Can I search CRM records with the Breakcold API?

Yes. The records endpoint lists or searches records across the contacts, companies, and deals a workspace holds, so an agent can look up an existing record before creating a duplicate.

What are the rate limits for the Breakcold API?

The OpenAPI spec does not publish a numeric rate limit. Check the Breakcold API reference at https://docs.breakcold.com/api/overview for the current limits before running a high-volume job.

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

Search Jentic for 'create a CRM record', and it returns the Breakcold create-record operation with its input schema. List your authorized workspaces first, then post the record to the right one. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Breakcold Public API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbearer3 EndpointsREST

For Agents

List authorized workspaces, search CRM records, and create a new record in Breakcold from data an agent has collected.

Use for: List the Breakcold workspaces my token can access, Search for CRM records matching a company name, Create a new contact record in Breakcold, Find all records in a given workspace

Not supported: Does not handle email sending, call logging, or payment processing. Use for Breakcold CRM record search and creation only.

The Breakcold API reads and writes CRM records across the workspaces a key is authorized to reach, and lets you search those records or create a new one from data your agent has gathered. Records cover the contacts, companies, and deals a sales team tracks in Breakcold. The surface is deliberately small: list your workspaces, search records, and create a record.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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

100%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

41%

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.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

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 Breakcold Public API to your agent

Capabilities

Use Cases

Start building with Breakcold Public API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Breakcold Public API

Jentic AI Readiness Score

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