emnify
emnify is a cloud-native global IoT cellular connectivity provider operating its own mobile core and SuperNetwork across 540+ MNOs in 190+ countries. emnify supplies SIMs, eUICC-enabled multi-form-factor cards, and Consumer/Advanced eSIM (SGP.32) profiles to enterprise IoT deployments — fleet tracking, EV charging, point-of-sale, smart buildings, micromobility, airline crew tablets, and more. The emnify REST API, GraphQL API, and Data Streamer give programmatic control over SIMs, endpoints, service and tariff profiles, eUICC profile operations, events, SMS, callbacks, and outbound usage/event streaming to S3, Kinesis, and webhooks. NTN-IoT satellite connectivity via Skylo extends coverage beyond terrestrial cellular.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles emnify the way a machine reads it — 96 machine-readable artifacts across 29 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — emnify scores 70.3/100 (exemplar), with a separate agent-readiness read of 56/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile emnify
Each block below is one kind of artifact we hold for emnify. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 29
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
emnify GraphQL API
emnify GraphQL API for flexible, single-request queries against the emnify data model with customizable response shapes. An in-browser GraphiQL IDE supports interactive explorat...
emnify Data Streamer
Stream event and usage data to outbound destinations (AWS S3, AWS Kinesis, REST/webhook, Datadog, Salesforce, Keen.io). Supports detailed object schemas for data types, traffic ...
emnify Documentation MCP Server
Public MCP server for emnify documentation. Connect Claude Code, Cursor, or any MCP-aware client to query emnify product, developer, and API reference content directly from your...
emnify subpackage_applicationTokens API
The subpackage_applicationTokens API from emnify — 2 operation(s) for subpackage_applicationtokens.
emnify subpackage_authentication API
The subpackage_authentication API from emnify — 8 operation(s) for subpackage_authentication.
emnify subpackage_automations API
The subpackage_automations API from emnify — 6 operation(s) for subpackage_automations.
emnify subpackage_cloudConnect API
The subpackage_cloudConnect API from emnify — 7 operation(s) for subpackage_cloudconnect.
emnify subpackage_customEvents API
The subpackage_customEvents API from emnify — 4 operation(s) for subpackage_customevents.
emnify subpackage_endpoint API
The subpackage_endpoint API from emnify — 16 operation(s) for subpackage_endpoint.
emnify subpackage_euicc API
The subpackage_euicc API from emnify — 5 operation(s) for subpackage_euicc.
emnify subpackage_euiccOperation API
The subpackage_euiccOperation API from emnify — 4 operation(s) for subpackage_euiccoperation.
emnify subpackage_events API
The subpackage_events API from emnify — 2 operation(s) for subpackage_events.
emnify subpackage_integrations API
The subpackage_integrations API from emnify — 10 operation(s) for subpackage_integrations.
emnify subpackage_ipAddressSpaces API
The subpackage_ipAddressSpaces API from emnify — 3 operation(s) for subpackage_ipaddressspaces.
emnify subpackage_lookups API
The subpackage_lookups API from emnify — 8 operation(s) for subpackage_lookups.
emnify subpackage_operator API
The subpackage_operator API from emnify — 1 operation(s) for subpackage_operator.
emnify subpackage_organization API
The subpackage_organization API from emnify — 9 operation(s) for subpackage_organization.
emnify subpackage_passwordManagementAndActivation API
The subpackage_passwordManagementAndActivation API from emnify — 4 operation(s) for subpackage_passwordmanagementandactivation.
emnify subpackage_serviceLookupsAndConfiguration API
The subpackage_serviceLookupsAndConfiguration API from emnify — 5 operation(s) for subpackage_servicelookupsandconfiguration.
emnify subpackage_serviceProfiles API
The subpackage_serviceProfiles API from emnify — 7 operation(s) for subpackage_serviceprofiles.
emnify subpackage_sim API
The subpackage_sim API from emnify — 9 operation(s) for subpackage_sim.
emnify subpackage_simOperation API
The subpackage_simOperation API from emnify — 4 operation(s) for subpackage_simoperation.
emnify subpackage_simUnlinkedProductStatistics API
The subpackage_simUnlinkedProductStatistics API from emnify — 1 operation(s) for subpackage_simunlinkedproductstatistics.
emnify subpackage_systemEvents API
The subpackage_systemEvents API from emnify — 2 operation(s) for subpackage_systemevents.
emnify subpackage_tagManagement API
The subpackage_tagManagement API from emnify — 8 operation(s) for subpackage_tagmanagement.
emnify subpackage_tariffPlans API
The subpackage_tariffPlans API from emnify — 3 operation(s) for subpackage_tariffplans.
emnify subpackage_tariffProfiles API
The subpackage_tariffProfiles API from emnify — 9 operation(s) for subpackage_tariffprofiles.
emnify subpackage_userManagement API
The subpackage_userManagement API from emnify — 8 operation(s) for subpackage_usermanagement.
emnify subpackage_workspaces API
The subpackage_workspaces API from emnify — 7 operation(s) for subpackage_workspaces.
Scroll within the panel for all 29 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
emnify REST API
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
emnify REST API
OPEN COLLECTIONArazzo Workflows 17
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
emnify Blacklist Operator for Endpoint
Authenticate, list available operators, then add one to an endpoint's blacklist.
ARAZZOemnify Check Endpoint Connectivity
Authenticate, read endpoint details, then read its live connectivity status.
ARAZZOemnify Create and Tag Endpoint
Authenticate, create a tag, create an endpoint, then assign the tag to it.
ARAZZOemnify Decommission Endpoint
Authenticate, read the endpoint, suspend its SIM, then delete the endpoint.
ARAZZOemnify Extend Traffic Limit When Blocked
Authenticate, read endpoint connectivity, then grant a temporary traffic limit extension if blocked.
ARAZZOemnify Find SIM and Provision Endpoint
Authenticate, find a SIM by ICCID, then create an endpoint bound to that SIM.
ARAZZOemnify Get Endpoint Usage Statistics
Authenticate, confirm the endpoint, then read its usage and daily usage statistics.
ARAZZOemnify Locate Endpoint
Authenticate, confirm the endpoint, then retrieve its cell-tower-based location.
ARAZZOemnify Organization Volume Report
Authenticate, read organization details, then read active inclusive volumes and daily stats.
ARAZZOemnify Provision and Activate Endpoint
Authenticate, create an endpoint with a SIM, then activate that SIM.
ARAZZOemnify Register SIM Batch by BIC
Authenticate, validate a SIM batch by its BIC, then register the batch to the workspace.
ARAZZOemnify Reset Endpoint Connectivity When Blocked
Authenticate, read connectivity status, then reset connectivity only when the device is stuck.
ARAZZOemnify Send SMS and Track Delivery
Authenticate, send an SMS to an endpoint, then list the endpoint's SMS to confirm it.
ARAZZOemnify Send SMS to Endpoint
Authenticate, confirm the endpoint exists, then send a mobile-terminated SMS to it.
ARAZZOemnify Set Endpoint Data Quota
Authenticate, read the current data quota, then set a new data quota on an endpoint.
ARAZZOemnify Set Endpoint SMS Quota
Authenticate, read the current SMS quota, then assign a new SMS quota to an endpoint.
ARAZZOemnify Suspend SIM When Active
Authenticate, read a SIM, and suspend it only when it is currently Activated.
ARAZZOScroll within the panel for all 17 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
emnify GraphQL API
emnify provides a GraphQL API alongside its REST API, enabling flexible single-request queries against the emnify IoT connectivity data model. Clients can select exactly the fie...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Emnify Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Emnify Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Emnify Finops
FINOPSFeatures 29
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 29 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Emnify Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
emnify API Rules
SPECTRALemnify API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Emnify Endpoint Structure
JSON STRUCTUREEmnify Sim Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for emnify — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 10
Reference material describing how the API behaves
Scroll within the panel for all 10 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 20
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 20 ·
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/emnify · machine-readable index on apis.io