Install Jentic One Beta

Connect the Remindlo SMS Reminder API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Remindlo SMS Reminder 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%2Fremindlo.co.uk%2Fremindlo" | 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%2Fremindlo.co.uk%2Fremindlo" | 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 Remindlo SMS Reminder API.

List campaigns

Create or update contact

Get contact

Enroll in campaign

Send SMS message

Use Cases

GET STARTED

Start building with Remindlo SMS Reminder API

Explore with Jentic One

View OpenAPI Document

Automated Campaigns Management

Automate campaigns operations by combining multiple Remindlo SMS Reminder API endpoints. Agents can create or update contact and then list contacts in a single workflow.

Call POST /contacts to create or update contact, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Remindlo SMS Reminder 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 'list campaigns', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — sms reminder and campaign management api for automated customer communications.

METHOD

PATH

DESCRIPTION

GET

/campaigns

List campaigns

POST

/contacts

Create or update contact

GET

/contacts

List contacts

GET

/contacts/{id}

Get contact

POST

/campaigns-enroll

Enroll in campaign

POST

/messages

Send SMS message

GET

/campaigns

List campaigns

POST

/contacts

Create or update contact

GET

/contacts

List contacts

GET

/contacts/{id}

Get contact

POST

/campaigns-enroll

Enroll in campaign

POST

/messages

Send SMS message

Why Jentic?

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

Setup

Wiring Remindlo by hand means sending its sk_live x-api-key header to api.remindlo.co.uk and mapping its campaign, contact, and message endpoints yourself. Through Jentic you install once, import Remindlo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Remindlo puts the contact id in the URL path (/contacts/{id}), so a rule can pin your agent to reading one contact and listing campaigns. You choose the operations it may call, so sending messages or enrolling contacts in campaigns is not included unless you add them.

Credential isolation

Your Remindlo 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 'list campaigns' or 'look up a contact', and Jentic returns the matching Remindlo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Remindlo SMS Reminder API through Jentic.

What authentication does the Remindlo SMS Reminder API use?

The Remindlo SMS Reminder API uses an API key passed in the `x-api-key` 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 list campaigns with the Remindlo SMS Reminder API?

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

What are the rate limits for the Remindlo SMS Reminder 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 list campaigns through Jentic?

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

How many endpoints does the Remindlo SMS Reminder API have?

The Remindlo SMS Reminder API exposes 6 endpoints covering campaigns, contacts, messages operations.

Can I limit what my agent is allowed to do with the Remindlo SMS Reminder API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Remindlo operations and credentials the agent may use. Because Remindlo puts the contact id in the URL path (/contacts/{id}), you can pin the agent to read a single contact and list campaigns while withholding write operations. Sending SMS messages (POST /messages) or enrolling contacts in campaigns (POST /campaigns-enroll) stays off limits unless you explicitly add those operations.

Remindlo SMS Reminder API

Name: Remindlo SMS Reminder API
Brand: Remindlo SMS Reminder API
Availability: InStock

AI ReadinessAI-Aware (B)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing AutomationapiKey6 EndpointsREST

For Agents

Programmatically list campaigns, create or update contact. Covers 6 operations with apiKey authentication.

Use for: I need to campaigns, I want to or update contact, Search for contacts, Find all contact

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

SMS reminder and campaign management API for automated customer communications. The API exposes 6 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: ASignals: 4

99%

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

42%

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

21%

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.

55%

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 Remindlo SMS Reminder API to your agent

Capabilities

Use Cases

Start building with Remindlo SMS Reminder API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Remindlo SMS Reminder API

Jentic AI Readiness Score

Remindlo SMS Reminder 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