Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SendMsg 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%2Fsendmsg.com%2Fsendmsg" | 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%2Fsendmsg.com%2Fsendmsg" | 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 SendMsg API.
Send Message
List Messages
Get Message
Create Contact
Monitor SendMsg API operational status and events
GET STARTED
Patterns agents use SendMsg API for, with concrete tasks.
★ CRM Operations
Use the SendMsg API to perform crm operations programmatically. The API provides 13 endpoints covering core functionality including send message, list messages, get message.
Call POST /messages to send message
Automated Messages Management
Automate messages operations by combining multiple SendMsg API endpoints. Agents can list messages and then get message in a single workflow.
Call GET /messages to list messages, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SendMsg 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 'send message', load the operation schema, and execute with Jentic-managed credentials
13 endpoints — sendmsg is an sms messaging platform.
METHOD
PATH
DESCRIPTION
/messages
Send Message
/messages
List Messages
/messages/{message_id}
Get Message
/messages/bulk
Send Bulk Messages
/contacts
Create Contact
/contacts
List Contacts
/contacts/{contact_id}
Get Contact
/contacts/{contact_id}
Update Contact
/messages
Send Message
/messages
List Messages
/messages/{message_id}
Get Message
/messages/bulk
Send Bulk Messages
/contacts
Create Contact
/contacts
List Contacts
/contacts/{contact_id}
Get Contact
/contacts/{contact_id}
Update Contact
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SendMsg API by hand means setting up its X-API-Key header auth against api.sendmsg.com/v4 and handling status codes yourself. Through Jentic you install once, import the SendMsg API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The SendMsg API puts the message and contact ids in the URL path (/messages/{message_id} and /contacts/{contact_id}), so a rule can pin your agent to one contact or message. You choose the operations it may call, so ones that change state like updating a contact are not included unless you add them.
Credential isolation
Your SendMsg 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 'send a message to a contact', and Jentic returns the matching SendMsg operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using SendMsg API through Jentic.
What authentication does the SendMsg API use?
The SendMsg 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 send message with the SendMsg API?
Yes. Use the POST /messages endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SendMsg 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 send message through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send message'. Jentic returns the matching SendMsg API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SendMsg API have?
The SendMsg API exposes 13 endpoints covering messages, contacts, campaigns operations.
Can I limit what my agent is allowed to do with the SendMsg API?
Yes. Because you run Jentic One yourself, your own rules decide which SendMsg operations and credentials the agent may use. Since the API puts message and contact ids in the URL path, such as /messages/{message_id} and /contacts/{contact_id}, you can pin the agent to a single contact or message. You also pick the operations it can call, so state-changing ones like updating a contact stay out of reach unless you grant them.
For Agents
Programmatically send message, list messages. Covers 13 operations with apiKey authentication.
Use for: I need to send message, I want to messages, Search for message, Find all send bulk messages
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
SendMsg is an SMS messaging platform. The API provides access to SMS sending, delivery tracking, contacts, and messaging campaigns. The API exposes 13 endpoints secured with apiKey authentication.
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>