Install Jentic One Beta

Connect the Coldreach API to your agent

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

Pull the accounts and contacts enrolled in a specific outreach campaign

Search recent job-opening signals for a target account by its domain

Read the messages a campaign has sent to each contact

Exclude an account so it is skipped in future outreach

Upsert contacts into a campaign with pre-provided personalization variables

GET STARTED

Start building with Coldreach API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Coldreach API for, with concrete tasks.

★ Agent-Driven Campaign Monitoring

An AI agent connected through Jentic can watch a running cold-outreach campaign without a human logging in: it lists the contacts enrolled in the campaign, reads the messages already sent, and pulls the analytics overview to summarize reply activity. Because every operation is read-only, the agent reports progress without changing campaign state.

List the contacts in campaign cmp_123, read its sent messages, and fetch the analytics overview to report reply activity

Signal-Based Account Research

Before an agent enrolls or messages an account, it can check whether the company is actively hiring. The Coldreach jobs lookup returns recent job openings for a company by its domain, so the agent surfaces a timely hiring signal that explains why an account is worth contacting now.

Search job openings for the domain acme.com to surface hiring signals for an account before outreach

Campaign Contact Sync

Teams that build their target list elsewhere can push it into Coldreach. The raw contacts upsert accepts contacts with pre-provided personalization variables, so an agent keeps a campaign's audience in sync with an external source of truth and sets the merge fields each message will use.

Upsert a contact with email and custom personalization variables into campaign cmp_123

Account Suppression

To keep an outreach program clean, an agent can exclude accounts that should never be contacted, such as existing customers or competitors. The exclude operation marks an account so Coldreach skips it in future outreach, giving the agent a programmatic suppression control.

Exclude the account for domain acme.com so it is skipped in future outreach

Key Endpoints

13 endpoints — the coldreach api retrieves your outbound sales campaigns along with the accounts, contacts, and messages enrolled in each one.

METHOD

PATH

DESCRIPTION

GET

/public/v1/campaigns

List campaigns

GET

/public/v1/campaigns/{id}

Get campaign details

GET

/public/v1/campaigns/{id}/contacts

List the contacts enrolled in a campaign

GET

/public/v1/campaigns/{id}/messages

List the messages a campaign has sent

POST

/public/v1/campaigns/{id}/raw/contacts

Upsert contacts with pre-provided variables

GET

/public/v1/jobs/{domain}

Search recent job openings for a company domain

POST

/public/v1/accounts/exclude

Exclude an account from outreach

GET

/public/v1/analytics/overview

Get an analytics overview of campaign performance

GET

/public/v1/campaigns

List campaigns

GET

/public/v1/campaigns/{id}

Get campaign details

GET

/public/v1/campaigns/{id}/contacts

List the contacts enrolled in a campaign

GET

/public/v1/campaigns/{id}/messages

List the messages a campaign has sent

POST

/public/v1/campaigns/{id}/raw/contacts

Upsert contacts with pre-provided variables

GET

/public/v1/jobs/{domain}

Search recent job openings for a company domain

POST

/public/v1/accounts/exclude

Exclude an account from outreach

GET

/public/v1/analytics/overview

Why Jentic?

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

Setup

Wiring Coldreach by hand means handling its x-api-key organization key, learning the orgId.secret format, and paging every campaign list yourself. Through Jentic you install once, import Coldreach from the API Directory, store the key once, and your agent calls it.

Permission scoping

Coldreach puts the campaign id in the URL path (/public/v1/campaigns/{id}/...), so a rule can pin your agent to one campaign: it can read that campaign's contacts and messages and nothing else. You choose the operations it may call, so write actions like excluding an account are not included unless you add them.

Credential isolation

Your Coldreach organization 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 'read a cold outreach campaign' or 'find job-opening signals for a company', and Jentic returns the matching Coldreach operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Coldreach API through Jentic.

What authentication does the Coldreach API use?

The Coldreach API authenticates with an organization API key sent in the x-api-key request header, in the format orgId.secret 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 search job openings for a target account with the Coldreach API?

Yes. The jobs lookup at /public/v1/jobs/{domain} returns recent job openings for a company by its domain, accepting cursor, since, and take parameters to page through results. Agents use this as a hiring signal to decide which accounts are worth contacting now.

What are the rate limits for the Coldreach API?

The OpenAPI spec does not define rate limits for the Coldreach API. Check the Coldreach developer documentation at https://developer.coldreach.ai for the current limits that apply to your organization key.

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

Yes. Coldreach puts the campaign id in the URL path, so write a rule that allows only the read operations on one campaign: the agent can then list that campaign's contacts and messages but cannot exclude an account or upsert contacts, and every call it makes is logged.

How do I pull a campaign's contacts with the Coldreach API through Jentic?

Search Jentic with an intent like 'list contacts in a cold outreach campaign', and Jentic returns the campaign contacts operation at /public/v1/campaigns/{id}/contacts with its input schema so your agent passes the campaign id and pages through results. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Coldreach MCP server?

You don't need an MCP server to give your agent Coldreach. Jentic connects it directly from the API Directory: import the API, store your organization key once, and your agent calls the campaign, account, and job-signal operations on demand.

Coldreach API

AI ReadinessFoundational (D-)41/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing AutomationapiKey13 EndpointsREST

For Agents

Retrieve Coldreach outbound campaigns with their accounts, contacts, and sent messages, search job-opening signals by company domain, upsert contacts, and read campaign analytics.

Use for: Find all accounts enrolled in a Coldreach campaign, List the messages sent in an outreach campaign, Search recent job openings at a target account's domain, Exclude an account from future outreach

Not supported: Does not handle email delivery infrastructure, contact enrichment, or CRM record storage. Use for managing Coldreach outbound campaigns, contacts, and job-opening signals only.

The Coldreach API retrieves your outbound sales campaigns along with the accounts, contacts, and messages enrolled in each one. It searches recent job-opening signals for a target company by domain, upserts contacts with your own personalization variables, excludes accounts from future outreach, and reports campaign performance through an analytics overview. Authentication uses an organization API key passed in the x-api-key header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

86%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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

21%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

48%

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

50%

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: A+Signals: 1

91%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Coldreach API to your agent

Capabilities

Start building with Coldreach API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Coldreach API

Jentic AI Readiness Score

Coldreach 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