Install Jentic One Beta

Connect the Messaging API v3.x to your agent

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

create free trial number list

get all free trial numbers

health check

send messages

fetch all sent/received messages

GET STARTED

Start building with Messaging API v3.x API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Messaging API v3.x API for, with concrete tasks.

★ Communications Operations

Use the Messaging API v3.x to perform communications operations programmatically. The API provides 18 endpoints covering core functionality including create free trial number list, get all free trial numbers, health check.

Call POST /free-trial-numbers to create free trial number list

Automated Free Trial Numbers Management

Automate free trial numbers operations by combining multiple Messaging API v3.x endpoints. Agents can get all free trial numbers and then health check in a single workflow.

Call GET /free-trial-numbers to get all free trial numbers, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Messaging API v3.x 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 oauth2 tokens manually.

Search Jentic for 'create free trial number list', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

18 endpoints — send and receive sms & mms programmatically, leveraging australia's leading mobile network.

METHOD

PATH

DESCRIPTION

POST

/free-trial-numbers

create free trial number list

GET

/free-trial-numbers

get all free trial numbers

GET

/health-check

health check

POST

/messages

send messages

GET

/messages

fetch all sent/received messages

GET

/messages/{messageId}

fetch a specific message

PUT

/messages/{messageId}

update a message

PATCH

/messages/{messageId}

update message tags

POST

/free-trial-numbers

create free trial number list

GET

/free-trial-numbers

get all free trial numbers

GET

/health-check

health check

POST

/messages

send messages

GET

/messages

fetch all sent/received messages

GET

/messages/{messageId}

fetch a specific message

PUT

/messages/{messageId}

update a message

PATCH

/messages/{messageId}

update message tags

Why Jentic?

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

Setup

Wiring the Telstra Messaging API by hand means running its OAuth2 client-credentials flow to mint scoped tokens, refreshing them, targeting products.api.telstra.com/messaging/v3, and writing the retry glue yourself. Through Jentic you install once, import the Messaging API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

The Messaging API puts the message id in the URL path (/messages/{messageId}), so a rule can pin your agent to one message: it can read and update that message and nothing else. You choose the operations it may call, so ones like provisioning free-trial numbers are not included unless you add them.

Credential isolation

Your Telstra client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a message' or 'check message status', and Jentic returns the matching Messaging API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Messaging API v3.x API through Jentic.

What authentication does the Messaging API v3.x use?

The Messaging API v3.x uses OAuth 2.0 for authorization. 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 create free trial number list with the Messaging API v3.x?

Yes. Use the POST /free-trial-numbers endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Messaging API v3.x?

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 create free trial number list through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create free trial number list'. Jentic returns the matching Messaging API v3.x operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Messaging API v3.x have?

The Messaging API v3.x exposes 18 endpoints covering free trial numbers, health check, messages operations.

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

Yes. Because Jentic One is self-hosted, you write the rules that decide which Telstra Messaging operations and credentials your agent may use. Since the message id sits in the URL path (/messages/{messageId}), a rule can pin the agent to a single message so it can only read and update that one and nothing else. You also choose which operations are exposed, so calls like provisioning free-trial numbers stay off-limits unless you add them.

Telstra Messaging API v3.x

AI ReadinessAI-Ready (A-)76/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliveryoauth218 EndpointsREST

For Agents

Programmatically create free trial number list, get all free trial numbers. Covers 18 operations with oauth2 authentication.

Use for: I need to free trial number list, I want to all free trial numbers, Search for health check, Find all send messages

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

Send and receive SMS & MMS programmatically, leveraging Australia's leading mobile network. With Telstra's Messaging API, we take out the complexity to allow seamless messaging integration into your app, with just a few lines of code. Our REST API is enterprise grade, allowing you to communicate with engaging SMS & MMS messaging in your web and mobile apps in near real-time on a global scale. Intr. The API exposes 18 endpoints secured with oauth2 authentication.

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

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

30%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

100%

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: C-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.

64%

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

85%

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 Messaging API v3.x to your agent

Capabilities

Start building with Messaging API v3.x API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Telstra Messaging API v3.x

Jentic AI Readiness Score

Messaging API v3.x

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