Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / CommsHarbor
CommsHarbor logo

CommsHarbor

56
AI ReadinessFoundational (C)56/100
See full scorecard
Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer, apiKey182 EndpointsREST

For Agents

Send transactional email for an organization, verify sending domains, read delivery feedback events and suppressions, and manage a tenant CRM of contacts, companies, and deals.

Use for: Send a transactional email from my organization, Verify the DKIM and DMARC state of a sending domain, Read the delivery events for a message I sent, Suppress a bounced recipient address

Not supported: Does not handle SMS, voice calls, or push notifications. Use for transactional email delivery and tenant CRM management only.

The CommsHarbor API sends transactional email on behalf of an organization and records what happens to every delivery. It registers and verifies sending domains against SES, DKIM, and DMARC, queues idempotent messages, exposes normalized delivery feedback events, and manages suppressions so bad addresses are not retried. A built-in tenant CRM stores contacts, companies, deals, pipelines, tasks, and marketing consent alongside the sending data. Authentication uses a bearer API key, with a session cookie for account-level operations.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the CommsHarbor to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CommsHarbor, 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.

1

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%2Fcommsharbor.com%2Fcommsharbor" | sh
2

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%2Fcommsharbor.com%2Fcommsharbor" | 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 CommsHarbor API.

Queue an idempotent transactional email for an organization

Register a sending domain and verify its SES, DKIM, and DMARC state

Read a delivery and its normalized SES feedback events

Suppress a recipient so a bad address is not retried

Store and update CRM contacts, companies, and deals in the tenant CRM

Import contacts from a consent-declared CSV and export them back

Use Cases

Patterns agents use CommsHarbor API for, with concrete tasks.

★ Agent-Sent Transactional Email

An AI agent connected through Jentic can send account notifications and confirmations without a mail server of its own: it queues an idempotent message for the organization and then reads the delivery's normalized SES feedback events to confirm the message was accepted and delivered. The idempotency key lets the agent retry safely without sending duplicates.

Queue a transactional email to a recipient and read its delivery events to confirm it was delivered

Sending Domain Onboarding

Before an organization can send, its domain has to pass authentication checks. CommsHarbor registers a sending domain and probes SES, DKIM, DMARC, and custom MAIL FROM state on demand, so an agent can drive domain onboarding and report exactly which records still need DNS changes.

Register the sending domain example.com and check its SES, DKIM, and DMARC verification state

Tenant CRM Management

CommsHarbor carries a tenant CRM beside its sending data, so the same credential that sends mail can keep records current. An agent creates and updates contacts, companies, deals, pipelines, and tasks, and records permission-based marketing consent for each contact, keeping the audience and its consent state in one place.

Create a contact in the tenant CRM and attach it to a deal in a pipeline

Deliverability Hygiene

To protect sender reputation, an agent reviews what happened to recent mail and acts on it. It reads the feedback events for a delivery and suppresses any recipient that hard-bounced or complained, so CommsHarbor stops retrying addresses that damage deliverability.

Read the feedback events for a delivery and suppress any recipient that hard-bounced

Key Endpoints

182 endpoints — the commsharbor api sends transactional email on behalf of an organization and records what happens to every delivery.

METHOD

PATH

DESCRIPTION

POST

/api/messages

Queue an idempotent transactional email delivery

GET

/api/organizations/{organization_id}/deliveries/{delivery_id}

Read one delivery and its SES MessageId

GET

/api/organizations/{organization_id}/deliveries/{delivery_id}/events

List the normalized SES feedback events for a delivery

POST

/api/organizations/{organization_id}/domains/{domain_id}/verify

Check SES, DKIM, and DMARC state for a sending domain

POST

/api/organizations/{organization_id}/crm/contacts

Create a contact in the tenant CRM

POST

/api/organizations/{organization_id}/suppressions

Suppress a recipient in the organization

POST

/api/messages

Queue an idempotent transactional email delivery

GET

/api/organizations/{organization_id}/deliveries/{delivery_id}

Read one delivery and its SES MessageId

GET

/api/organizations/{organization_id}/deliveries/{delivery_id}/events

List the normalized SES feedback events for a delivery

POST

/api/organizations/{organization_id}/domains/{domain_id}/verify

Check SES, DKIM, and DMARC state for a sending domain

POST

/api/organizations/{organization_id}/crm/contacts

Create a contact in the tenant CRM

POST

/api/organizations/{organization_id}/suppressions

Suppress a recipient in the organization

Jentic AI Readiness Score

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.

C

CommsHarbor

- Foundational (C)
56/100
42
Foundational Compliance
68
Developer Experience & Jentic Compatibility
59
AI-Readiness & Agent Experience
52
Agent Usability
58
Security
71
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
42

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.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

68

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
14%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

70%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

87%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

59

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4
79%

Description Coverage

Coverage of descriptions across API elements.

0%

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.

52

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: C-Signals: 1
51%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

58

Security

Trust, risk posture, and security compliance.

Grade: C+Signals: 1
57%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

71

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

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

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring CommsHarbor by hand means handling its bearer API key, the mmk_ key prefix, a session cookie for account operations, and idempotency keys on every send. Through Jentic you install once, import CommsHarbor from the API Directory, store the key once, and your agent calls it.

Permission scoping

CommsHarbor puts the organization id in the URL path (/api/organizations/{organization_id}/...), so a rule can pin your agent to one organization and the operations you pick. You choose what it may call, so destructive actions like deleting a sending domain or a CRM record are not included unless you add them.

Credential isolation

Your CommsHarbor 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 'send a transactional email' or 'verify a sending domain', and Jentic returns the matching CommsHarbor operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio SendGrid Mail

→

SendGrid is a high-volume transactional and marketing email sender with its own deliverability tooling.

Choose SendGrid when the agent needs a large, established email platform rather than CommsHarbor's combined sending and tenant CRM.

Alternative

Resend

→

Resend is a developer-first transactional email API focused on sending and delivery tracking.

Choose Resend when the agent only needs to send and track email without the CRM and consent features.

Complementary

Postmark

→

Postmark specializes in fast transactional delivery and detailed message activity.

Use Postmark alongside CommsHarbor when the agent needs a second sending path or richer per-message activity data.

Complementary

HubSpot CRM Contacts

→

HubSpot provides a full standalone CRM that can hold contacts beyond the CommsHarbor tenant CRM.

Use HubSpot when the agent needs a dedicated CRM of record and syncs contacts into CommsHarbor for sending.

FAQs

Specific to using CommsHarbor API through Jentic.

What authentication does the CommsHarbor API use?

Authenticated CommsHarbor endpoints use a bearer API key sent as an Authorization header (organisation keys use an mmk_ prefix), and account-level operations use a global session carried in an HttpOnly cookie per the OpenAPI spec. When you call it through Jentic, the 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 verify a sending domain with the CommsHarbor API?

Yes. The domain verify operation observes SES, DKIM, DMARC, and custom MAIL FROM state right now and stores what it saw, so an agent can register a sending domain, trigger a check, and report which DNS records still need attention before the organization sends mail.

What are the rate limits for the CommsHarbor API?

The OpenAPI spec does not define numeric rate limits for the CommsHarbor API. Check the CommsHarbor documentation at https://commsharbor.com for the current sending and request limits that apply to your organization.

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

Yes. Write a rule that allows only the message-send and delivery-read operations for one organization, so the agent can send mail and check its delivery events but cannot delete a sending domain or a CRM record, and every call it makes is logged.

How do I send a transactional email with the CommsHarbor API through Jentic?

Search Jentic with an intent like 'send a transactional email', and Jentic returns the messages operation at /api/messages with its input schema so your agent passes the recipient and content and an idempotency key. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a CommsHarbor MCP server?

You don't need an MCP server to give your agent CommsHarbor. Jentic connects it directly from the API Directory: import the API, store your bearer key once, and your agent calls the messaging, domain, delivery, and CRM operations on demand.

GET STARTED

Start building with CommsHarbor API

Explore with Jentic One
View OpenAPI Document