For Agents
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sailthru (Engage by Marigold) 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Sailthru (Engage by Marigold) API.
Send a one-off transactional email to a single user with a chosen template
Schedule a blast campaign to a named subscriber list with a chosen send-time
Update a user profile with custom variables that downstream templates render
GET STARTED
Send transactional and campaign email through Sailthru, manage subscriber lists and templates, and read user profiles so an agent can drive personalised lifecycle email.
Use for: Send a welcome email to a user via Sailthru, Schedule a campaign blast to my newsletter list for tomorrow morning, Update a user profile with a new lifetime-value variable, Add a user to the active-subscribers list
Not supported: Does not handle SMS, push notifications, or paid advertising — use for email sends, lists, templates, and Sailthru user profiles only.
Jentic publishes the only available OpenAPI specification for Sailthru (Engage by Marigold) API, keeping it validated and agent-ready. Sailthru, now part of Marigold, is a customer engagement platform focused on personalised email marketing, user profiles, and lifecycle campaigns. The API exposes 13 endpoints across blasts, lists, sends, templates, and user data, letting an agent send transactional or campaign email, manage subscriber lists, look up profiles, and orchestrate templated content. It is well-suited to media and retail brands who already store user state in Sailthru and want to drive sends from external systems.
Add or remove a user from a subscriber list to keep segments accurate
Manage email templates including content, subject line, and from address
Look up a user by email and inspect their lifecycle state in Sailthru
Patterns agents use Sailthru (Engage by Marigold) API for, with concrete tasks.
★ Triggered Lifecycle Emails
Drive transactional and lifecycle emails from product events such as sign-up, purchase, or abandoned cart by calling Sailthru's send endpoint with the user's email and a chosen template. Sailthru renders personalisation variables server-side using the user's profile, so the calling system only needs to supply the trigger context. Lifecycle teams pair this with profile updates to keep template variables fresh.
Update the Sailthru user profile for jane@example.com with last_purchase_amount=49.99, then call /send with template=post-purchase-thanks for that user.
Campaign Scheduling for Editorial Teams
Editorial teams compose a daily or weekly newsletter and schedule it to a Sailthru list at the correct send-time without logging into the dashboard. The /blast endpoint accepts subject, list, content, and schedule fields in one call, which lets a CMS or workflow tool publish the newsletter the moment editorial sign-off lands. This compresses the publish-and-schedule loop into a single API request.
Create a Sailthru blast targeting list=daily-newsletter with subject=Today's Headlines, html_body from the CMS export, scheduled for 2026-06-12 06:00 UTC.
Profile-Synchronised Segmentation
Keep Sailthru user profiles in lockstep with the source-of-truth customer record so segmentation stays accurate. The /user endpoint accepts arbitrary key-value variables which downstream lists, templates, and lifecycle campaigns can target. Marketing operations teams use this to push attributes such as plan tier, churn risk, or product preferences into Sailthru on a recurring schedule.
Iterate over the daily customer-attribute changeset and call /user for each email with the updated plan_tier and churn_risk variables.
Agent-Driven Re-Engagement
Hand a retention agent the ability to identify lapsed users in a list, build a personalised re-engagement send, and execute it through Sailthru without a human marketer. By calling Sailthru through Jentic the agent searches by intent, loads the schema for /list and /send, and chains the operations safely. This lifts re-engagement campaigns out of the marketer's manual queue and into autonomous execution.
Pull the lapsed-90d list from Sailthru, send each user a /send call with template=we-miss-you, and log the resulting send IDs.
13 endpoints — jentic publishes the only available openapi specification for sailthru (engage by marigold) api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/send
Send a templated email to a single user
/blast
Schedule a campaign blast to a list
/list
Manage a subscriber list and its members
/template
Create or update an email template
Look up or update a user by email address
/send
Send a templated email to a single user
/blast
Schedule a campaign blast to a list
/list
Manage a subscriber list and its members
/template
Create or update an email template
Look up or update a user by email address
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Sailthru api_key and shared secret are stored encrypted in the Jentic vault. Jentic computes the api_sig HMAC-MD5 signature server-side per request, so the agent never holds the secret and never has to implement signing.
Intent-based discovery
Agents search by intent (e.g. 'send a templated email') and Jentic returns the matching Sailthru operation with the parameter schema for template name, recipient, and variables.
Time to first call
Direct Sailthru integration: 1-2 days handling the api_sig signing, retry logic, and template variable contracts. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Sailthru (Engage by Marigold) API through Jentic.
Why is there no official OpenAPI spec for Sailthru (Engage by Marigold) API?
Marigold does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Sailthru (Engage by Marigold) API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Sailthru API use?
Sailthru uses an API key plus an HMAC-MD5 signature over the request payload, sent as api_key and api_sig query parameters. Through Jentic both values are computed server-side from credentials in the vault, so the agent never handles the secret or the signing logic.
Can I send a transactional email with the Sailthru API?
Yes. POST to /send with the recipient's email, a template name, and any custom variables; Sailthru renders the template server-side using the recipient's user profile and queues the send.
What are the rate limits for the Sailthru API?
Sailthru does not publish hard rate limits in this spec; in practice plans throttle bulk send and profile-update calls. If you receive a 429 from /send or /user, back off exponentially before retrying through Jentic.
How do I schedule a campaign blast through Jentic?
Search Jentic for schedule a Sailthru blast, load the schema for /blast, and execute with list, subject, html_body, and schedule_time. Jentic returns the new blast id which you can poll back for status.
Can I update user profile variables in bulk?
The /user endpoint updates a single profile per call; for bulk updates loop the call across the changeset and pace the requests. Each call accepts an arbitrary vars object so a single request can set many attributes at once.