Install Jentic One Beta

Connect the Sendiio API to your agent

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

Check credentials

Subscribe to list (JSON)

Unsubscribe email

Get email list

Monitor Sendiio API operational status and events

Use Cases

GET STARTED

Start building with Sendiio API

Explore with Jentic One

View OpenAPI Document

Automated Authentication Management

Automate authentication operations by combining multiple Sendiio API endpoints. Agents can subscribe to list (json) and then subscribe to list (redirect) in a single workflow.

Call POST /lists/subscribe/json to subscribe to list (json), then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sendiio 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 'check credentials', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

22 endpoints — sendiio is an email and sms marketing platform.

METHOD

PATH

DESCRIPTION

POST

/auth/check

Check credentials

POST

/lists/subscribe/json

Subscribe to list (JSON)

POST

/lists/subscribe

Subscribe to list (redirect)

POST

/lists/{encryptedId}/unsubscribe

Unsubscribe email

POST

/lists/phone/{encryptedId}/unsubscribe

Unsubscribe phone

GET

/lists/email/{encryptedId}

Get email list

GET

/lists/phone/{encryptedId}

Get phone list

GET

/lists/email

Get all email lists

POST

/auth/check

Check credentials

POST

/lists/subscribe/json

Subscribe to list (JSON)

POST

/lists/subscribe

Subscribe to list (redirect)

POST

/lists/{encryptedId}/unsubscribe

Unsubscribe email

POST

/lists/phone/{encryptedId}/unsubscribe

Unsubscribe phone

GET

/lists/email/{encryptedId}

Get email list

GET

/lists/phone/{encryptedId}

Get phone list

GET

/lists/email

Get all email lists

Why Jentic?

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

Setup

Wiring the Sendiio API by hand means setting up its dual header auth, sending both the token and secret headers on every request against sendiio.com/api/v1, and handling status codes yourself. Through Jentic you install once, import the Sendiio API from the API Directory, store the token and secret once, and your agent calls it.

Permission scoping

The Sendiio API puts the list id in the URL path (/lists/email/{encryptedId} and /lists/phone/{encryptedId}), so a rule can pin your agent to one list. You choose the operations it may call, so ones like unsubscribing a contact are not included unless you add them.

Credential isolation

Your Sendiio token and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'subscribe a contact to an email list', and Jentic returns the matching Sendiio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sendiio API through Jentic.

What authentication does the Sendiio API use?

The Sendiio API uses an API key passed in the `token` 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 check credentials with the Sendiio API?

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

What are the rate limits for the Sendiio 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 check credentials through Jentic?

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

How many endpoints does the Sendiio API have?

The Sendiio API exposes 22 endpoints covering authentication, fields, forms operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendiio operations the agent may call, so you can allow it to subscribe a contact to a list while withholding operations like unsubscribing an email or phone number. The Sendiio API carries the list id in the URL path, as in /lists/email/{encryptedId} and /lists/phone/{encryptedId}, so a rule can pin the agent to one specific list. Your token and secret are held by your own Jentic One instance and injected only for the calls you have permitted.

Sendiio API

Name: Sendiio API
Brand: Sendiio API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey22 EndpointsREST

For Agents

Programmatically check credentials, subscribe to list (json). Covers 22 operations with apiKey authentication.

Use for: I need to check credentials, I want to subscribe to list (json), Search for subscribe to list (redirect), Find all unsubscribe email

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

Sendiio is an email and SMS marketing platform. The API provides endpoints for managing lists, forms, fields, sequences, webhooks, and authentication. The API exposes 22 endpoints secured with apiKey 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).

75%

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.

49%

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

45%

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

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 Sendiio API to your agent

Capabilities

Use Cases

Start building with Sendiio API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sendiio API

Jentic AI Readiness Score

Sendiio 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