Kymeta
Kymeta Corporation is a Redmond, Washington satellite communications company that builds electronically steered, flat-panel metamaterial antennas and the connectivity service that runs behind them. Spun out of Intellectual Ventures in 2012 from metamaterials research begun at Duke University, Kymeta ships the u8 terminal family — Osprey u8, Goshawk u8, Peregrine u8, Hawk u8 and the compact Kestrel u5 — for military and government, maritime, land-mobile, energy and humanitarian users who need multi-orbit GEO/LEO connectivity on the move. The hardware is paired with Kymeta Connect, a software-defined service platform reached through the Kymeta Access app and the Kymeta Access Portal, which handles terminal management, subscriptions, usage metrics and remote monitoring. Kymeta operates a first-party API host and its own OAuth 2.0 / OpenID Connect identity provider, but publishes no public developer program, API reference or machine-readable contract; product documentation and release notices require a Kymeta Access Portal account.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Kymeta the way a machine reads it — 7 machine-readable artifacts across 2 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 — Kymeta scores 27.8/100 (thin), with a separate agent-readiness read of 12/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Kymeta runs a live first-party API host at api.kymeta.io that answers /health, /version and /status unauthenticated and 404s every specification path, while its own support site states "You must have a Kymeta Access Portal account to access the notices" — so the contract, reference and release notes for the Kymeta Connect platform all sit behind a customer tenant rather than being unpublished.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Kymeta's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://api.kymeta.io/status→ HTTP 200https://api.kymeta.io/openapi.json→ HTTP 404https://www.kymetacorp.com/support/product-and-software-updates→ HTTP 200https://access.kymeta.io/.well-known/openid-configuration→ HTTP 200
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-08-24 · rubric v0.12.1
Put this on your own site. The badge is drawn live from Kymeta's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/kymeta/"
title="Kymeta on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/kymeta.svg"
alt="Kymeta Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/kymeta/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/kymeta/"
title="Kymeta on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/kymeta/card.svg"
alt="Kymeta Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Kymeta
Each block below is one kind of artifact we hold for Kymeta. 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 2
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.
Kymeta Connect Platform API
Kymeta's first-party API host for the Kymeta Connect service platform, which backs the Kymeta Access app and the Kymeta Access Portal. The host answers unauthenticated on three ...
Kymeta Access Identity
Kymeta's own OAuth 2.0 / OpenID Connect authorization server (issuer https://access.kymeta.io), the single sign-on point for the Kymeta Access Portal, Kymeta Academy and Grapevi...
Pricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Kymeta 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.
Kymeta Rate Limits
RATE LIMITSSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Kymeta — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/kymeta · machine-readable index on apis.io
This is an independent, third-party profile of Kymeta, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.