Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / IOT / EMnify
EMnify logo

EMnify APIs for AI Agents

www.emnify.com·Developer portal → www.emnify.com

IOTDevice ManagementJentic-Generated DocumentsBearer tokenAgent Ready

For Agents

APIs2 in catalogue
Endpoints194 indexed
AuthBearer token — 1 credential for all 2 APIs
ProvenanceJentic-generated documents

An agent can authenticate to EMnify, provision and update SIMs and endpoints, send SMS to IoT devices, set data quotas and traffic limits, read usage and tariff data, and administer users and workspaces across both the core and enterprise APIs.

EMnify offers connectivity-only cellular IoT management, without firmware or a device cloud, exposed through two API surfaces that share the same platform and bearer credential: a 13-endpoint core surface for essential SIM, endpoint, and SMS work, and a 181-endpoint enterprise surface for bulk operations, quotas, MFA-protected user management, and event integrations.

Use for: Managing cellular IoT connectivity through EMnify: SIM and endpoint lifecycle, SMS to devices, data quotas, tariff plans, users, and event integrations.

Not supported: device firmware, device cloud, MQTT data brokering, non-cellular networks, hardware provisioning

Credentials: Both APIs use HTTP Bearer authentication, and a token obtained from EMnify's authenticate endpoint covers calls to both the core and enterprise surfaces.

All 2 EMnify OpenAPI documents are Jentic-generated and indexed by Jentic, kept validated and agent-ready.

EMnify is a cellular IoT connectivity platform. Its APIs manage SIMs, endpoints, users, organizations, tariff plans, and integrations across global mobile networks. Jentic publishes and maintains the OpenAPI specifications for both EMnify surfaces, so AI agents can authenticate, provision connectivity, send SMS, set data quotas, and administer multi-tenant workspaces through structured tooling. The two APIs share one bearer credential and one control plane, differing only in depth: a compact core surface for essential SIM and endpoint work, and a full enterprise surface for fleet-scale operations.

Jentic One on Github

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...UseWhy
Basic SIM, endpoint, and SMS operationsEMnify APIThe core API covers authentication, SIM and endpoint lifecycle, SMS, and tariff reads in 13 endpoints without the full administrative surface.
Fleet-scale operations and administrationEMnify Enterprise APIThe 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 endpointEMnify APIBoth 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 endpointEMnify Enterprise APIData 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" | sh
2

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

Once connected, ask your agent something like: “manage cellular IoT SIMs and endpoints”.

What AI Agents Can Do with EMnify

Each workflow spans multiple EMnify APIs. Jentic routes each operation to the right API automatically.

Provision then scale a device fleet

Start a new deployment on the core API by authenticating, creating SIMs, binding endpoints, and sending a provisioning SMS, then move fleet-wide administration to the enterprise API for bulk endpoint updates, data quotas, and event integrations as the fleet grows. One bearer token spans both surfaces.

Example prompt:

Use emnify to POST /authenticate, POST /sim, and POST /endpoint for the initial devices, then use emnify-api to POST /api/v2/endpoint/multi for batch updates and POST /api/v1/endpoint/{endpoint_id}/quota/data to cap costs.

APIs used

EMnify API + EMnify Enterprise API

Send SMS and enforce cost controls

Deliver a command SMS to a managed endpoint through the core API, then apply a data quota and read daily usage statistics on the enterprise API so a runaway device cannot generate a surprise bill. Cost controls live on the enterprise surface while the SMS command channel is available on both.

Example prompt:

Use emnify to POST /sms to the endpoint, then use emnify-api to GET /api/v1/endpoint/{endpoint_id}/stats/daily and POST /api/v1/endpoint/{endpoint_id}/quota/data to set a hard cap.

APIs used

EMnify API + EMnify Enterprise API

Reconcile tariffs across both surfaces

Read service profiles and tariff plans on the core API to reconcile fleet billing, then use the enterprise API to adjust workspace and organization configuration or invite the finance user who owns the reconciliation. This keeps plan assignment and account administration consistent across a multi-tenant setup.

Example prompt:

Use emnify to GET /service_profile and GET /tariff_plan for the reconciliation report, then use emnify-api to POST /api/v2/user/invitation to add the finance owner.

APIs used

EMnify API + EMnify Enterprise API

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.

Intent-based discovery

Agents search the Jentic directory by intent such as 'provision a new IoT SIM' or 'set an endpoint data quota', and Jentic returns the matching EMnify operation with its input schema, so the agent picks the right surface and endpoint without browsing reference docs.

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?

Yes. An agent can provision SIMs and endpoints, send SMS to devices, apply data quotas and traffic limits, read usage and cost statistics, administer users and workspaces, and configure event integrations. The core API covers day-to-day SIM and endpoint work while the enterprise API handles bulk and multi-tenant operations.

Does EMnify handle device firmware or a device cloud?

No. EMnify is a connectivity-only platform focused on cellular SIMs, endpoints, SMS, and the associated account controls. It does not manage device firmware, provide a device cloud, or broker MQTT data. Teams that also need firmware or a device cloud typically pair EMnify with a platform such as Particle.

What happens when an EMnify API returns a rate limit response?

The OpenAPI specs do not declare quantitative rate limits, and EMnify enforces limits at the account level. Treat HTTP 429 responses as authoritative and back off using the Retry-After header when it is present, on both the core and enterprise surfaces.

If you need a different IOT vendor

All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.

ParticleIntegrated IoT device cloud with bundled connectivity and firmware management, where EMnify is connectivity-only.
TwilioProgrammable SMS and IoT SIM connectivity, useful for reaching phones outside a managed EMnify fleet.
HologramGlobal cellular IoT SIM and connectivity management, an adjacent alternative for device fleets.

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.

Book a Demo