Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Text2VIP 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%2Ftext2vip.messagingchannel.com%2Ftext2vip-messagingchannel" | 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%2Ftext2vip.messagingchannel.com%2Ftext2vip-messagingchannel" | 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 Text2VIP API.
Send an SMS message
Update subscription
Integrate Text2VIP API into automated workflows
Query and filter Text2VIP API records by parameters
Monitor Text2VIP API operational status and events
GET STARTED
Patterns agents use Text2VIP API for, with concrete tasks.
★ Communications Operations
Use the Text2VIP API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including send an sms message, update subscription.
Call POST /messages to send an sms message
Data Retrieval and Monitoring
Query Text2VIP API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Text2VIP API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Text2VIP 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 an sms message', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — api for sms and messaging services.
METHOD
PATH
DESCRIPTION
/messages
Send an SMS message
/subscriptions
Update subscription
/messages
Send an SMS message
/subscriptions
Update subscription
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Text2VIP API by hand means learning its Authorization header API-key auth against the api.text2vip.messagingchannel.com host and coding its message and subscription calls yourself. Through Jentic you install once, import the Text2VIP API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Text2VIP carries the recipient and message in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as sending a message. You choose the operations it may call, so updating a subscription is not included unless you add it.
Credential isolation
Your Text2VIP 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', and Jentic returns the matching Text2VIP API 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 Text2VIP API through Jentic.
What authentication does the Text2VIP API use?
The Text2VIP API uses an API key passed in the `Authorization` 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 an sms message with the Text2VIP 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 Text2VIP 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 an sms message through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send an sms message'. Jentic returns the matching Text2VIP API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Text2VIP API have?
The Text2VIP API exposes 2 endpoints covering messages, subscriptions operations.
Can I limit what my agent is allowed to do with the Text2VIP API?
Yes. Because you run Jentic One yourself, you decide which Text2VIP operations the agent may call, so you can allow it to send a message with POST /messages while withholding the ability to update a subscription with PUT /subscriptions. Text2VIP carries the recipient and message in the request body rather than a resource id in the URL, so restricting the agent to only the operations it needs keeps its access tightly scoped. Your API key is held and injected by your own instance under your rules, so the agent never sees the raw secret and can only run the calls you have permitted.
For Agents
Programmatically send an sms message, update subscription. Covers 2 operations with apiKey authentication.
Use for: I need to send an sms message, I want to subscription, Get the current status of Text2VIP API resources, List all records from Text2VIP API
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
API for SMS and messaging services. The API exposes 2 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>