Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Campaigner 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%2Fcampaigner.com%2Fcampaigner" | shStep 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%2Fcampaigner.com%2Fcampaigner" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Campaigner API.
Send individual SMS and MMS messages to a recipient phone number
Create, schedule, and cancel email campaigns for a contact list
Build segmented contact lists with custom fields and signup forms
Import, update, and upsert contact records in bulk
Launch SMS campaigns and read their per-recipient sends and tracked links
GET STARTED
Export account contacts over sFTP for downstream processing
List the automated marketing workflows configured on an account
Patterns agents use Campaigner API for, with concrete tasks.
★ AI Agent Campaign Automation
An AI agent connected through Jentic can run a full email or SMS campaign on request: it creates the campaign, sets the recipient list, schedules the send, and reports back the delivery and tracked-link results. Campaigner handles list segmentation, send scheduling, and link tracking so the agent coordinates the sequence instead of wiring each step by hand.
Create an email campaign, set its recipient list, schedule it to send in one hour, and confirm the campaign is queued
Transactional SMS and MMS Notifications
Send order confirmations, reminders, and alerts as individual SMS or MMS messages. Campaigner delivers each message to a single recipient and records the send for later reporting, which suits one-off notifications triggered by application events.
Send a single SMS reminder to a customer phone number and verify the send was accepted
Contact List Management
Keep marketing audiences current by importing new contacts, upserting changed records, and organizing them into segmented lists with custom fields. Campaigner supports bulk contact import and signup-form capture so audience hygiene stays current without manual edits.
Import a batch of contacts with email addresses and custom field values into a named list
Campaign Performance Tracking
Pull the sends and tracked links for a specific email or SMS campaign to measure reach and engagement. Campaigner exposes per-campaign send records and clicked-link data that feed reporting dashboards.
Retrieve the tracked links and send records for a given SMS campaign and summarize the click counts
45 endpoints — the campaigner api sends email, sms, and mms marketing campaigns to your contact lists and tracks every send and clicked link.
METHOD
PATH
DESCRIPTION
/sms/v1/send/single
Send a single SMS
/mms/v1/send/single
Send a single MMS
/email/v1/campaign
Create an email campaign
/sms/v1/campaign
Create an SMS campaign
/contacts/v1
Create a contact
/contacts/v1
List contacts for an account
/lists/v1
Create a contact list
/workflows/v1
List automated workflows
/sms/v1/send/single
Send a single SMS
/mms/v1/send/single
Send a single MMS
/email/v1/campaign
Create an email campaign
/sms/v1/campaign
Create an SMS campaign
/contacts/v1
Create a contact
/contacts/v1
List contacts for an account
/lists/v1
Create a contact list
/workflows/v1
List automated workflows
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Campaigner by hand means setting up its IntegrationKey header auth and tracking the right versioned paths for SMS, email, contacts, and exports yourself. Through Jentic you install once, import Campaigner from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which Campaigner operations the agent may call, such as sending an SMS or creating an email campaign, so higher-risk operations like deleting contacts or lists are not included unless you add them.
Credential isolation
Your Campaigner IntegrationKey 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 'send an SMS' or 'create an email campaign', and Jentic returns the matching Campaigner operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Campaigner API through Jentic.
What authentication does the Campaigner API use?
The Campaigner API authenticates with an API key sent in the `IntegrationKey` request header, per its OpenAPI spec. You generate the key from your Campaigner account, and through Jentic it is stored encrypted by your own Jentic One instance and injected when the agent makes a call, so it never appears in the agent's prompt or logs.
Can I send both SMS and email with the Campaigner API?
Yes. The API exposes separate operations for sending single SMS and MMS messages and for creating, scheduling, and sending email campaigns to a contact list. You can also launch SMS campaigns and read their per-recipient sends and tracked links for reporting.
Can I manage contact lists with the Campaigner API?
Yes. You can create lists, add and segment contacts, define custom fields, and import or upsert contact records in bulk. Signup-form capture and sFTP contact exports are also available for keeping audiences current.
Is there a Campaigner MCP server?
You do not need an MCP server to give your agent the Campaigner API. Jentic connects it directly from the API Directory: import Campaigner, store your IntegrationKey once, and your agent sends messages and runs campaigns through the operations the API already exposes. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.
Can I limit what my agent is allowed to do with the Campaigner API?
Yes. Write a rule that allows only the operations the agent needs, for example sending an SMS and creating an email campaign, and leave out higher-risk ones like deleting contacts or lists. The agent can then run campaigns while the actions you excluded stay unavailable, and every call it makes is logged.
How do I send an SMS through Jentic with the Campaigner API?
Search Jentic for 'send an SMS', which returns the Campaigner single-SMS operation with its input schema, then supply the recipient number and message body and the agent runs it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Send email, SMS, and MMS campaigns, manage segmented contact lists and custom fields, and read per-campaign sends and tracked links through the Campaigner API.
Use for: Send a single SMS to a customer's phone number, Create and schedule an email campaign for my subscriber list, Import a batch of contacts with custom field values, Find all sends for a specific SMS campaign
Not supported: Does not handle payment processing, CRM deal tracking, or push notifications. Use for email, SMS, and MMS marketing campaigns only.
The Campaigner API sends email, SMS, and MMS marketing campaigns to your contact lists and tracks every send and clicked link. It manages contacts, custom fields, segmented lists, and signup forms, and can import or upsert contact data in bulk. Automated marketing workflows, category tagging, and sFTP contact exports round out the account-level campaign surface.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>