Install Jentic One Beta

Connect the SendX REST API to your agent

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

Get all contacts

Manage marketing data programmatically

Integrate SendX REST API into automated workflows

Query and filter SendX REST API records by parameters

Monitor SendX REST API operational status and events

GET STARTED

Start building with SendX REST API

Explore with Jentic One

View OpenAPI Document

Automated Campaigns Management

Automate campaigns operations by combining multiple SendX REST API endpoints. Agents can get all campaigns and then get all tags in a single workflow.

Call GET /campaign to get all campaigns, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SendX REST 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 'get all contacts', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — sendx rest api for managing contacts, campaigns, tags, lists, senders, and webhooks for email marketing and marketing automation.

METHOD

PATH

DESCRIPTION

GET

/contact

Get all contacts

GET

/campaign

Get all campaigns

GET

/tag

Get all tags

GET

/list

Get all contact lists

GET

/sender

Get all verified sender addresses

GET

/webhook

Get all webhooks

GET

/contact

Get all contacts

GET

/campaign

Get all campaigns

GET

/tag

Get all tags

GET

/list

Get all contact lists

GET

/sender

Get all verified sender addresses

GET

/webhook

Get all webhooks

Why Jentic?

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

Setup

Wiring SendX by hand means setting the X-Team-ApiKey header on every request and handling its contact, campaign, and list calls yourself. Through Jentic you install once, import SendX from the API Directory, store the key once, and your agent calls it.

Permission scoping

SendX exposes collection-level endpoints for contacts, campaigns, tags, and lists, so limit the agent to the operations it needs, such as listing contacts or reading campaigns. You choose the operations it may call, so it holds only the read access you grant.

Credential isolation

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

FAQs

Specific to using SendX REST API through Jentic.

What authentication does the SendX REST API use?

The SendX REST API uses an API key passed in the `X-Team-ApiKey` 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 all contacts with the SendX REST API?

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

What are the rate limits for the SendX REST 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 all contacts through Jentic?

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

How many endpoints does the SendX REST API have?

The SendX REST API exposes 6 endpoints covering campaigns, contacts, lists operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SendX operations and credentials the agent may use. SendX exposes collection-level endpoints for contacts, campaigns, tags, lists, senders, and webhooks, so you can restrict the agent to just the calls it needs, such as GET /contact or GET /campaign, and withhold the rest. Since these are read operations, the agent holds only the read access you explicitly grant.

SendX REST API

Name: SendX REST API
Brand: SendX REST API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail MarketingapiKey6 EndpointsREST

For Agents

Programmatically get all contacts, get all campaigns. Covers 6 operations with apiKey authentication.

Use for: I need to all contacts, I want to all campaigns, Search for all tags, Find all all contact lists

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

SendX REST API for managing contacts, campaigns, tags, lists, senders, and webhooks for email marketing and marketing automation. The API exposes 6 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

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.

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

53%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SendX REST API to your agent

Capabilities

Start building with SendX REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

SendX REST API

Jentic AI Readiness Score

SendX REST 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