Install Jentic One Beta

Connect the MSG91 API to your agent

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

Send and verify one-time passwords across SMS and email channels via /v5/otp and /v5/otp/verify

Trigger transactional flow templates with dynamic variables via POST /v5/flow

Pull SMS delivery logs and analytics via /v5/report/sms/logs and /v5/report/sms/analytics

Run multi-channel campaigns through the Campaign and Segmento endpoints

Send and track WhatsApp template messages and inbound replies

GET STARTED

Start building with MSG91 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MSG91 API for, with concrete tasks.

★ OTP-Based Login and Signup

Consumer apps issue one-time passwords during signup and login to verify phone ownership without storing passwords. MSG91's /v5/otp endpoint sends the code, /v5/otp/verify validates the user's input, and /v5/otp/retry reissues if the SMS is missed. The dedicated OTP routing tier delivers in seconds across Indian carriers, which is why the same flow powers most fintech and ride-hailing onboarding stacks in the region.

Call POST /v5/otp with the user's mobile number, then call GET /v5/otp/verify with the submitted code and reject the signup if the response indicates a mismatch.

Transactional SMS Flows for Order Updates

E-commerce and logistics platforms send order-confirmed, out-for-delivery, and delivered notifications as transactional SMS. MSG91's /v5/flow templates accept dynamic variables, so a single approved DLT template covers every order without per-message content review. The /v5/report/sms/logs endpoint exposes delivery state for reconciliation against the order pipeline.

Call POST /v5/flow with the approved template id and the order variables, then audit deliveries via POST /v5/report/sms/logs filtered to that flow id.

WhatsApp Template Notifications

Customer engagement teams send WhatsApp template messages - appointment reminders, shipping notifications, invoice receipts - through the MSG91 WhatsApp integration. Templates are pre-approved with Meta and the API attaches dynamic variables at send time. This is the primary channel for high-engagement notifications where SMS deliverability or open rates are insufficient.

Send a 'shipment_dispatched' WhatsApp template to the customer's number with order id and tracking link as template variables.

Agent-Driven Multi-Channel Outreach

An AI agent runs an outreach playbook that escalates from email to SMS to WhatsApp until the recipient engages. Through Jentic the agent searches for 'send a transactional sms', 'send a whatsapp template', and 'send an email' and gets a single auth flow across MSG91's email, SMS, and WhatsApp endpoints. Channel fallback is one configuration step instead of three integrations.

Search Jentic for 'send a transactional sms', execute POST /v5/flow, and on no-engagement after 24 hours fall back to a WhatsApp template send through the same agent flow.

Key Endpoints

76 endpoints — msg91 is an india-headquartered cloud communications platform that exposes sms, otp, email, whatsapp, rcs, and voice messaging through a single api alongside segmento contact management and campaign tooling.

METHOD

PATH

DESCRIPTION

POST

/v5/otp

Issue a one-time password to a phone number

GET

/v5/otp/verify

Verify a submitted OTP

POST

/v5/flow

Trigger a transactional flow template

POST

/v5/report/sms/logs

Pull SMS delivery logs

GET

/v5/report/sms/analytics

Retrieve SMS analytics aggregates

GET

/v5/report/otp/analytics

Retrieve OTP analytics aggregates

POST

/v5/otp

Issue a one-time password to a phone number

GET

/v5/otp/verify

Verify a submitted OTP

POST

/v5/flow

Trigger a transactional flow template

POST

/v5/report/sms/logs

Pull SMS delivery logs

GET

/v5/report/sms/analytics

Retrieve SMS analytics aggregates

GET

/v5/report/otp/analytics

Retrieve OTP analytics aggregates

Why Jentic?

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

Setup

Wiring MSG91 by hand means setting your authkey in the authkey header, choosing between its two hosts, and learning the channel-specific path conventions for OTP, SMS, and flow calls. Through Jentic you install once, import the MSG91 API from the API Directory, store the authkey once, and your agent calls it.

Permission scoping

MSG91 carries its targets in the request body and query rather than a resource path, so limit the agent to the operations it needs, such as sending an OTP or reading analytics. You choose the operations it may call, so it stays within the messaging actions you allow.

Credential isolation

Your MSG91 authkey is stored once, encrypted, by your own Jentic One instance and injected into the authkey header 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 OTP' or 'send a WhatsApp template', and Jentic returns the matching MSG91 operation with its input schema, so the agent calls the right endpoint without learning the channel-specific path conventions.

FAQs

Specific to using MSG91 API through Jentic.

What authentication does the MSG91 API use?

The MSG91 API uses an API key passed in the authkey header. Through Jentic the authkey is stored encrypted in the vault and injected at request time, so it never appears in the agent's prompt context.

Can I send and verify OTPs in one workflow?

Yes. POST /v5/otp issues the code to the supplied mobile number and GET /v5/otp/verify validates the user's submitted code. /v5/otp/retry resends the code if the user does not receive the first message.

What are the rate limits for the MSG91 API?

MSG91 enforces channel-specific throughput tied to your account class - DLT-approved transactional SMS routes burst higher than promotional routes, and WhatsApp respects the Meta tier on your number. Spread campaign sends across the /v5/flow endpoint with batching to avoid throttling.

How do I trigger a transactional SMS flow through Jentic?

Search Jentic for 'send a transactional sms', load the /v5/flow schema, and execute POST /v5/flow with the approved DLT template id and your variables. The agent receives the delivery acknowledgment without ever holding the authkey.

Is the MSG91 API free?

MSG91 offers free trial credits for evaluation but production use is metered per channel - SMS by sender route and country, WhatsApp by Meta conversation tier, voice per minute. Check the dashboard for active rates before launching a campaign.

Does MSG91 support WhatsApp templates?

Yes. The WhatsApp endpoints send pre-approved templates with dynamic variables and ingest inbound replies on the configured webhook. Approval flows through Meta's Business Manager and templates appear in the dashboard once live.

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

Yes. Because you run Jentic One yourself, your own rules decide which MSG91 operations and credentials the agent may use, so you can allow only the actions it needs, such as issuing an OTP with POST /v5/otp or reading SMS analytics via GET /v5/report/sms/analytics. MSG91 carries its targets in the request body and query rather than a resource path, so scoping happens at the operation level: you can permit sending a transactional flow through POST /v5/flow while withholding campaign or WhatsApp sends. Any operation you do not grant stays unavailable to the agent, and the authkey is injected at request time rather than exposed to it.

MSG91 API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsSms MessagingapiKey76 EndpointsREST

For Agents

Send SMS, email, WhatsApp, and voice messages, run OTP verification, and manage contact campaigns through MSG91's multi-channel communications API.

Use for: I need to send a one-time password to a phone number for login, Verify the OTP code a user just submitted, Send a WhatsApp template message to a customer, Pull the delivery analytics for an SMS campaign

Not supported: Does not handle CRM lead management, payments, or live agent helpdesk routing - use for outbound multi-channel messaging and OTP verification only.

MSG91 is an India-headquartered cloud communications platform that exposes SMS, OTP, Email, WhatsApp, RCS, and Voice messaging through a single API alongside Segmento contact management and campaign tooling. The API covers transactional flows like one-time-password issue and verify, marketing campaign sends, contact list management, and per-channel analytics. Across 76 operations it consolidates multi-channel customer messaging behind one authkey-based authentication model.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

97%

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

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: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

39%

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: ASignals: 1

90%

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

Capabilities

Start building with MSG91 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MSG91 API

Jentic AI Readiness Score

MSG91 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