canonical: https://jentic.com/apis/globalalerting.com/globalalerting

# Globalalerting ZOLEO API

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.

## For AI agents

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

## Scope

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

## Capabilities

- Register a ZOLEO device and link or unlink it
- 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
- Retrieve a weather forecast for a device's location

## Use cases

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

Example prompt: 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.

Example prompt: Register a device at signup, log it in, and update its push notification token

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/zoleosignup` | Register a ZOLEO device |
| 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 |

## Key resources

- **Devices** — Register, update, delete, and log in devices and read link status
- **Messages** — Send and retrieve mobile-originated messages, retrieve mobile-terminated messages, and delete threads or messages
- **Notifications** — Set the iOS notification app list and update the push notification token
- **Contacts** — Resolve contacts for a device
- **Forecast** — Retrieve a weather forecast for a device's location

## AI readiness

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.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 80 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 64 / 100
- **View full report:** https://jentic.com/apis/globalalerting.com/globalalerting/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **The SMS Works** — The SMS Works sends and receives SMS messages over cellular networks.
- **SureVoIP** — SureVoIP adds voice telephony alongside messaging.
- **Open-Meteo** — Open-Meteo returns weather forecasts by coordinates.

## FAQ

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