Install Jentic One Beta

Connect the Sendcrux API to your agent

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

Create campaign

List campaigns

Get campaign

Query and filter Sendcrux API records by parameters

Monitor Sendcrux API operational status and events

GET STARTED

Start building with Sendcrux API

Explore with Jentic One

View OpenAPI Document

Automated Campaigns Management

Automate campaigns operations by combining multiple Sendcrux API endpoints. Agents can list campaigns and then get campaign in a single workflow.

Call GET /campaigns to list campaigns, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sendcrux 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 apiKey tokens manually.

Search Jentic for 'create campaign', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — cold email outreach and automation platform api for managing email campaigns, domain warm-up, and deliverability.

METHOD

PATH

DESCRIPTION

POST

/campaigns

Create campaign

GET

/campaigns

List campaigns

GET

/campaigns/{id}

Get campaign

POST

/contacts

Create contact

GET

/contacts

List contacts

POST

/campaigns

Create campaign

GET

/campaigns

List campaigns

GET

/campaigns/{id}

Get campaign

POST

/contacts

Create contact

GET

/contacts

List contacts

Why Jentic?

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

Setup

Wiring the Sendcrux API by hand means learning its X-API-Key header auth, calling api.sendcrux.com/v1, and managing campaign and contact payloads yourself. Through Jentic you install once, import the Sendcrux API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Sendcrux puts the campaign id in the URL path (/campaigns/{id}), so a rule can pin your agent to reading one campaign. You choose the operations it may call, so campaign or contact creation is not included unless you add it.

Credential isolation

Your Sendcrux API 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 campaign' or 'list contacts', and Jentic returns the matching Sendcrux API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sendcrux API through Jentic.

What authentication does the Sendcrux API use?

The Sendcrux API uses an API key passed in the `X-API-Key` 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 create campaign with the Sendcrux API?

Yes. Use the POST /campaigns endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Sendcrux 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 create campaign through Jentic?

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

How many endpoints does the Sendcrux API have?

The Sendcrux API exposes 5 endpoints covering campaigns, contacts operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendcrux operations and credentials the agent may use. You can allow it to only list or get campaigns (GET /campaigns and GET /campaigns/{id}) while leaving campaign and contact creation (POST /campaigns, POST /contacts) off the allowed list. Since Sendcrux puts the campaign id in the URL path, a rule can even pin the agent to reading a single campaign.

Sendcrux API

Name: Sendcrux API
Brand: Sendcrux API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Community OpenAPI document · agent-readyMarketingEmail MarketingapiKey5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically create campaign, list campaigns. Covers 5 operations with apiKey authentication.

Use for: I need to campaign, I want to campaigns, Search for campaign, Find all contact

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

Cold email outreach and automation platform API for managing email campaigns, domain warm-up, and deliverability. The API exposes 5 endpoints secured with apiKey authentication.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

35%

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

26%

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.

62%

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).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Sendcrux API to your agent

Capabilities

Start building with Sendcrux API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sendcrux API

Jentic AI Readiness Score

Sendcrux 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