EMnify APIs for AI Agents
IOTDevice ManagementJentic-Generated SpecsBearer tokenAgent Ready
EMnify API Catalog
2 APIs across 1 product group. All share one credential.
IOT2
EMnify Enterprise APIOperate the full EMnify cellular IoT control plane - endpoints, SIMs, users, organizations, tariff plans, and integrations across 181 endpoints.~181 endpointsEMnify APIAuthenticate, manage SIM and endpoint lifecycle, send SMS, and read service profiles on EMnify's cellular IoT platform.~13 endpoints
Which EMnify API should I use?
| I want to... | Use | Why |
|---|---|---|
| Basic SIM, endpoint, and SMS operations | EMnify API | The core API covers authentication, SIM and endpoint lifecycle, SMS, and tariff reads in 13 endpoints without the full administrative surface. |
| Fleet-scale operations and administration | EMnify Enterprise API | The enterprise API adds bulk endpoint calls, data quotas, traffic limit extensions, MFA user management, workspaces, and event integrations across 181 endpoints. |
| Send SMS to a managed IoT endpoint | EMnify API | Both APIs expose SMS, but the core API is the leaner path when only sending is needed. |
| Set a data quota or cost cap on an endpoint | EMnify Enterprise API | Data quotas and traffic limit extensions exist only on the enterprise surface. |
Install Jentic One Beta
Connect the EMnify APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EMnify APIs, 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.
1
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%2Femnify.net" | sh2
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%2Femnify.net" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Once connected, ask your agent something like: .
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring EMnify by hand means exchanging credentials for a bearer token, threading it through two API surfaces and their control-plane operations, and building your own retries against cdn.emnify.net. With Jentic you install once, add the EMnify APIs from the Jentic directory, store the token once, and your agent calls both surfaces.
Permission scoping
EMnify puts the SIM id and endpoint id in the URL path, so your own rules can pin an agent to one SIM or one endpoint and to a chosen set of operations. Actions like creating SIMs, sending SMS, or setting data quotas are not available to the agent unless you add them.
Credential isolation
Your EMnify 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, and the same token serves both the core and enterprise APIs.
FAQs
Specific to using EMnify APIs through Jentic.
What is the difference between the two EMnify APIs?
The core EMnify API is a compact 13-endpoint surface for authentication, SIM and endpoint lifecycle, SMS, and tariff reads. The enterprise EMnify API is a 181-endpoint surface that adds bulk endpoint operations, data quotas, traffic limit extensions, MFA-protected user management, organization and workspace configuration, and event integrations. Start on the core API and move to the enterprise API when a deployment needs fleet-scale control.
Do both EMnify APIs share the same credentials?
Yes. Both surfaces use HTTP Bearer authentication, and a token obtained from EMnify's authenticate endpoint works against both the core and enterprise APIs. You store the token once and use it across all EMnify operations.
Why does Jentic publish OpenAPI specs for EMnify?
EMnify does not publish a stable OpenAPI specification at these entry points. Jentic generates and maintains both specs and validates them against the live API so that AI agents and developers can call EMnify through structured tooling rather than hand-built clients.
Can an agent manage a full IoT fleet through these APIs?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
