Install Jentic One Beta

Connect the ZOLEO API to your agent

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

Send and retrieve mobile-originated messages for a device

Retrieve mobile-terminated messages and delete a conversation thread

Update device information and push notification tokens

Look up a device's link status and resolve contacts

GET STARTED

Start building with ZOLEO API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ZOLEO API for, with concrete tasks.

★ Agent-Driven Device Messaging

An AI agent relays messages to and from a ZOLEO satellite device for an off-grid user. It sends a mobile-originated message, polls for mobile-terminated replies, and clears a thread once the conversation is done. Jentic exposes each ZOLEO operation with its input schema so the agent passes the device id and message body correctly on the first call.

Send a mobile-originated message from a device id, then retrieve the mobile-terminated replies for that device

Device Registration and Linking

A companion app onboards a new ZOLEO unit and ties it to a user account. The ZOLEO API registers the device during signup, logs the device in, and can unlink it or update its stored information later. Push notification tokens are kept current so the user hears about new messages.

Location Weather and Contacts

A trip-planning assistant pulls safety context for a device out in the field. The ZOLEO API returns a weather forecast for the device's latitude and longitude and resolves the user's contacts for addressing messages. Together they let the assistant brief the user before they send.

Retrieve the weather forecast for a device's latitude and longitude, then look up the device's contacts

Key Endpoints

16 endpoints — the zoleo api registers satellite messaging devices and exchanges messages with them over the global alerting platform backend.

METHOD

PATH

DESCRIPTION

POST

/zoleosignup

POST

/devices/{deviceId}/momessages

Send one or more mobile-originated messages

GET

/devices/{deviceId}/momessages

Retrieve mobile-originated messages

GET

/zoleo/{deviceId}/mtmessages/{messageId}

Retrieve mobile-terminated messages

PATCH

/devices/{deviceId}

Update device information

GET

/zoleo/{deviceId}

Retrieve link status and device info

GET

/zoleoforecast/{deviceId}/{latitude}/{longitude}

Retrieve a weather forecast for a device location

POST

/zoleosignup

POST

/devices/{deviceId}/momessages

Send one or more mobile-originated messages

GET

/devices/{deviceId}/momessages

Retrieve mobile-originated messages

GET

/zoleo/{deviceId}/mtmessages/{messageId}

Retrieve mobile-terminated messages

PATCH

/devices/{deviceId}

Update device information

GET

/zoleo/{deviceId}

Retrieve link status and device info

GET

/zoleoforecast/{deviceId}/{latitude}/{longitude}

Retrieve a weather forecast for a device location

Why Jentic?

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

Setup

Wiring the ZOLEO API by hand means managing several API key headers, the X-GAPAPIKEY, X-SECURITY-KEY, and reCAPTCHA SECRET-TOKEN, across signup and device operations, plus the production and beta tenant hosts. Through Jentic you install once, import ZOLEO from the API Directory, store the keys once, and your agent calls it.

Permission scoping

ZOLEO puts the device id in the URL path (/devices/{deviceId}/..., /zoleo/{deviceId}/...), so a rule can pin your agent to one device and the operations you pick, such as sending and reading its messages. You choose the operations it may call, so deleting the device or a message thread is not included unless you add them.

Credential isolation

Your ZOLEO keys 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 device message' or 'get a device forecast', and Jentic returns the matching ZOLEO operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using ZOLEO API through Jentic.

What authentication does the ZOLEO API use?

The ZOLEO API authenticates with API key headers per its OpenAPI spec: most device operations send the X-GAPAPIKEY header, device registration adds an X-SECURITY-KEY and a reCAPTCHA SECRET-TOKEN, and a few endpoints like the weather forecast need no key. Through Jentic the keys are stored encrypted by your own Jentic One instance and injected at call time, so they never sit in your agent's prompt or logs.

Can I send messages with the ZOLEO API?

Yes. You post one or more mobile-originated messages for a device id and retrieve mobile-terminated messages when replies arrive. A delete operation clears a conversation thread or a single message on the server when it is no longer needed.

What are the rate limits for the ZOLEO API?

The ZOLEO OpenAPI spec does not publish fixed rate limits. Because it is a per-device backend, pace requests per device and back off on errors rather than assume a shared quota.

Is there a ZOLEO MCP server?

You do not need an MCP server to give your agent the ZOLEO API. Jentic connects it directly from the API Directory: import it, store your keys once, and your agent calls its operations. Operations are discovered on demand, so your agent's context stays lean instead of loading a full tool list up front.

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

Yes. Write a rule that allows only the message-send and message-read operations under one device id, so the agent can exchange messages for that device but cannot delete the device or unlink it, and every call it makes is logged. Device deletion and unlinking stay out of the allowed set until you add them.

How do I send a device message with the ZOLEO API through Jentic?

Search Jentic for 'send a message from a device', and it returns the ZOLEO mobile-originated message operation with its input schema. Your agent posts the device id and message body, then polls for mobile-terminated replies. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Globalalerting ZOLEO API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Community OpenAPI document · agent-readyCommunicationsSms MessagingapiKey16 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Register ZOLEO satellite devices, send and retrieve device messages, update device information and push tokens, and look up link status, contacts, and weather.

Use for: Register a new ZOLEO device, Send a message from a device, Retrieve incoming messages for a device, Update a device's push notification token

Not supported: Does not provision satellite hardware, handle billing, or place voice calls. Use for registering ZOLEO devices and exchanging messages with them only.

The ZOLEO API registers satellite messaging devices and exchanges messages with them over the Global Alerting Platform backend. It sends and retrieves mobile-originated messages, retrieves mobile-terminated messages, and deletes conversation threads or individual messages on the server. Device login, link-status lookups, push notification token updates, contacts lookup, and a device-location weather forecast complete the surface the ZOLEO apps consume.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

60%

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: A-Signals: 4

51%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

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

51%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

81%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

76%

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: C-Signals: 1

50%

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

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ZOLEO API to your agent

Capabilities

Start building with ZOLEO API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Globalalerting ZOLEO API

Jentic AI Readiness Score

ZOLEO 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