Install Jentic One Beta

Connect the International SOS Communication API to your agent

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

Dispatch a communication through the SMS, push, text-to-speech, Teams, or email channel endpoints

Attach recipients to a communicationId and page through the recipient list

Read delivery history and response history for a delivery or channel

Count and list travellers affected by an alert or present in a country, with a vipsOnly filter

GET STARTED

Start building with International SOS Communication API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use International SOS Communication API for, with concrete tasks.

★ AI duty-of-care assistant checking who is affected by an alert

When a security or medical alert breaks, a developer's agent connected through Jentic finds the International SOS monitor operations by intent and calls them with the Authorization token injected at execution time. It counts travellers per alert, pulls the affected traveller details, and reports who is in the impact area, without the token ever entering the agent's context.

POST /api/monitor/TravelerCountsByAlert with salesForceAccountId, alertIds, startTimeGmt and endTimeGmt for today, then POST /api/monitor/TravelerDetailsByAlert with the same body to list the affected travellers

Multi-channel safety messaging

A travel risk team needs to reach travellers on whichever channel works in the field. The International SOS Communication API has separate send endpoints for SMS, push, text-to-speech calls, Microsoft Teams, and email, plus recipient endpoints that attach people to a communicationId. Delivery status and delivery history operations show what reached each person.

POST /v1/recipients with a communicationId and its recipients, then GET /deliveryhistory/{deliveryId} for a delivery to confirm it was delivered

Response tracking after an alert

After a check-in message goes out, the team needs to know who answered. The API records responses arriving over push, Teams, SMS, email, and voice, returns the response history for a channel, and returns a response summary for a communication, so coordinators can chase only the people who have not replied.

Call GET /responsesummary/communicationid/{id} for the check-in communication and list recipients with no response

Template and channel settings per client

Each International SOS client account, identified by salesforceId, has its own templates and enabled channels. The API returns active channels for a client, saves client channel settings with a channelCode and isActive flag, and lets a tool fetch, create, update, or delete message templates.

Call GET /clientChannelSettings/activeChannels/{salesforceId} for a client, then GET /templates/{type} with that salesforceId and channelCode to show the template in use

Key Endpoints

115 endpoints — the international sos communication api sends traveller safety communications from the international sos platform over sms, push, text-to-speech calls, microsoft teams, and email, then tracks each delivery and the responses recipients send back.

METHOD

PATH

DESCRIPTION

POST

/v1/channel/sms

Send through the SMS channel

POST

/v1/recipients

Add recipients to a communication

GET

/deliveryhistory/{deliveryId}

Get delivery history

GET

/responsesummary/communicationid/{id}

Get a communication's response summary

POST

/api/monitor/TravelerCountsByAlert

Count travellers by alert

POST

/api/monitor/TravelerItineraries

Get traveller itineraries

GET

/templates/{type}

Get templates by type

POST

/v1/channel/sms

Send through the SMS channel

POST

/v1/recipients

Add recipients to a communication

GET

/deliveryhistory/{deliveryId}

Get delivery history

GET

/responsesummary/communicationid/{id}

Get a communication's response summary

POST

/api/monitor/TravelerCountsByAlert

Count travellers by alert

POST

/api/monitor/TravelerItineraries

Get traveller itineraries

GET

/templates/{type}

Get templates by type

Why Jentic?

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

Setup

Wiring International SOS by hand means passing the Authorization token on every call, picking the right US or EU host, and working through a spec with no operation ids across delivery, response, and monitor routes. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

Most International SOS operations carry the client, traveller, or recipient in the request body, so rules bound which operations your agent may call rather than which traveller it sees. You choose the operations it may call, so sending SMS or deleting a template are not included unless you add them.

Credential isolation

Your International SOS token 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 'count travellers affected by an alert' or 'get delivery history', and Jentic returns the matching International SOS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using International SOS Communication API through Jentic.

What authentication does the International SOS Communication API use?

Per its OpenAPI spec, the International SOS Communication API uses an API key scheme: an authorization token sent in the `Authorization` request header, applied to every operation. Through Jentic the token is stored by your own instance and attached to each call at execution time.

Does the International SOS Communication API have US and EU endpoints?

Yes. The spec lists two servers: https://api.internationalsos.com/comms-api-us and https://api.internationalsos.com/comms-api-eu. Use the host that matches the region your International SOS account is provisioned in.

Can I find travellers in a specific country with this API?

Yes. POST /api/monitor/TravelerCountsByCountry returns traveller counts and POST /api/monitor/TravelerDetailsByCountry returns traveller details for the isoCodes you pass, between startTimeGmt and endTimeGmt, with an optional vipsOnly filter. GET /api/monitor/Countries returns the countries available to query.

What are the rate limits for the International SOS Communication API?

The OpenAPI spec does not specify rate limits. Check with International SOS through https://www.internationalsos.com for the limits that apply to your account before sending large recipient batches.

Is there an International SOS MCP server?

You don't need an MCP server to give your agent International SOS. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the monitor, delivery, and messaging operations it needs, discovered on demand rather than loaded into its context.

Can I limit what my agent is allowed to do with International SOS?

Yes. For example, write a rule that allows only the traveller monitor reads such as POST /api/monitor/TravelerCountsByAlert and GET /deliveryhistory/{deliveryId}, so the agent can report who is affected and what was delivered but cannot send messages or edit templates, and every call it makes is logged.

How do I count travellers affected by an alert through Jentic?

Import the International SOS Communication API from the Jentic API Directory and store your Authorization token once. Your agent searches for 'count travellers affected by an alert', gets POST /api/monitor/TravelerCountsByAlert with its schema, and sends salesForceAccountId, alertIds, and the time window. To run it on your own infrastructure, install Jentic One from its GitHub repo.

International SOS Communication API

AI ReadinessNon-Ready (F)0/100

See full scorecard

Community OpenAPI document · agent-readyCommunicationsPush NotificationsapiKey115 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send International SOS safety communications over SMS, push, voice, Teams, and email, check delivery and response status, and look up travellers affected by an alert or in a country.

Use for: I need to send an SMS safety alert to travellers, Find all travellers currently in a given country, Get the delivery history for a communication delivery, Check whether recipients responded to a push alert

Not supported: Does not handle travel booking, medical case management, or risk intelligence content authoring. Use for International SOS traveller communications, delivery tracking, and traveller monitoring only.

The International SOS Communication API sends traveller safety communications from the International SOS platform over SMS, push, text-to-speech calls, Microsoft Teams, and email, then tracks each delivery and the responses recipients send back. It exposes the recipient lists, message templates, and per-client channel settings behind those communications, keyed to a client's salesforceId. Monitor operations return traveller counts, traveller details, and itineraries by alert or by country, and manager-alert operations return notification details for a given AlertId. The API is served from separate US and EU hosts.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

68%

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

11%

Description Coverage

Coverage of descriptions across API elements.

84%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

80%

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

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the International SOS Communication API to your agent

Capabilities

Start building with International SOS Communication API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

International SOS Communication API

Jentic AI Readiness Score

CommunicationApi, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

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