GigSky

GigSky is a global eSIM and mobile-data roaming platform offering travel and enterprise/IoT cellular connectivity across 190+ destinations. For business, enterprise, and IoT customers it provides the GigSky Enterprise Manager (GEM) and IoT SIM Management portal with RESTful APIs for eSIM provisioning, plan/catalog and connectivity management, orders, and usage controls. The partner/reseller and enterprise API surface is account-gated rather than publicly documented.

GigSky publishes 4 API contracts indexed on the APIs.io network, including Plans & Catalog API, eSIM Provisioning API, Orders API, and 1 more. Tagged areas include eSIM, Mobile Data, Roaming, Connectivity, and IoT.

GigSky’s developer surface includes authentication, documentation, engineering blog, and 6 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

20.9/100 emerging ▬ flat Agent 16/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

1 published contract

eSIM Mobile Data Roaming Connectivity IoT Telecommunications

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 20.9/100 · emerging

Contract Quality 7.5 / 21

Developer Ergonomics 4.0 / 17

Access Clarity 1.3 / 17

Operational Transparency 0.6 / 11

Contract Governance 0.0 / 10

Discoverability 5.6 / 9

Regulatory Posture 1.5 / 15

Agent readiness — 16/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/gigsky/"><img src="https://apis.io/badge/gigsky/card.svg" alt="GigSky on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 7.9 — up to +18.4 composite points
Contract Quality scores 35.2 — up to +16.2 composite points
Developer Ergonomics scores 23.8 — up to +15.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/gigsky/apis.yml: open an issue on github.com/api-evangelist/gigsky to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

eSIM

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

GigSky Plans & Catalog API

Programmatic access to GigSky's catalog of regional and global eSIM data plans by destination and price zone, used by partners and enterprises to browse and select connectivity....

GigSky eSIM Provisioning API

RESTful eSIM/SIM provisioning and lifecycle management through the GigSky Enterprise Manager (GEM) and IoT SIM Management portal - assigning and activating eSIM profiles, countr...

GigSky Orders API

Order placement and fulfillment for eSIM plans and SIM deployments by partners and enterprises, tied to GigSky's pay-as-you-go and pooled-data billing models. Order endpoints, b...

GigSky Usage API

Reporting on data consumption and connectivity usage per SIM, user group, sub-account, or pooled plan, supporting GigSky's monthly statement and pay-as-you-go billing. Usage end...

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

GigSky Enterprise & IoT API

OPEN COLLECTION

GigSky API pricing

Not yet checked against GigSky's own pricing page. Compiled by API Evangelist on 2026-06-21 from www.gigsky.com/; confirm before you rely on a figure.

Plan	Price
Consumer Travel eSIM Data Plans usage	—
Enterprise & IoT Connectivity enterprise	—
Partner / Reseller & Bulk eSIM enterprise	—

Plan details, limits and sources →

Rate limits

API Rate Limit: see provider documentation requests

Compiled by API Evangelist, not yet checked against GigSky's documentation. Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

Gigsky Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Gigsky Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Gigsky Finops

FINOPS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Gigsky Authentication

http · 1 scheme

SECURITY

Gigsky Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Source (apis.yml)

aid: gigsky
url: https://raw.githubusercontent.com/api-evangelist/gigsky/refs/heads/main/apis.yml
name: GigSky
kind: company
description: GigSky is a global eSIM and mobile-data roaming platform offering travel and enterprise/IoT cellular connectivity
  across 190+ destinations. For business, enterprise, and IoT customers it provides the GigSky Enterprise Manager (GEM) and
  IoT SIM Management portal with RESTful APIs for eSIM provisioning, plan/catalog and connectivity management, orders, and
  usage controls. The partner/reseller and enterprise API surface is account-gated rather than publicly documented.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/gigsky.png
tags:
- eSIM
- Mobile Data
- Roaming
- Connectivity
- IoT
- Telecommunications
tags_raw:
- eSIM
- Mobile Data
- Roaming
- Connectivity
- IoT
- Telecom
created: '2026-06-21'
modified: '2026-06-21'
specificationVersion: '0.23'
apis:
- aid: gigsky:gigsky-plans-catalog-api
  name: GigSky Plans & Catalog API
  tags:
  - Plans
  - Catalog
  - Data Plans
  - Pricing
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.gigsky.com/enterprise-solutions
  baseURL: https://api.gigsky.com
  properties:
  - url: https://www.gigsky.com/enterprise-solutions
    type: Documentation
  - url: openapi/_original/gigsky-openapi.yml
    type: OpenAPI
  description: Programmatic access to GigSky's catalog of regional and global eSIM data plans by destination and price zone,
    used by partners and enterprises to browse and select connectivity. Endpoints, base URL, and authentication are partner/enterprise-gated
    and not publicly documented as of the review date; the base URL shown is illustrative and unverified.
- aid: gigsky:gigsky-esim-provisioning-api
  name: GigSky eSIM Provisioning API
  tags:
  - eSIM
  - Provisioning
  - SIM Management
  - OTA
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.gigsky.com/iot-solutions
  baseURL: https://api.gigsky.com
  properties:
  - url: https://www.gigsky.com/iot-solutions
    type: Documentation
  - url: openapi/_original/gigsky-openapi.yml
    type: OpenAPI
  description: RESTful eSIM/SIM provisioning and lifecycle management through the GigSky Enterprise Manager (GEM) and IoT
    SIM Management portal - assigning and activating eSIM profiles, country-by-country connectivity control, per-SIM and per-user-group
    limits, sub-accounts, and Over-the-Air (OTA) network provisioning. The API is account-gated; endpoint and auth details
    are not publicly published.
- aid: gigsky:gigsky-orders-api
  name: GigSky Orders API
  tags:
  - Order
  - Activation
  - Fulfillment
  tags_raw:
  - Orders
  - Activation
  - Fulfillment
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.gigsky.com/enterprise-solutions
  baseURL: https://api.gigsky.com
  properties:
  - url: https://www.gigsky.com/enterprise-solutions
    type: Documentation
  - url: openapi/_original/gigsky-openapi.yml
    type: OpenAPI
  description: Order placement and fulfillment for eSIM plans and SIM deployments by partners and enterprises, tied to GigSky's
    pay-as-you-go and pooled-data billing models. Order endpoints, base URL, and authentication are partner/enterprise-gated
    and not publicly documented.
- aid: gigsky:gigsky-usage-api
  name: GigSky Usage API
  tags:
  - Usage
  - Reporting
  - Data Consumption
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.gigsky.com/enterprise-solutions
  baseURL: https://api.gigsky.com
  properties:
  - url: https://www.gigsky.com/enterprise-solutions
    type: Documentation
  - url: openapi/_original/gigsky-openapi.yml
    type: OpenAPI
  description: Reporting on data consumption and connectivity usage per SIM, user group, sub-account, or pooled plan, supporting
    GigSky's monthly statement and pay-as-you-go billing. Usage endpoints and authentication are account-gated and not publicly
    documented as of the review date.
common:
- type: DomainSecurity
  url: security/gigsky-domain-security.yml
- type: Authentication
  url: authentication/gigsky-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/gigsky
- type: Website
  url: https://www.gigsky.com/
- type: Documentation
  url: https://www.gigsky.com/enterprise-solutions
- type: Plans
  url: plans/gigsky-plans-pricing.yml
- type: RateLimits
  url: rate-limits/gigsky-rate-limits.yml
- type: FinOps
  url: finops/gigsky-finops.yml
- url: https://www.gigsky.com/blog
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

GigSky API — frequently asked questions

Does GigSky have an API?

Yes. APIs.io lists 4 APIs from GigSky, including GigSky Plans & Catalog API, GigSky eSIM Provisioning API and GigSky Orders API, and 1 more.

Is there an OpenAPI specification for the GigSky API?

Yes. APIs.io indexes 4 OpenAPI specifications for GigSky, each linked for download from this page.

How do I authenticate with the GigSky API?

GigSky uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Gigsky Authentication.

How much does the GigSky API cost?

APIs.io lists 3 pricing plans for GigSky, with each plan's price, limits and inclusions under Pricing on this page.

Is the GigSky API ready for AI agents?

GigSky has a Kin Score of 20.9 out of 100 (emerging) and an Agent Readiness score of 16.1 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/gigsky"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/gigsky/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/gigsky/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.