Vapor IO is an Austin, Texas edge computing company that builds and operates the Kinetic Grid, a carrier-neutral network of micro modular data centers offering edge colocation, interconnection, networking and network-delivered AI across dozens of US markets and, through a Cellnex partnership, into Europe. Its public, machine-readable developer surface is the open source Synse platform, published under the vapor-ware GitHub organization: Synse Server, a uniform HTTP and WebSocket API for monitoring and controlling physical and virtual devices (data center equipment, IoT devices, building management systems, edge hardware), and the Synse plugin gRPC API, whose Protocol Buffers contract is published in full. Protocol-specific plugins cover IPMI, SNMP, Modbus over TCP/IP, Intel AMT and Juniper JTI, with Go and Python SDKs, a Go CLI, Helm charts and Docker images. Kinetic Grid Portal telemetry is described as API-accessible but is documented only to customers.
Vapor IO is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Edge Computing, Data Center, Colocation, and Infrastructure.
The Vapor IO catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Vapor IO’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, CLI, sandbox, and 22 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) 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 could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
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/vapor-io/"><img src="https://apis.io/badge/vapor-io/card.svg" alt="Vapor IO 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
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)
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
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.
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.
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.
Synse Server exposes a uniform HTTP and WebSocket API for reading from and writing to physical and virtual devices through protocol-specific plugins. The same 18 operations are ...
The internal gRPC API for bi-directional communication between Synse Server and Synse plugins. The published Protocol Buffers contract defines the V3Plugin service with 12 RPCs ...
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: