Install Jentic One Beta

Connect the CleverReach API to your agent

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

Get receiver count for a client

Create a new account within an agency

Integrate CleverReach API into automated workflows

Query and filter CleverReach API records by parameters

Monitor CleverReach API operational status and events

GET STARTED

Start building with CleverReach API

Explore with Jentic One

View OpenAPI Document

Automated Clients Management

Automate clients operations by combining multiple CleverReach API endpoints. Agents can get active receiver count for a client and then get available mail sending quota in a single workflow.

Call GET /v3/clients/{id}/activereceivercount to get active receiver count for a client, then verify the result

AI Agent Integration via Jentic

AI agents discover and call CleverReach API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'get receiver count for a client', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

22 endpoints — cleverreach email marketing rest api for managing clients, groups, receivers, mailings, blacklists, and forms.

METHOD

PATH

DESCRIPTION

GET

/v3/clients/{id}/receivercount

Get receiver count for a client

GET

/v3/clients/{id}/activereceivercount

Get active receiver count for a client

GET

/v3/clients/{id}/contingent

Get available mail sending quota

GET

/v3/clients/{id}/invoiceaddress

Get client billing address

GET

/v3/clients/{id}/nextinvoicedate

Get next invoice date

GET

/v3/clients/{id}/plan

Get current subscription plan name

POST

/v3/clients/createAccount

Create a new account within an agency

POST

/v3/blacklist/validate

Filter list of emails to valid ones

GET

/v3/clients/{id}/receivercount

Get receiver count for a client

GET

/v3/clients/{id}/activereceivercount

Get active receiver count for a client

GET

/v3/clients/{id}/contingent

Get available mail sending quota

GET

/v3/clients/{id}/invoiceaddress

Get client billing address

GET

/v3/clients/{id}/nextinvoicedate

Get next invoice date

GET

/v3/clients/{id}/plan

Get current subscription plan name

POST

/v3/clients/createAccount

Create a new account within an agency

POST

/v3/blacklist/validate

Why Jentic?

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

Setup

Wiring the CleverReach API by hand means learning its bearer token auth, targeting the rest.cleverreach.com host, and threading client and receiver calls yourself. Through Jentic you install once, import CleverReach API from the API Directory, store the token once, and your agent calls it.

Permission scoping

CleverReach API puts the client id in the URL path (/v3/clients/{id}/...), so a rule can pin your agent to one client: it can read that client's receiver count, plan, and contingent and nothing else. You choose the operations it may call, so actions like account creation are not included unless you add them.

Credential isolation

Your CleverReach API 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 'get the receiver count for a client' or 'validate a blacklist entry', and Jentic returns the matching CleverReach API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CleverReach API through Jentic.

What authentication does the CleverReach API use?

The CleverReach API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I get receiver count for a client with the CleverReach API?

Yes. Use the GET /v3/clients/{id}/receivercount endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the CleverReach API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get receiver count for a client through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get receiver count for a client'. Jentic returns the matching CleverReach API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the CleverReach API have?

The CleverReach API exposes 22 endpoints covering clients, groups, receivers operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which CleverReach operations and credentials the agent may use. Since the CleverReach API carries the client id in the URL path (/v3/clients/{id}/...), you can pin the agent to a single client and allow only read calls such as receiver count, subscription plan, and available sending quota. Higher-impact operations like creating a new account within an agency stay off-limits unless you explicitly add them.

Rest Cleverreach CleverReach API

Name: CleverReach API
Brand: CleverReach API
Availability: InStock

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer22 EndpointsREST

For Agents

Programmatically get receiver count for a client, get active receiver count for a client. Covers 22 operations with bearer authentication.

Use for: I need to receiver count for a client, I want to active receiver count for a client, Search for available mail sending quota, Find all client billing address

Not supported: Does not handle payments, communications, or crm - use for marketing only.

CleverReach email marketing REST API for managing clients, groups, receivers, mailings, blacklists, and forms. The API exposes 22 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

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

17%

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

75%

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

59%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CleverReach API to your agent

Capabilities

Start building with CleverReach API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rest Cleverreach CleverReach API

Jentic AI Readiness Score

CleverReach 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