Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Textmagic 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%2Ftextmagic.com%2Ftextmagic" | 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%2Ftextmagic.com%2Ftextmagic" | 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 Textmagic API.
Send message
List messages
Get message
Delete message
Monitor Textmagic API operational status and events
GET STARTED
Patterns agents use Textmagic API for, with concrete tasks.
★ Communications Operations
Use the Textmagic API to perform communications operations programmatically. The API provides 36 endpoints covering core functionality including send message, list messages, get message.
Call POST /messages to send message
Automated Contacts Management
Automate contacts operations by combining multiple Textmagic 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 Textmagic 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
36 endpoints — textmagic sms messaging api.
METHOD
PATH
DESCRIPTION
/messages
Send message
/messages
List messages
/messages/{id}
Get message
/messages/{id}
Delete message
/messages/price
Get message price
/replies
List replies
/sessions
List sessions
/sessions/{id}
Get session
/messages
Send message
/messages
List messages
/messages/{id}
Get message
/messages/{id}
Delete message
/messages/price
Get message price
/replies
List replies
/sessions
List sessions
/sessions/{id}
Get session
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Textmagic by hand means setting its X-TM-Key header on every request to rest.textmagic.com and handling the messaging endpoints yourself. Through Jentic you install once, import Textmagic from the API Directory, store the key once, and your agent calls it.
Permission scoping
Textmagic puts the message id in the URL path (/messages/{id}), so a rule can pin your agent to reading one message. You choose the operations it may call, so destructive ones like deleting a message are not included unless you add them.
Credential isolation
Your Textmagic 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 an SMS message' or 'check the price of a message', and Jentic returns the matching Textmagic 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 Textmagic API through Jentic.
What authentication does the Textmagic API use?
The Textmagic API uses an API key passed in the `X-TM-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 Textmagic 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 Textmagic 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 Textmagic API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Textmagic API have?
The Textmagic API exposes 36 endpoints covering contacts, lists, messages operations.
Can I limit what my agent is allowed to do with the Textmagic API?
Yes. Because you run Jentic One yourself, your own rules decide which Textmagic operations and credentials the agent may use. You can allow it to send a message with POST /messages or read a single message with GET /messages/{id} while leaving destructive calls like DELETE /messages/{id} out entirely. Since the message id sits in the URL path, a rule can pin the agent to reading one specific message rather than the whole account.
For Agents
Programmatically send message, list messages. Covers 36 operations with apiKey authentication.
Use for: I need to send message, I want to messages, Search for message, Find all message
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Textmagic SMS messaging API. Send messages, manage contacts, templates, and phone numbers. The API exposes 36 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>