Install Jentic One Beta

Connect the SendPulse API to your agent

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

Obtain an OAuth 2.0 access token

Get account information

Create a mailing list

Query and filter SendPulse API records by parameters

Monitor SendPulse API operational status and events

GET STARTED

Start building with SendPulse API

Explore with Jentic One

View OpenAPI Document

Automated Authentication Management

Automate authentication operations by combining multiple SendPulse API endpoints. Agents can get account information and then get team members details in a single workflow.

Call GET /user/info to get account information, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SendPulse 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 'obtain an oauth 2.0 access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

23 endpoints — sendpulse rest api for email marketing, mailing lists, campaigns, and account management.

METHOD

PATH

DESCRIPTION

POST

/oauth/access_token

Obtain an OAuth 2.0 access token

GET

/user/info

Get account information

GET

/user/invited-users-list

Get team members details

GET

/user/balance/detail

Get detailed balance information

POST

/addressbooks

Create a mailing list

GET

/addressbooks

Get all mailing lists

GET

/addressbooks/{id}

Get mailing list info

PUT

/addressbooks/{id}

Edit a mailing list

POST

/oauth/access_token

Obtain an OAuth 2.0 access token

GET

/user/info

Get account information

GET

/user/invited-users-list

Get team members details

GET

/user/balance/detail

Get detailed balance information

POST

/addressbooks

Create a mailing list

GET

/addressbooks

Get all mailing lists

GET

/addressbooks/{id}

Get mailing list info

PUT

/addressbooks/{id}

Edit a mailing list

Why Jentic?

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

Setup

Wiring SendPulse by hand means exchanging your client credentials at /oauth/access_token for a bearer token, refreshing it as it expires, and threading it onto every marketing call yourself. Through Jentic you install once, import SendPulse from the API Directory, store the token once, and your agent calls it.

Permission scoping

SendPulse puts the address book id in the URL path (/addressbooks/{id}/...), so a rule can pin your agent to one address book: it can read and update contacts there and nothing else. You choose the operations it may call, so a book-level delete is not included unless you add it.

Credential isolation

Your SendPulse 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 'create an address book' or 'get account balance', and Jentic returns the matching SendPulse operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SendPulse API through Jentic.

What authentication does the SendPulse API use?

The SendPulse 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 obtain an oauth 2.0 access token with the SendPulse API?

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

What are the rate limits for the SendPulse 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 obtain an oauth 2.0 access token through Jentic?

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

How many endpoints does the SendPulse API have?

The SendPulse API exposes 23 endpoints covering authentication, account, mailinglists operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SendPulse operations and credentials the agent may use. Since SendPulse puts the address book id in the URL path (/addressbooks/{id}/...), you can pin the agent to a single address book so it reads and updates contacts there and touches nothing else. You choose the operations it can call, so a book-level delete stays out of reach unless you explicitly add it.

SendPulse API

Name: SendPulse API
Brand: SendPulse API
Availability: InStock

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer23 EndpointsREST

For Agents

Programmatically obtain an oauth 2.0 access token, get account information. Covers 23 operations with bearer authentication.

Use for: I need to obtain an oauth 2.0 access token, I want to account information, Search for team members details, Find all detailed balance information

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

SendPulse REST API for email marketing, mailing lists, campaigns, and account management. The API exposes 23 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: DSignals: 4

16%

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.

61%

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

60%

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

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SendPulse API to your agent

Capabilities

Start building with SendPulse API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

SendPulse API

Jentic AI Readiness Score

SendPulse 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