Xenesis
Xenesis, Inc. is an optical satellite communications company founded in 2017 by Mark LaPenna and headquartered in Lisle, Illinois. It builds the Xen-Hub, a free-space optical (laser) communications terminal enabled by a technology transfer from NASA's Jet Propulsion Laboratory and rated at greater than 10 Gbps, and plans Intercessor, a space-to-ground optical mesh network intended to backhaul high-bandwidth data with lower latency and higher capacity than radio-frequency or terrestrial fiber links. The company has taken Space Development Agency optical-terminal awards (Phase 1 in August 2022, a Phase 2 follow-on in December 2023) built to the SDA OCT v3.1 and v4.0 standards, signed a payload agreement with Airbus for a Bartolomeo demonstration slot on the International Space Station, and holds a $1.2M agreement with Georgia Tech for satellite optical communications work. Xenesis is a space hardware and telecommunications-infrastructure company, not a software vendor: as of this profiling pass it publishes no public API, developer portal, SDK, or machine-readable contract of any kind, and its own website is currently returning an HTTP 401 site-wide password lock.
Xenesis is profiled on the APIs.io network. Tagged areas include Company, Space, Satellite, Optical Communications, and Free-Space Optics.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Space and Satellite (operators, earth observation, ground segment) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.