Install Jentic One Beta

Connect the Text2reach SMS Messaging API to your agent

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

Send SMS

Get message delivery status

Cancel SMS

Verify PIN code

Monitor Text2reach SMS Messaging API operational status and events

GET STARTED

Start building with Text2reach SMS Messaging API

Explore with Jentic One

View OpenAPI Document

Automated Account Management

Automate account operations by combining multiple Text2reach SMS Messaging API endpoints. Agents can get message delivery status and then get extended delivery report in a single workflow.

Call GET /sms/status to get message delivery status, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Text2reach SMS Messaging 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 sms', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — text2reach sms messaging api for sending sms messages, checking delivery status, managing credits, and pin verification.

METHOD

PATH

DESCRIPTION

GET

/sms/send

Send SMS

GET

/sms/status

Get message delivery status

GET

/sms/details

Get extended delivery report

GET

/sms/cancel

Cancel SMS

GET

/sms/credit

Get credits balance

GET

/sms/prices

Get prices

GET

/sms/pin

Verify PIN code

GET

/sms/send

Send SMS

GET

/sms/status

Get message delivery status

GET

/sms/details

Get extended delivery report

GET

/sms/cancel

Cancel SMS

GET

/sms/credit

Get credits balance

GET

/sms/prices

Get prices

GET

/sms/pin

Verify PIN code

Why Jentic?

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

Setup

Wiring the Text2reach SMS Messaging API by hand means handling its api_key query-parameter auth against the api.text2reach.com host and coding each send, status, and pricing call yourself. Through Jentic you install once, import the Text2reach SMS Messaging API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Text2reach carries the destination and message in query parameters rather than a resource id in the URL path, so limit the agent to the operations it needs, such as sending an SMS or checking delivery status. You choose the operations it may call, so cancelling a message is not included unless you add it.

Credential isolation

Your Text2reach 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' or 'check message delivery status', and Jentic returns the matching Text2reach SMS Messaging API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Text2reach SMS Messaging API through Jentic.

What authentication does the Text2reach SMS Messaging API use?

The Text2reach SMS Messaging API uses an API key passed in the `api_key` query. 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 sms with the Text2reach SMS Messaging API?

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

What are the rate limits for the Text2reach SMS Messaging 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 sms through Jentic?

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

How many endpoints does the Text2reach SMS Messaging API have?

The Text2reach SMS Messaging API exposes 7 endpoints covering account, pin verification, sms operations.

Can I limit what my agent is allowed to do with the Text2reach SMS Messaging API?

Yes. Because you run Jentic One yourself, you decide which of the API's operations the agent may call, so you can grant only sending an SMS (GET /sms/send) and checking delivery status (GET /sms/status) while withholding the rest. Text2reach passes the destination number and message in query parameters rather than a path resource id, so scoping is done at the operation level: cancelling a message (GET /sms/cancel) is not available to the agent unless you add it. Your API key is held encrypted by your own instance and injected only for the operations you have allowed.

Text2reach SMS Messaging API

AI ReadinessFoundational (D+)48/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsSms MessagingapiKey7 EndpointsREST

For Agents

Programmatically send sms, get message delivery status. Covers 7 operations with apiKey authentication.

Use for: I need to send sms, I want to message delivery status, Search for extended delivery report, Find all cancel sms

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

Text2reach SMS messaging API for sending SMS messages, checking delivery status, managing credits, and PIN verification. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

100%

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: D+Signals: 4

45%

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: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Text2reach SMS Messaging API to your agent

Capabilities

Start building with Text2reach SMS Messaging API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Text2reach SMS Messaging API

Jentic AI Readiness Score

Text2reach SMS Messaging 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